Agile is more rapid in delivering effective and working results to customers while not paying much importance to efficiency. In Agile based environment sequence of steps is not given much importance and more focus is toward making working product faster with continuous collaboration of client to solve his/her issues in real time, On the other hand waterfall project management methodology follows more of a sequential process where structure and and approach is given most importance. It is comparison of traditional project management vs modern approach to management. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Anon, no Agile do not replace Waterfall as a rule of thumb. You will find that certain industries/customer still require full specifications and planning up front. I have spend more time working in a hybrid environment than any other. The 'back end' would be agile while the 'front end' is still waterfall.
Remember that Agile has been around for ages with different frameworks, SCRUM being a more recent one. Saving Changes...
Seema SonkiyaHead Business Analysis Practices, PMI-PBA trainer| iZenBridge Consultancy Private LimitedJaipur, Rajasthan, India
For Waterfall, the right term is predictive life cycle; here we can predict the solution from the day one. We can predict what has to be done and how?
Agile is used when we cannot predict in advance how the solution will look like? You frequently deliver small usable work, and we decide further actions by taking the feedback.
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Pick the right tool for the job at hand. The value is dependent on the needs of the organization. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Both are no matter of comparison. Agile is a practice. Waterfall is a life cycle process based on Predictive life cycle model. You can apply Agile using Waterfall life cycle process. I am doing that from years and you can find examples outside there. I am working with Agile from the very beginning when I was part of the place where Agile was formally born (USA DoD NSF/Agility Forum, 1990) and I was part of the group of authors of the former Agile software development method named DSDM (version 1 and 2. Today becomes agile solution delivery method). I was the pleasure to write a short article form PM Network that perhaps helps you, ("Perfectly Positioned", http://www.pmnetwork-digital.com/pmnetwork/april_2016?pg=73#pg73 Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
And let me say: I am leading my seventh initiative to implement Agile at enterprise wide fashion (non software, non IT, non an specific method). And to do things, to create any type of product, we have five different project life cycle process defined. We choose one depending on some factors we create from organizational architecture (needs as Andrew said, uncertainty as Seema said, and other factors we create from organizational architecture). You can find predictive and adaptative process model into them. And our project/program and portfolio managers work with them including the fact there are a mix of project using a mix of them at the same time. Saving Changes...
John TiesoAuthor, Lecturer in Business Management| The Catholic University of America, Busch School of Business & EconomicsArlington, Va, United States
Agile is a method--one which can be applied in many different forms, depending on the purpose. The steps performed in an agile environment are determined strictly by the need and culture of an organization.
Conversely, the 'Waterfall' is a set of fixed steps, with specified deliverables, which demonstrate a complete life cycle in advance, unlike Agile, which can change both as needed in specific projects.
...
1 reply by Sergio Luis Conte
Jun 15, 2017 5:23 PM
Sergio Luis Conte
...
John. with all my due respect, Agile is not a method. Agile as Lean (are not the same) are practices. With basement in those practices you can define life cycle process and methods based on these life cycle process.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jun 15, 2017 5:18 PM
Replying to John Tieso
...
Agile is a method--one which can be applied in many different forms, depending on the purpose. The steps performed in an agile environment are determined strictly by the need and culture of an organization.
Conversely, the 'Waterfall' is a set of fixed steps, with specified deliverables, which demonstrate a complete life cycle in advance, unlike Agile, which can change both as needed in specific projects.
John. with all my due respect, Agile is not a method. Agile as Lean (are not the same) are practices. With basement in those practices you can define life cycle process and methods based on these life cycle process. Saving Changes...
John TiesoAuthor, Lecturer in Business Management| The Catholic University of America, Busch School of Business & EconomicsArlington, Va, United States
Sergio: With all respect, Agile, in my view, is a method. It creates a format and structure within which to do work, define an expected outcome or output, and ensures that there is a logic to how to proceed.
In deference, it can also be defined as a practice, both from the perspective that there are professionals who are dedicated to the processes which are inherent in the workflow and decision-making process.
Agile methods can be practiced in whole, in part, or be one of the techniques adopted in a framework for a project as one of several means to achieve success. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sorry John, but it does not right. As I mentioned in other forums I was part of the intiative where Agile was formally created. Agile was created from Lean. And as Lean both are practices or disciplines. Life Cycle models was created with basemen on Agile (predictive), life cycle process was created from those life cycle models (iterative, incremental, etc) and then methods was created to support those life cycle models (SCRUM, DSDM, etc). It is important to take into account this. If not, people will fail when tried to use Agile practices. For example, people can apply Agile with predictive life cycle models and life cycle proces based on those models like waterfall. Saving Changes...
Love can sweep you off your feet and carry you along in a way you've never known before. But the ride always ends, and you end up feeling lonely and bitter. Wait. It's not love I'm describing. I'm thinking of a monorail.
