Agile antipatterns (Odessa, Vinnitsa)
Download as PPTX, PDF0 likes537 views
The document discusses various agile antipatterns identified by Yuriy V. Silvestrov, highlighting issues such as the impact of project size on process formality, violations of agile principles, and common symptoms in scrum practices. Solutions include fostering customer collaboration, conducting retrospectives, and measuring outcomes effectively. The author emphasizes the importance of adapting agile practices according to team maturity and project requirements.
Agile antipatterns (Odessa, Vinnitsa)
- 1. Catch Agile Antipatterns of using Agile: how to survive by Yuriy V. Silvestrov
- 2. About me Yuriy V. Silvestrov 10+ years record in IT, 8+ years devoted to managing projects. Now working for Ciklum, managing a team of 30+ persons making different software for Danish financial organizations. Please visit my website http://yuriy.silvestrov.com for more info or contact me at yuriy@silvestrov.com.
- 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. ⌛ < 60 Time is counting
- 5. Agile Scrum Kanban I will try to adapt How many of you using
- 6. Catches ◦ When size matters ◦ Agile principles violation ◦ Dealing with Conveyor ◦ Scrum-like ◦ Scrum cargo cult ◦ Common sense bias ◦ Out of Agile Q&A Content
- 7. Snowflake men by Max Dorofeev
- 8. Scrum XP Kanban Lean Crystal Agile frameworks
- 9. Catch 1: Size matters
- 10. Cockburn Scale L L6 L20 L40 L100 The closer the E E6 E20 E40 E100 project is to D D6 D20 D40 D100 the right- top, the more C C6 C20 C40 C100 formal process 21- 41- you need. 1-6 7-20 40 100
- 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 back Solution?
- 12. Customer collaboration over contract negotiation Responding to change over following a plan Individuals and interactions over processes and tools Working software over comprehensive documentation Catch 2: Agile principles violation
- 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. “DeathMarch” by Edward Yourdon
- 15. Catch 3: dealing with conveyor
- 16. No releases schedule Priorities changing often Hard to estimate size of each element Why Scrum is not best choice
- 17. Try Kanban Solution?
- 19. Should always try to improve Scrum-like symptoms: No retrospectives
- 20. Scrum-like symptoms: Standup-meeting as speech to PM
- 21. Code Complete ✔ Unit Tested ✔ Peer Reviewed ✔ QA Complete ✔ Documented ✔ Scrum-like symptoms: No Done-Done criteria
- 22. Pareto rule: 80% of task value takes 20% time. Another 20% takes another 80% of time. Scrum-like symptoms: 80% done
- 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. Catch 5: Scrum cargo cult
- 25. Rethink you process: are you benefitting from all of you tools and processes? Formal and informal retrospectives should help. Solution
- 26. Catch 6: Common sense bias
- 27. Pair programming Planning pocker Common sense bias examples
- 28. Measure! Implement the right metrics Solution?
- 29. Catch 7: Is there anything out of Agile?
- 30. Integration Scope Time Cost Quality Human Resource Communications Risk Procurement SCRUM to PMBOK areas
- 31. Learn! Solution?
- 32. ??? Questions?