Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Catch agile

456 vues

Publié le

History of Agile frameworks and examples of it's misusing.

Publié dans : Technologie, Business
  • Login to see the comments

  • Soyez le premier à aimer ceci

Catch agile

  1. 1. Catch AgileAntipatterns of using Agile: how to survive by Yuriy V. Silvestrov
  2. 2. About meYuriy V. Silvestrov10+ years record in IT, 8+ years devoted to managingprojects. Now working for Ciklum, managing a teamof 30+ persons making different software for Danishfinancial organizations.Please visit my websitehttp://yuriy.silvestrov.comfor more info or contact me atyuriy@silvestrov.com.
  3. 3. About lection
  4. 4. ⌛ < 60Time is counting
  5. 5.  Agile Scrum Kanban I will try to adaptHow many of you using
  6. 6.  History of Project Management Frameworks ◦ Waterfall ◦ BDUF ◦ Incremental ◦ Agile Catches ◦ Waterfall problems ◦ When Agile wouldn’t work ◦ Dealing with Conveyor ◦ Scrum-like ◦ Scrum cargo cult ◦ Common sense bias Business cases Q&AContent
  7. 7. Snowflake men by Max Dorofeev
  8. 8. History of PM Frameworks
  9. 9. Waterfall
  10. 10. By IBM ResearchCost of bug fix
  11. 11.  Comprehensive documentation Tools and processes Following a plan Contract negotiationInvention of BDUF
  12. 12. BDUF Problems
  13. 13. Incremental development
  14. 14. Agile
  15. 15.  Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a planAgile manifesto: 2001
  16. 16.  Teamwork & responsibility over Individuals and Interaction Deliver Value over Working software Partnership elaboration over Customer collaboration Embrace change over Respond to ChangeAgile manifesto 2.0: 2011
  17. 17.  Scrum XP Kanban Lean CrystalAgile frameworks
  18. 18. Scrum
  19. 19.  “Many of the [systems] details only become known to us as we progress in the [systems] implementation. Some of the things that we learn invalidate our design and we must backtrack. David Parnas, A Rational Design ProcessCatch 0: problems of Waterfall
  20. 20. Be Agile!Solution?
  21. 21. Catch 1: when Agile wouldnt work
  22. 22.  The more is your team size and the more a bug in your product would cost, the less you’d to benefit from Agile. Alastair CoburnTeam size and bug-critical soft
  23. 23.  Customer collaboration over contract negotiation Responding to change over following a plan Individuals and interactions over processes and tools Working software over comprehensive documentationAgile principles violation
  24. 24. “DeathMarch” by Edward Yourdon
  25. 25. Catch 2: dealing with conveyor
  26. 26.  No releases schedule Priorities changing often Hard to estimate size of each elementWhy Scrum is not best choice
  27. 27.  Try KanbanSolution?
  28. 28. Catch 3: scrum-like
  29. 29.  Should always try to improveNo retrospectives
  30. 30. Standup-meeting as speech to PM
  31. 31. Code Complete ✔ Unit Tested ✔ Peer Reviewed ✔ QA Complete ✔ Documented ✔No Done-Done criteria
  32. 32.  Pareto rule:80% of task valuetakes 20% time.Another 20% takesanother 80% of time.80% done
  33. 33. Catch 4: Scrum cargo cult
  34. 34. Catch 5: Common sense bias
  35. 35. Business cases
  36. 36. ???Questions?
  37. 37. yuriy@silvestrov.comThank you!

×