If you know how to do it without being indicted anyway.
Constant back and forth change orders, pointless delays to serve constantly changing stakeholders, constant demos with no real product, no one in the customer with any power who has experience to call BS on timelines or delivery, etc.
And if done correctly, everyone in the ‘customer’ is simultaneously happy and angry and so it’s easy to deflect blame and point fingers back into their own org.
Or so I’ve heard from folks who are involved. I try to avoid it like a plague, the BS I deal with hurts my soul enough already.
The federal government is a big beast, though, so it takes a while for the idea to spread.
If leadership isn't careful (and it seldom pays to be careful), it becomes an excuse for every real wrong.
> Testing was largely a manual process. Releases and deployment required lengthy overnight downtimes and often failed, required equally-lengthy rollbacks. The core data layer lacked a schema. Provisioning hosting resources was slow and not automated. Critically, there was a pervasive lack of monitoring of the site. No APM, no bog-standard metrics about CPU, memory, disk, network, etc., that could be viewed by anyone on the team.