Public-sector entities have faced controversy over how large IT projects are built and deployed. The original style of creating management systems was waterfall: an exploration of need or request for information is done; an RFP is released with a list of requirements; after a vendor is selected, they plan and build out the project; it is then released. After the release, the department can then review and adjust the program.
The big complaints about this style are the wrangling of cost and timeline. Another concern is that reviewing and requesting changes after a product is released can be too late. Some things are baked into a system, making it very difficult to undo or manipulate after other things have been built on top.
In order to fix this problem, many vendors have begun offering agile methods. The agile methodology has allowed for review and feedback along the plan and build.
However, agile has also received criticism for scope and budget creep.
Some vendors have suggested dividing requirements up and using a hybrid approach.
