Team Anti-patterns - and how to resolve them

Transcript

1. Team Anti-patterns - and how to resolve them - Dev.Talk February 2016 Marcel Körtgen
2. Agenda •Patterns? Anti-pattern? •Team Anti-Patterns (selected) •Some References •Summary
3. Many (Anti-)Patterns out there...
4. http://www.antipatterns.com/thebook.htm AntiPatterns.com
5. https://dzone.com/refcardz/git-patterns-and-anti-patterns Technical...
6. http://theburningmonk.com/2015/05/craftconf15-takeaways-from-microservice-antipatterns/ For hypes...
7. http://blog.zend.com/2014/11/14/identifying-continuous-delivery- antipatterns/ For hypes...
8. http://www.slideshare.net/AliKheyrollahi/5-antipatterns-in-api-design-ddd-east-anglia-2015 ...and legacy (e.g. client/server)
9. http://www.slideshare.net/AliKheyrollahi/5-antipatterns-in-api-design-ddd-east-anglia-2015 ...and legacy (e.g. client/server)
10. https://www.blossom.co/blog/product-management-anti-patterns For management...
11. https://weisbart.com/event/scrum-gathering-2013-agile-antipatters ...and teams
12. https://keyholesoftware.com/2015/03/02/agile-team-member-anti-patterns/ ...and teams
13. http://www.slideshare.net/simonguest/presentation-antipatterns And for presentations
14. How to avoid death By PowerPoint: David JP Phillips at TEDxStockholmSalon #2/2014 Think Again And for presentations
15. http://inedo.com/release/repository Even card games. Fun!
16. What is an Anti-Pattern?
17. “A pattern that may be commonly used but is ineffective and/or counterproductive in practice.” — Wikipedia
18. https://weisbart.com/event/scrum-gathering-2013-agile-antipatters It’s not just a bad idea
19. http://martinfowler.com/bliki/AntiPattern.html It initially looks attractive...
20. http://www.slideshare.net/anm8tr/professional-javascript-antipatterns ...but turns out problematic
21. Why learn Anti-patterns? Two key elements •A repeated pattern of action that appears beneficial, but ultimately produces more bad consequences than beneficial results •A refactored solution exists that has been proven in actual practice and is repeatable
22. “Scrum is like your mother-in-law. It's constantly pointing out your shortcomings.” — Ken Schwaber
23. Team Anti-patterns (some)
24. Continuous “No Improvement” aka “Zombie Bugs” or “Constant firefighting” Smells: • A “fixed” problem rises again & again • May also be a “similar” problem rising up after the first was fixed
25. Continuous “No Improvement” aka “Zombie Bugs” or “Constant firefighting” Antidote: • “Get the basics right!” • You are fighting symptoms • Identify root cause & just fix it (no matter what) → from Agile for Humans #12: Agile Experiments with Woody Zuil [Podcast]
26. Watching the Runners aka “Maximizing capacity” or “Idle fear” Smells: • Management concern over idle developers Why bad: • “Watch the baton, not the runners”
27. Watching the Runners aka “Maximizing capacity” or “Idle fear” Antidote: • Allow slack time • Encourage pair programming • WIP limits
28. A “Bug Fixing” Sprint Smells: • You need time for your product to stabilize before a release Antidote: • Continuous Integration • Demo your product at the end of each sprint
29. Silo People aka “stove pipe” Smells: • Premature Allocation • Prioritizing stories based on team skills
30. Silo People aka “stove pipe” Why bad: • Stories will be prioritized based on the skills of the developers - not customer need • Low “bus factor”, which means bottlenecks when specialized developers are unavailable
31. Silo People aka “stove pipe” Antidote: • Prioritize stories based on product / market needs • Strong XP practices • Pair program to share knowledge • Collective Code-Ownership • Cross-functional teams
32. Summary Anti-patterns helpful because... • more easily spotting bad practices (symptoms) • better communication (defined terms) • resolving the cause (known antidote)
33. Further Reading •AntiPatterns website •The Daily WTF •The Agile Antipattern Project •Dilbert Comics
34. Thank You Time for Questions!