Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why agile


Published on

Basic presentation about the agile way of working

  • Be the first to comment

Why agile

  1. 1. Why to move to agile
  2. 2. Introduction
  3. 3. Expectations
  4. 4. Problems of Waterfall
  5. 5. Introduction to Agile
  6. 6. Individuals and interactions over processes and tools
  7. 7. Working softwareover comprehensive documentation
  8. 8. Customer collaboration over contract negotiation
  9. 9. Responding to change over following a plan
  10. 10. Different agile methods
  11. 11. Benefits of Agile
  12. 12. ComparisonProcess Traditional Development Agile DevelopmentMeasure of Success Conformance to plan Response to change, working softwareManagement Culture Command and Control Leadership/CollaborativeRequirements and Design Big and up front Continuous/emergent/just-in- timeCoding and Implementation Code all features in Code and unit test, deliver parallel/test later seriallyTest and Quality Assurance Big, planned/test late Continuous/concurrent/test earlyPlanning and Scheduling PERT/detailed/fix scope, Two-level plan, fix-date, estimate time and resource estimate scope
  13. 13. Continuous Delivery
  14. 14. You will hit the wall
  15. 15. Barriers to agile adoption
  16. 16. There will be resistance
  17. 17. Reasons for Resistance
  18. 18. Problems solved?
  19. 19. Expectations check
  20. 20. Credits• Survey data: –• Agile Manifesto –
  21. 21. Pictures• Why to move to agile:• Introduction• Expectations• Problems of Waterfall• Introduction to agile Agile_Software_Development_methodology.svg.png• Individuals and interactions over processes and tools• Working software over comprehensive documentation• Customer collaboration over contract negotiation• Responding to change over following a plan• You will hit the wall• There will be resistance• Problems solved?• Expectations check• Thank you for your attention
  22. 22. Thank you for your attention!
  23. 23. Contact InformationSven Schnee Agile Project Manager Twitter: @MrSnow76 LinkedIn: Goncalves Agile Project Manager Twitter: @lgoncalves1979 LinkedIn: