Agile Antipatterns

Antipatterns presented for discussion as part of Agile Delivery Masterclass during BelTech 2014 conference workshops

Transcript

1. Agile   Anti-patterns 1 BelTech  Conference  2014   Agile  Masterclass
2. Anti-patterns 2 Non-technical stakeholders dictating technical feasibility or ‘solutionising’
3. Anti-patterns 3 Stand-ups as simple status updates
4. Anti-patterns 4 Phased sprints approach   ‘design sprint’ ->   ‘dev sprint’ ->   ‘test sprint’
5. Anti-patterns 5 Poor quality user stories
6. Anti-patterns 6 Very long sprints with very large pieces of work – testing backloaded to the very end
7. Anti-patterns 7 Developers not allowed to talk to business, not responsible for estimates, not allowed any responsibility for low-level technical decisions
8. Anti-patterns 8 Estimates produced only by Product Owner, Architect or an other single person
9. Anti-patterns 9 Multiple Product Owners working on the same product
10. Anti-patterns 10 Stagnant technical practices
11. Anti-patterns 11 Not paying off technical debt
12. Anti-patterns 12 No retrospectives
13. Anti-patterns 13 Turning people off with too many radical changes
14. Anti-patterns 14 Ultra-detailed user stories
15. Anti-patterns 15 Scrum Master as boss - assigning tasks and giving orders rather than facilitating and coaching
16. Anti-patterns 16 Acquiring an agile process and then dictating that it can never be changed
17. Anti-patterns 17 Using an ‘agile tool’ to define the process
18. Anti-patterns 18 Product Owner == Scrum Master
19. Anti-patterns 19 Product backlog determined at outset and forever fixed
20. Anti-patterns 20 Product Owner with no authority to decide priority, change features etc (e.g. proxy PO)