3 ms·
It’s no accident. Waterfall is driven by government procurement regulations. If the components of the waterfall look uncannily like a high level work breakdown
by Spooky23 8y ago
It’s no accident. Waterfall is driven by government procurement regulations. If the components of the waterfall look uncannily like a high level work breakdown structure of a project... that’s because it is.
The historical philosophy of government procurement is not just an outcome, but a competitive process. In many circumstances each part of delivery let to bid, and bidders performing design work cannot implement.
Even today, design-build (aka agile) is fairly limited in most procurement scenarios.
The thing that’s hard for people to grasp is that equity in procurement often yields increased cost and timelines. If vendors don’t price risk into bids, they lose money and fail to deliver. The government compensates with more stringent requirements that make it harder to bid, which shrinks the bidding pool, etc.
- cheschire 8y agoIndeed. The documents referenced in the OP seem like the eventual attempt at squeezing software development into the confines of Public Law 93-400[0], which predated the DOD Standard doc from OP by a good decade, and the Federal Acquisition Regulation which was an evolution of the Armed Services Procurement Regulation originally published in 1947! In my opinion, these concepts are fundamental to the successful functioning of a monopsony like the government, who is also subject to it's own equitable competition laws. 0: https://www.gpo.gov/fdsys/pkg/STATUTE-88/pdf/STATUTE-88-Pg796.pdf https://www.gpo.gov/fdsys/pkg/STATUTE-88/pdf/STATUTE-88-Pg79...
- igouy 8y agoAlso, when vendors don't have their bid accepted, they have been known to take the government to court. So the government compensates with a document heavy process -- not to prepare for implementation, but to prepare for a court case.