How does Agile differ from Waterfall?
A free video tutorial from Nextgen Academy
International Agile Project Consultant
3.7 instructor rating • 1 course • 20,223 students
Learn more from the full courseYour complete guide to Agile, Scrum, Kanban
Scrum Master certification training + Agile Scrum Training + Scrum Product Owner training
02:53:28 of on-demand video • Updated May 2019
- At the end of this course, students will easily be able to practically apply each 12 steps of the Agile Manifesto
- Learn to differentiate and understand risks and pitfalls in an Agile environment and how to overcome them
- At the end of the course, students will be able to practically apply their your new Scrum Master and Kanban knowledge to lead teams through production sprints
- Students will be able to demonstrate a deep knowledge in Project Planning as well as risk mitigation
- Students will be able to add value to their organization through learning about Business Value in an Agile environment
- You will be able to foresee risks and demonstrate excellent problem solving skills using different methods
English [Auto] So if we look at agile you see that the first point is actually a key principle within the agile methodology frequent delivery of work and value that the customer frequently sees work being delivered within Sprint review sessions usually within 10 days. Changes in decisions can be made throughout the project. The second part being strong sense of ownership. Now there's always a strong sense of ownership team wide as the team works together daily to build a product. You have all your ceremonies in your scrum with you. This can be very easy to produce MVP. Now agile prides itself in delivering high business value and working software thus making it easier to produce a basic version of said software that can be timed with business goals such as marketing etc. Every day is a requirement day development is a more user focused as there is no single point in time for requirements but every day community requirements which can be section into further sprints into the product backlog and take it into the future sprints that you will have. Now let's take a look at the negative sides of agile here. So each item might not be completed in the time box. Agile as we're going to explore within this course is a time box delivery. This allows for changes and prioritization. Now this means that delivery items might not be able to complete it within the planned sprints. Should the store points be too high or wrongly estimated by the team during the sprint planning now additional project costs can also encourages additional features being requested throughout the project. We need to adapt and change as well when we work on agile. So reduction of quality. There's a risk for possible reduction of quality due to frequent refactoring. It's a full scope is not considered in the architecture or design. Now if we look at the agile timeline loop here you usually have your meeting time and this is your backlog group sessions or spring training sessions. You also have design code and test release feedback which you are receiving a script review sessions going back into the plan. So let's take a quick look at a comparison between waterfall and agile. So starting with customer availability customers get involved they're very certain milestones in the project for instance approvals. There is design hand over to Dev there's test handover as you hand over so all of those are very self-contained. If you look at customer availability with an agile stakeholder availability is very very important throughout the project and key. You have them in your reviews you have them within your sprints you have them within your sprint planning always talking to each other. Communicating is also one of the principles of agile. So when we look at scope and waterfall the predefined requirements are key for waterfall and they work really well when the changes are limited. That means that there's a pre agreed scenario to work out. And this is pretty much it. Any changes on welcome. So if you look at scope and agile adapt very well to change it does come at a cost when the project is not known in advance. When we talk about prioritization and waterfall the customers get everything they ask for. If the task is determined within the contract then the requirements phase that is all agreed. But that waterfall is that it's like everything is agreed on upfront and then the team executes it. When you look at prioritization with an agile delivering value a working software reduces the risk and can show signs of project being on track rapid milestone delivery increases the chance of an organizational approval where we're looking at pricing cost budget for waterfall. There's always an agreement as mentioned before the handshake happens upfront. That means that the fixed project cost stands now for Agile that works great with a rolling budget or when a cost is set with a limit of Sprint's let's say 10 sprints or whatever. However that means the work is still pending. So a cost model for Agile could be monthly funding for the whole project when you look at the team aspect for waterfall and jostle for waterfall the team handoffs mostly happened during separate milestones have been achieved design to development. For instance if you look at agile there's smaller teams and their self organized. They're pretty much run themselves but this process is the killer of agile.