Do not think "Agile vs. Waterfall". This discussion leads to nowwhere. Think about "Agility" as a lean approach to get work done in projects where you have adaptive scenarios. You can work with agility also in a waterfall environment! Check out there Agile Practise Part in this website where you can find also articles that discuss this matter. Saving Changes...
Agile is a mindset where you select approaches which help to respond to change. Your mindset is to deliver value frequently. In waterfall, things are explored upfront, and you receive value at the end. Saving Changes...
Both are not matter of comparison. Agile is a practice. Waterfall is a life cycle process based on predictive life cycle model. In fact you can apply Agile using waterfall life cycle process into your project.
...
1 reply by John Tieso
Sep 15, 2017 5:14 PM
John Tieso
...
Absolutely, we did it in the US Government for years, since the early definition of systems engineering from the Navy. As Sergio indicated, Agile is a practice--a way of accomplishing work, and Waterfall is the life cycle in the form of steps versus a timeline.
Agile is about providing a framework that allowed changes to be readily incorporated in a project. In Agile, the schedule is fixed but the scope is not.
Waterfall is about predicting what will happen and doing the work necessary to bring it to life. In waterfall, the scope is fixed but the schedule is not. Saving Changes...
Waterfall
This being a traditional methodology is the simplest and easiest to understand. In this methodology, there is a sequence of tasks which leads to the final deliverable. One task must be completed before the next one begins, in a connected sequence of items that add up to the overall deliverable. The effectiveness of this methodology is that every step is pre-planned. Any changes in customer’s need or priorities will disrupt the entire sequence of tasks, making it very difficult to manage.
Agile
This project methodology focuses on visualizing end state. Agile?—?a refinement of earlier methodologies provide rapid continuous delivery. Agile’s four main values are expressed as:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Teams following Agile methodology work in cycles of planning, executing and evaluating results at the end. Depending upon the results of these evaluations, the final deliverable may be modified in order to create a better end result for the customer. It mainly emphasizes on continuous collaboration both within the project team members and with project stakeholders. Saving Changes...
Sorry, but the point to be succesful is: to understand that Agile is not a methodology and Waterfal is not a methodology. What you have are methods based on a life cycle process (waterfall for example) where you can apply some practices (Agile, Lean, etc.) You can find a lot in the new PMBOK Guide about it (i was part of the group of authors and reviewers) Saving Changes...
Both are not matter of comparison. Agile is a practice. Waterfall is a life cycle process based on predictive life cycle model. In fact you can apply Agile using waterfall life cycle process into your project.
Absolutely, we did it in the US Government for years, since the early definition of systems engineering from the Navy. As Sergio indicated, Agile is a practice--a way of accomplishing work, and Waterfall is the life cycle in the form of steps versus a timeline. Saving Changes...
Zareh, I disagree with the conclusion in the article you are referencing. This Waterfall vs. Agile discussion leads to nowhere. I am a strong supporter of tailoring the practices to the best fit of a project and also the maturity of the respective organization to digest what degree of agility is important to consider. The recently issued PMI Agile Practise Guide offers additional guidance.
Zareh, I disagree with the conclusion in the article you are referencing. This Waterfall vs. Agile discussion leads to nowhere. I am a strong supporter of tailoring the practices to the best fit of a project and also the maturity of the respective organization to digest what degree of agility is important to consider. The recently issued PMI Agile Practise Guide offers additional guidance. Saving Changes...
