Which Project Management method would be best equipped to handle change in requirements? Why?

Managing change with the traditional Waterfall methodology would undoubtedly prove much more challenging than it would with the Agile methodoloy.

The fact that Agile methodology will mean breaking the project down into many smaller sections known as sprints, each typically of between 1 – 4 weeks in duration allows the team to make changes along the way in an extremely dynamic manner. By its very nature, Agile methodology caters to constant changes in terms of project requirements and as the project advances new requirements may be identified and quickly integrated into the next upcoming sprints.

In this specific case we are developing mobile apps which is another clear reason to favour the use of Agile as it is particularly appropriate for software development projects which tend to require close collaboration between self-organising and cross-functional teams.

Scrum is a specific Agile framework and one of the most popular Agile methodologies with the objective of enabling the production and delivery of properly tested product increments within short iterations. Meeting daily, exchanging feedback and ensuring full accountability ensures that all team members are fully updated, engaged and focused on both specific and collective project requirements and the fact that a sprint will usually only last a couple of weeks means that while we will not introduce any major change in the middle of a sprint, we can do it almost “seamlessly“ in the next upcoming sprint.

With a traditional Waterfall methodology whereby each phase must be completed before the next phase can begin a 30% increase in scope while maintaining the same time deadline would require totally rethinking every aspect of the project, and quite possibly, a lot of the work already done.

Related: 3/3 Blues in D – Potentially Shippable Product