The results in messed up. We always strove, after winning, to write a rational requirements document that acknowledge the uncertainty. Most times they 'got it' and accepted that sort of management style, but there were also times when you'd be tasked to do something utterly useless because of some "shall" in a requirements document that is now hopelessly out of date. But it depends. A half million $ contract you can have that conversation. $60million+, several subcontractors? Not so much.
What eventually happens is that to give oversight to the decision makers on a sufficiently large project, your dev leads spend all day in status update meetings with scrum masters, who spend all day in status update meetings with project managers, who spend all day in status update meetings with directors and functional leads. Decisions are made a level above that, so you've got 5 levels of management in a big game of telephone.
It's still probably better than the alternative, but Agile doesn't give you the certainty around schedule and budget that waterfall does. There's a mindset in the government that often manages around schedule and budget ONLY; so it will take rooting out several generations of government project managers to really start to crack the problem.
Like I said, I don't envy the guy. But his bar for success is so low that it would be hard not to improve things.
I completely agree with the first sentence conceptually, but think the second is a terrible fit for that concept.
A monolithic healthcare.gov actually makes a lot of sense as every implementation will necessarily have loads of shared functionality.
There's a reason state exchanges have spent multiples of what healthcare.gov has per sign-up. [1]
>'Every single company that wants to should be able to build their own solution to this. They can be rewarded based on how many users they get, or the best one can win a bounty.'
This isn't a throwaway chat app. The tacit Government approval of free-for-all collection of the SSNs, income and health coverage information that go into a marketplace application would not be wise.
1: http://www.npr.org/blogs/health/2014/05/08/310721495/healthc...
One of the governing principles of the ACA was that the states would be afforded the ability to experiment with their own approaches to meet the law's guidelines, the other states could replicate what worked. Would have been a wonderful opportunity to try 50 differnent ways to bid, design and build the same system...
Government tech has the unfortunate problem of requiring instant scale. As in whenever you develop a new app or tool, it needs to roll out to a hundred thousand (or hundred million in the case of healthcare.gov) people and needs to integrate with dozens or even hundreds of different systems. Which of course, is the entire problem to begin with.
It's pretty obvious that the old way of doing things is not sustainable. Most people would say the answer is Agile processes; but that has drawbacks in a government context. Agile can mean many things. Depending on how you implement it, but there is an inescapable trade-off of efficiency for oversight. Government contracts need oversight; otherwise you have contractors who aren't meeting their obligations and collecting millions of dollars while throwing obviously unqualified people at a problem. Often nobody on the government side is even paying attention that the work isn't getting done until it's too late.
I really don't know what the answer is here. There are lots of problems with the government procurement process, but there is a lot of money on the line and the people receiving it have a vested interest in maintaining the status quo. Ultimately the procurement process is the biggest issue. Contracts go to the company that can navigate the procurement process most effectively; not the company best suited to do the job. Given the bureaucratic nightmare that is government procurement, any procurement process designed to find the best company for the job will still ultimately reward the companies most adept at gaming the system through back channels (e.g. calling in a favor with a Congressman to ensure the criteria for contractor selection benefit a specific company).