Are you referring to an adaptive life cycle vs. a predictive one, or the practices normally associated with agile delivery?
If the latter then I'd say that agile practices can be applied to traditional projects just as well as to projects following an adaptive lifecycle.
However, if it was the lifecycles, then traditional lifecycles work well where stakeholder needs & requirements are not likely to change, value can only be realized when the full scope is delivered, and/or key resources are only available at specific times over the project's life. Adaptive lifecycles would work well in all other cases so long as the appropriate mindset and behavior is in place in the team and supporting roles.
Kiron Saving Changes...
Jose Luis Gonzalez RugelPresidente Grupo Gonzalez - Program Manager - Docente- Consultor - ATP Trainner| DipromacomGuayaquil, Guayas, Ecuador
From my point of view, the atraditional schema is very useful for projects with clearly defined scope such as predictive, incremental, iterative projects (construction, infrastructure, etc). The agile principles are more useful for projects where the scope is detailed in the way as are the adaptive projects (softwatre, design, etc.). I do not believe in just traditional or just agile projects, I believe more in the hybrid concept where the PM decides which tool to use from each one of the approaches according to the project or stage that is being managed Saving Changes...
Elizeu AntonioManager for Network Operations| MSTelcomLuanda, Angola
Traditional, still happening...so more and more are embracing Project Management Methodology up now. Agile, for some still emerging and it will encourage development teamwork, iterations and so on.
I believe both, Traditional and Agile have projects more suited to one or another. Saving Changes...
There isn't such a big divide between organizations using one or the other. I still think the majority (when Agile is used) actually use a hybrid. Saving Changes...
