Agile Development Across Teams

By: Allen Hurst

Transcript

1. Coordinating Development Across Teams Allen Hurst
2. Allen Hurst Principal Consultant – Improving Enterprises Agile Coach, Project Manager, Developer Fightin’ Texas Aggie Live in Houston, TX
3. Do I use one product backlog or one per team? Do we track integration stories on the product backlog? Don’t we need more design up front? Shared services are keeping me from completing sprint deliverables We’re delivering iteratively, but we can’t integrate because the other team is waterfall Should we have one product owner or one per team? How can we have self-organizing teams but still standard processes? How do I compare velocity across my teams? Does integration happen after the sprint? Who should be invited to our scrum of scrums?
4. What problem are you solving? a.  support more applications? b.  deliver more, faster? c.  integrate across systems? hard!
5. What problem are you solving? a.  support more applications? b.  deliver more, faster? c.  integrate across systems? hard!
6. Shared Services/DevOps Teams Project Management/PMO Executive Portfolio Mgmt Program Mgmt Project Mgmt Metrics Team Collaboration Release Mgmt
8. Scaling: support more applications a. Support more applications
9. Scaling Adoption 1.  Agile “our way” 2.  Recognizing patterns 3.  Coordination between teams a. Support more applications
10. Do’s •  Minimum definition of done •  Minimum required reporting •  Recommended architecture and tools •  Prefer recommendations over mandates a. Support more applications Standardizing practices across teams 1. Agile “our way”
11. Don’ts •  Process bible •  Cookie cutter practices and architecture •  Compare team velocity •  Implement standards at the expense of self-organization a. Support more applications Standardizing practices across teams 1. Agile “our way”
12. Utilizing shared services a. Support more applications 2. Recognizing patterns
13. a. Support more applications 2. Recognizing patterns Product Owner Coordination
14. Scaling: deliver more, faster b. Deliver more, faster
15. b. Deliver more, faster Scrum of Scrums
16. Scaling: Integrate Across Systems c. Integrate across systems
17. App 1 The Enterprise Challenge App 5 App 3 App 4 App 2 MT 2 MT 1 DB 1 DB 2 Team Team Team Team Team Team Team Program c. Integrate across systems
18. Challenges with Scrum of Scrums 1.  Work item management 2.  Release planning 3.  Cross-team collaboration 4.  Managing dependencies c. Integrate across systems
19. Work Breakdown
20. Work Breakdown c. Integrate across systems 1. Work item management Feature (Epic) Story Business Activity (Theme) Feature (Epic) Feature (Epic) Feature (Epic) Feature (Epic) Story Story Story Story Story Story Story Story Story Story Story Story Story Story Story Team 1 Team 2 Team 3
22. Parking Lot c. Integrate across systems 1. Work item management
23. The Increment c. Integrate across systems 2. Release planning Increment Features Composed of Stories Added to Sprint Worked by Build Team Creates Promoted to Release Becomes
24. c. Integrate across systems Roles/Responsibilities/Personnel 3. Cross-team collaboration Chief PO PO PO PO 1  Backlog/Program   Team 1 PO Team 2 PO Team 3 PO 1  Backlog/Team   SoS  PO   App 1 PO App 2 PO App 3 PO 1  Backlog/Product   SoS  PO  
25. c. Integrate across systems Product Coordination Team 3. Cross-team collaboration
26. c. Integrate across systems 3. Cross-team collaboration Working Agreements
27. c. Integrate across systems Good technical citizen 3. Cross-team collaboration
28. The Increment c. Integrate across systems 2. Release planning Increment Features Composed of Stories Added to Sprint Worked by Build Team Creates Promoted to Release Becomes
29. c. Integrate across systems Program Management with Kanban 4. Managing dependencies
30. Scaled Agile Framework™ Big Picture
31. c. Integrate across systems 2. Release planning Agile Release Train
32. c. Integrate across systems 2. Release planning Agile Release Train
33. c. Integrate across systems 4. Managing dependencies Working with Waterfall Teams
34. c. Integrate across systems 4. Managing dependencies How much DUF is enuf? “As little as possible while still enabling integration at the next sprint boundary”
35. Do I use one product backlog or one per team? Do we track integration stories on the product backlog? Don’t we need more design up front? Shared services are keeping me from completing sprint deliverables We’re delivering iteratively, but we can’t integrate because the other team is waterfall Should we have one product owner or one per team? How can we have self-organizing teams but still standard processes? How do I compare velocity across my teams? Does integration happen after the sprint? Who should be invited to our scrum of scrums?
36. Questions? Discussion
37. Resources
38. Thanks! •  http://ahurst.com •  @allenhurst •  allen@improvingenterprises.com •  http://improvingenterprises.com