When considering the difference between waterfall and agile, does the methodology of a project impact the length of the project?
Grant HamelMr RTE Agile Passionate| The Coventry Building SocietyBanbury, Oxfordshire, United Kingdom
As agile is iterative and meant to assist to accelerate the delivery of a project, especially with accelerated outputs is it deemed as a more rapid delivery process? And does this then impact the length of the project? We have had the age old debate, waterfall or agile and often it is a hybrid of the two (if there is such a thing?). Perhaps the real question is that when estimating the length of a project, (and naturally the nature of the project determines the methodology), does the methodology impact this? Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Certainly, if the focus is on ensuring delivering value vs simply delivering on a list of [outdated] requirements, we can think of delivery as expedited. But it is the inherent feedback loop and transparency that affords these opportunities to teams and organizations.
When looking to predict the life of a project, consider the sought outcome to understand how to judge the end state. If the problem is solved with less functionality than originally thought, than fantastic. How did we determine that? Feedback, adjustments, transparency, inclusivity.
If we go into a silo and build what was once thought of as the solution for the at the time understood problem, it more than likely will take longer to realize a finished product, which may or may not solve the problem that may or may not still exist.
It is not just about time, but about value - solving a problem with the least amount of effort and 'stuff' as possible.
Estimation of length can either be prescribed through best guess or validated empirically. Saving Changes...
