Catch AgileAntipatterns of using Agile: how to survive                     by Yuriy V. Silvestrov
About meYuriy V. Silvestrov10+ years record in IT, 8+ years devoted to managingprojects. Now working for Ciklum, managing ...
 Based on my own and       About lection  team experience and a lot of interviews  conducted  Have been presented  in ...
⌛ < 60Time is counting
 Agile Scrum Kanban   I will try to adaptHow many of you using
   Catches    ◦   When size matters    ◦   Agile principles violation    ◦   Dealing with Conveyor    ◦   Scrum-like    ◦...
Snowflake men by Max Dorofeev
ScrumXP Kanban Lean CrystalAgile frameworks
Catch 1: Size matters
Cockburn                        ScaleL   L6   L20 L40 L100                      The closer theE   E6   E20 E40 E100 projec...
 Start creating procedures May be even to become more formal and  less agile When the project and team became more  mat...
 Customer collaboration over contract  negotiation Responding to change over following a  plan Individuals and interact...
 Try to keep agility inside, and be formal  seen from outside Actually, it’s rather political then project  management p...
“DeathMarch” by Edward Yourdon
Catch 3: dealing with conveyor
 No releases schedule Priorities changing often Hard to estimate size of each elementWhy Scrum is not best choice
   Try KanbanSolution?
Catch 4: scrum-like
   Should always try to improveScrum-like symptoms:No retrospectives
Scrum-like symptoms:Standup-meeting as speech to PM
Code Complete         ✔  Unit Tested           ✔  Peer Reviewed         ✔  QA Complete           ✔  Documented            ...
 Pareto rule:80% of task valuetakes 20% time.Another 20% takesanother 80% of time.Scrum-like symptoms:80% done
 Try to review your process against the  agile manifesto and checklists If something is missing, think if you could  ben...
Catch 5: Scrum cargo cult
 Rethink you process: are you benefitting  from all of you tools and processes? Formal and informal retrospectives shoul...
Catch 6: Common sense bias
 Pair programming Planning pockerCommon sense bias examples
 Measure! Implement the right metricsSolution?
Catch 7: Is there anything out ofAgile?
Integration    Scope         Time      Cost        Quality   Human Resource Communications    Risk      ProcurementSCRUM t...
   Learn!Solution?
???Questions?
yuriy@silvestrov.comThank you!
Upcoming SlideShare
Loading in...5
×

Agile antipatterns (Odessa, Vinnitsa)

347

Published on

Antipatterns of Agile: how to survive - how to find out that your agile is not agile enough and what to do there.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
347
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile antipatterns (Odessa, Vinnitsa)

  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.  Based on my own and About lection team experience and a lot of interviews conducted  Have been presented in Ciklum Donetsk last month but changed a bit afterwards.
  4. 4. ⌛ < 60Time is counting
  5. 5.  Agile Scrum Kanban I will try to adaptHow many of you using
  6. 6.  Catches ◦ When size matters ◦ Agile principles violation ◦ Dealing with Conveyor ◦ Scrum-like ◦ Scrum cargo cult ◦ Common sense bias ◦ Out of Agile Q&AContent
  7. 7. Snowflake men by Max Dorofeev
  8. 8. ScrumXP Kanban Lean CrystalAgile frameworks
  9. 9. Catch 1: Size matters
  10. 10. Cockburn ScaleL L6 L20 L40 L100 The closer theE E6 E20 E40 E100 project is toD D6 D20 D40 D100 the right- top, the moreC C6 C20 C40 C100 formal process 21- 41- you need. 1-6 7-20 40 100
  11. 11.  Start creating procedures May be even to become more formal and less agile When the project and team became more mature, you could bring agility backSolution?
  12. 12.  Customer collaboration over contract negotiation Responding to change over following a plan Individuals and interactions over processes and tools Working software over comprehensive documentationCatch 2: Agile principles violation
  13. 13.  Try to keep agility inside, and be formal seen from outside Actually, it’s rather political then project management problem, and you need to solve it with the political tools Solution?
  14. 14. “DeathMarch” by Edward Yourdon
  15. 15. Catch 3: dealing with conveyor
  16. 16.  No releases schedule Priorities changing often Hard to estimate size of each elementWhy Scrum is not best choice
  17. 17.  Try KanbanSolution?
  18. 18. Catch 4: scrum-like
  19. 19.  Should always try to improveScrum-like symptoms:No retrospectives
  20. 20. Scrum-like symptoms:Standup-meeting as speech to PM
  21. 21. Code Complete ✔ Unit Tested ✔ Peer Reviewed ✔ QA Complete ✔ Documented ✔Scrum-like symptoms:No Done-Done criteria
  22. 22.  Pareto rule:80% of task valuetakes 20% time.Another 20% takesanother 80% of time.Scrum-like symptoms:80% done
  23. 23.  Try to review your process against the agile manifesto and checklists If something is missing, think if you could benefit from bringing it back.Solution?
  24. 24. Catch 5: Scrum cargo cult
  25. 25.  Rethink you process: are you benefitting from all of you tools and processes? Formal and informal retrospectives should help.Solution
  26. 26. Catch 6: Common sense bias
  27. 27.  Pair programming Planning pockerCommon sense bias examples
  28. 28.  Measure! Implement the right metricsSolution?
  29. 29. Catch 7: Is there anything out ofAgile?
  30. 30. Integration Scope Time Cost Quality Human Resource Communications Risk ProcurementSCRUM to PMBOK areas
  31. 31.  Learn!Solution?
  32. 32. ???Questions?
  33. 33. yuriy@silvestrov.comThank you!
  1. ¿Le ha llamado la atención una diapositiva en particular?

    Recortar diapositivas es una manera útil de recopilar información importante para consultarla más tarde.

×