O'Reilly logo
  • Bill Levien thinks this is interesting:

IT software projects traditionally began with the production of extensive upfront documentation, which included project plans, functional requirements, system design specifications and technical architectural designs. These documents – which often took months to produce (and even longer to get approved) – were intended to ensure that the developed software would align with user requirements. In reality, however, these documents only served to provide corporate managers with a false sense of security in the expenditure of their IT budgets, and to ensure that delivered software would be substantially misaligned with the ongoing – and changing – needs of the business.


Cover of Everything you want to know about Agile


Agile helps avoid pitfalls of traditional IT Projects