Comment Oof - numerous problems (Score 1) 143
1. Big waterfall software projects fail. I collect examples of project successes and failures, and I have never come across a large software project that was successfully delivered on-time and on-budget. It's like unicorns: People dream of them, but they don't really exist. The only way you even have a chance of delivering a big project is to break it into pieces and deliver a lot of small projects.
2. Government funding forces you to do waterfall projects. Funding for big projects must be approved, meaning that you have to get all the requirements and project planning defined up front. After that, even if you can work some iterations into the implementation, you are still basically doing a big waterfall project. See (1) above.
3. Politics (if you are more direct: corruption). Big government projects go through a horrible bidding process. The successful bidder must outsource parts of the project, and the outsourcing must be distributed to the right types of businesses (women/minority/whatever) in the right political districts. None of this has anything to do with getting a good project done. It's more like making your best developers write code while carrying sacks of cement on their backs and hopping on one foot.
4. Lastly, regulations. Back when I worked in government acquisition, we once has a small contract to let. One bidder was a company that had never done government work before, but they thought they'd give it a try. They underbid the competition by a factor of 3 or 4. My boss quietly took the CEO to the side and told him that he'd better double his bid, because he had no clue how much regulatory crap and how much paperwork was about to head his way. The company doubled their bid, got the contract, and I'm pretty sure they still lost money on the deal.
tl;dr - Who in their right mind wants to work on a project that is (2) doomed to failure from the start, (3) prohibits you from trying to do a good job and (4) is more about paperwork than anything else.