Download to read offline
Uploaded byAskhat Urazbaev
Scaling agile
The document details strategies for scaling agile practices, emphasizing feature teams that minimize bureaucracy and enhance collaboration across various components. It discusses bottlenecks in delivery, the importance of managing dependencies, and techniques for improving team performance through effective practices and resource management. Additionally, it highlights the role of communication, early integration, and feedback in agile project success.
More Related Content
More from Askhat Urazbaev
Scaling agile
- 1. Scaling Agile Askhat Urazbaev AgileCoach ScrumTrek
- 2. Askhat Urazbaev • ScrumTrek •Agile Coach • CEO • In the past • Programmer, manager, process architect
- 3.
- 4.
- 5. Front End Back End Testers Architect OPS 6ppl 8 ppl 4 ppl Boss
- 6. Front End Back End Testers Architect OPS 6ppl 8 ppl 4 ppl BossToo long!
- 7. Why so long? Product Queuehere Queue here
- 8. Product Input > output Nolife here
- 9. Feature team • Mutualhelp • Early integration • Fast defect fixing • No beurocracy • Минимум бюрократии Size: 7±2
- 10. Boss Feature Team 1Feature Team 2 Feature Team 3 Architect Poor quality! I cannot control everything
- 11. Boss Feature Team 1Feature Team 2 Feature Team 3 Architect
- 12. Virtual Team • Membersof different teams • Meet around problem – Architecture, infrastructure, testing … • Typically – PO sync – SM/TL sync
- 13.
- 14. Flow Design Web Core Lib Backend Video Encoding iOSAndroidWinPhone Testing
- 15.
- 16. Feature Team Stack Android iOS C++ ObjC Video Java JavaScript HTML/CSS Ruby/Pyth on
- 17. Feature Team wouldbe… • Too large • Hard to help each other • Hard to deliver in a sprint
- 18. Where’s bottleneck? Design Web Core Lib Backend Video Encoding iOSAndroidWinPhone Testing Bottleneck
- 19.
- 20.
- 21.
- 22. Theory of constraint •Identify the constraint • Exploit the constraint • Subordinate & synchronize to the constraint • Elevate the performance of the constraint
- 23. Identify Type I • Fastresponse • Hardwork & Overtimes • No time for quality Type II • Waiting for result • Long queue of requests from other teams
- 24. Exploit • Transfer allpossible work to other teams • Get rid of unnecessary meetings • Get help for administrative work
- 25. Subordinate • Decrease plansto constraint
- 26.
- 27. Elevate • Hire andeducate
- 28.
- 30. “Integration” team • Cross-component team •Where rework is maximum • SWAT-team Size: 7±2
- 31. Backlog structure Integration features ~30% of backlog Team 1 Team 2 Team 3
- 32. Managing delivery team structure •Split into value streams • Find bottleneck • Cross-system and cross-component team where rework is maximum • Focus on the next constraint
- 33.
- 34.
- 35. Client and serviceteams Product Value User story, CR, Bug, Feature (but not task) ServiceClient
- 36.
- 37.
- 38.
- 39. Pairing story: GetFrom/Give To • Client: GetFrom • Service: GiveTo • Use acceptance criteria • Don’t use inside of team • Sync by dates and sprintshttp://blog.ciber.com/2013/planning-and-managing-dependencies-and-risks-in-agile/ As a Systems Engineer, I want to get a performance report from Vendors A,B, and C, so that I can determine if their software’s UI response time will meet our .5 second threshold.
- 40.
- 44. You are AgileCoach. Team B have commited new feature and broke team А’s functionality You can visit one retro. Which team retro would you visit first? A. Team A B. Team B C. Joint retro of А & B
- 45. “Self-defense” It is team responsibilityto cover its own code with tests
- 46.
- 47. In the middleof the sprint people from another teams bring in new urgent tasks. You could help but it will broke your own commitment. What would you do? A. Help immediately B. Move task to the next sprint
- 48.
- 50.
- 51. Managing urgent workin scrum • Don’t care. It just lows down your velocity • Allocate a budget • Have a person on duty
- 52. Policy • Request is#1 priority • Request is get fixed by members of both teams in 1 sprint • Request is considered as done if it is integrated, tested, all bugs are fixed and closed
- 53. 4 “keystone habits”(by Ahmed Sidky) 1. Communicating and collaborating 2. Deliver in evolutionary slices 3. Integrate as early as possible 4. Gather feedback from multiple levels as early as possible “Decentralized Control”
- 54.