Waterfall and agile are two unique development models used in interactive and software production. It's likely the debate over which is better will continue indefinitely, but in reality, both approaches boast significant but different benefits. It's generally accepted that agile, specifically, lends itself well to software development and large-scale website projects. Although a novice Project Manager may feel more comfortable working with a waterfall approach because each step is predictable, letting go of the familiar may well be worth it to make the move to an agile model. The collaboration and flexibility that agile brings can result in a better end product for your client, and a more engaged, harmonious internal team.
> large-scale website projects. Although a novice Project Manager
> may feel more comfortable working with a waterfall approach
> because each step is predictable, letting go of the familiar may well
> be worth it to make the move to an agile model. The collaboration
According to PMI, one of key responsibilities of PM is to define the scope of the project. The project can be executed by following waterfall model/iteration model!
In case of agile software development, the scope is not clear!! So the team develop something and iterate through the entire cycle till they get proper clarity on the software that needs to be developed. Generally R&D/New Product Development activities follow agile software development.
Best Regards,
Vivekanandan M Saving Changes...
Matthew PateePMO Director| ABM IndustriesBenicia, Ca, United States
I disagree with the statement "In case of agile software development, the scope is not clear!!".
Scope must be defined up front, prior to development, in all implementations of the Agile methodology I have seen. However, it is generally accepted that the scope will change because it is defined at a high-level with end-goals in mind. As iterations are delivered, requirements and solutions are changed and must be vetted against the scope. I strongly suggest that any requirements / solutions that are not aligned with the original scope follow change control.
When you are not sure how many iteration will happen, one cannot really do cost and time estimation for the project. Also CPI and SPI cannot be measured!!
It will be great if you can explain the constraints that needs to be managed by a PM!
Best Regards,
Vivekanandan M Saving Changes...
Matthew PateePMO Director| ABM IndustriesBenicia, Ca, United States
First - I agree with you... Timeline and budget are much more dificult to predict up-front. However, the scope of what you are trying to accomplish shouldn't be.
The same constraints are still managed, but in a diferent way. Think of Agile development as a Program where the Projects are managed serially. In other words, each iteration effectively becomes it's own project with it's own scope, budget and timeline. Until you are nearly complete with the first project (iteration), you cannot firm up the scope, timeline and budget for the second. Saving Changes...
Andrew MakarProgram Manager| AMAKAR LLCOakland Township, Mi, United States
Methodology can be used as a noun "the path to be taken" or as a verb "activities to be undertaken while on the path".
All too frequently these terms are misunderstood and/or interchanged (noun vs verb).
For the sake of context, "waterfall" is more frequently applicable to the "noun" (path to be taken - specific sequence of deliverables) and "agile" is applicable to the "verb" (activities and iterations to be taken while on that path).
Obtain further clarity from article posted at QAIassist.
