Waterfall and Agile: a comparison
•
4 likes•844 views
This document provides an overview of waterfall and agile methodologies. Waterfall aims to contain and control changes through sequential phases of analysis, design, development, testing while agile embraces change through iterative development and customer collaboration. The document discusses why agile is preferable due to the inevitability of change. It outlines the agile manifesto values and how scrum implements agile through self-organizing cross-functional teams, sprints, daily standups, and retrospectives to continually deliver working software.
Report
Share
Related slideshows
Waterfall and Agile: a comparison
- 1. Waterfall and Agile Patrice Kerremans
- 2. whoami Patrice Kerremans Architect 19 years Development 13 years Agile Development 8 years Certified Scrum Master
- 3. Waterfall
- 4. testcodedesignanalyse Why? To contain, control changes and budget How? What? A big misunderstanding* ;) * Read: http://pragtob.wordpress.com/2012/03/02/why-waterfall-was-a-big-misunderstanding- from-the-beginning-reading-the-original-paper/
- 6. Agile
- 7. Why agile? to embrace change
- 8. but WHY?? Because change is inevitable* * on many/most projects
- 9. huh WHY??? Because no-one can always foresee everything in every project* * at least I can’t
- 10. WHY??? Because the proof is in the eating of the pudding* * only when you eat the pudding, you taste its flavour and only then you can start improving
- 11. WHAT approach, mind-set to embrace change to learn from mistakes; fast, early, often people oriented business oriented
- 12. What not a religion excuse for not documenting excuse for not having requirements repeating waterfall in very short cycles excuse for having a few people do all the work excuse for having people work during weekends excuse for having only business tasks a now technical tasks performed
- 13. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 14. How with Scrum* * there are many ways to implement agile, I like Scrum, but maybe another framework is a better fit for you…
- 15. product owner scrum master team (5-9 people) what to do prioritize ceremonies unblock buffer deliver product increments full time contributors self-organising estimate work
- 17. CONTRACT As a customer I want to see how much I spent on gas and electricity Because I want to start saving on my energy spending 7% 8% 10% 11% 29% 35% -100 Electricity -30 Gas -120 Electricity -30 Gas -50 Gas
- 19. 24h 2-4 weeks Daily scrum to do the follow-up of the tasks What did I do yesterday? What am I doing today? What has been holding me back? 15 min
- 20. What did our team do since we last met? What will our team do before we meet again? Is anything slowing our team down or getting in our way? Am I about to put something in another team’s way? 15 min Scrum of scrums
- 21. When When you expect changes* * But not of the chaotic type
- 22. Well known unknown Requirements Technology chaos sim ple com plicatedcom plex Totally unclear Totally clear
- 23. Totally unclear Totally clear Well known unknown Requirements Technology H ouse of Pain W alk in the park Puzzle Labyrinth
- 24. Totally unclear Totally clear Well known unknown Requirements Technology science justdo it w aterfallifyou w anttoagile
- 25. some differences between scrum and waterfall
- 28. 0 25 50 75 100 1 2 3 4 5 6 7 8 9