Allen Hurst
Principal Consultant – Improving Enterprises
Agile Coach, Project Manager, Developer
Fightin’ Texas Aggie
Live in Houston, TX
Slide 3
Slide 3 text
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?
Slide 4
Slide 4 text
What problem are you solving?
a. support more applications?
b. deliver more, faster?
c. integrate across systems?
hard!
Slide 5
Slide 5 text
What problem are you solving?
a. support more applications?
b. deliver more, faster?
c. integrate across systems?
hard!
Slide 6
Slide 6 text
Shared Services/DevOps
Teams
Project Management/PMO
Executive
Portfolio
Mgmt
Program
Mgmt
Project
Mgmt
Metrics
Team Collaboration
Release
Mgmt
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
Scaling: support more applications
a. Support more applications
Slide 9
Slide 9 text
Scaling Adoption
1. Agile “our way”
2. Recognizing patterns
3. Coordination between teams
a. Support more applications
Slide 10
Slide 10 text
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”
Slide 11
Slide 11 text
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”
Slide 12
Slide 12 text
Utilizing shared services
a. Support more applications
2. Recognizing patterns
Slide 13
Slide 13 text
a. Support more applications
2. Recognizing patterns
Product Owner Coordination
Slide 14
Slide 14 text
Scaling: deliver more, faster
b. Deliver more, faster
Slide 15
Slide 15 text
b. Deliver more, faster
Scrum of Scrums
Slide 16
Slide 16 text
Scaling: Integrate Across Systems
c. Integrate across systems
Slide 17
Slide 17 text
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
Slide 18
Slide 18 text
Challenges with Scrum of Scrums
1. Work item management
2. Release planning
3. Cross-team collaboration
4. Managing dependencies
c. Integrate across systems
Slide 19
Slide 19 text
Work Breakdown
Slide 20
Slide 20 text
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
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
Parking Lot
c. Integrate across systems
1. Work item management
Slide 23
Slide 23 text
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
Slide 24
Slide 24 text
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
Slide 25
Slide 25 text
c. Integrate across systems
Product Coordination Team
3. Cross-team collaboration
Slide 26
Slide 26 text
c. Integrate across systems
3. Cross-team collaboration
Working Agreements
Slide 27
Slide 27 text
c. Integrate across systems
Good technical citizen
3. Cross-team collaboration
Slide 28
Slide 28 text
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
Slide 29
Slide 29 text
c. Integrate across systems
Program Management with Kanban
4. Managing dependencies
Slide 30
Slide 30 text
Scaled Agile Framework™ Big Picture
Slide 31
Slide 31 text
c. Integrate across systems
2. Release planning
Agile Release Train
Slide 32
Slide 32 text
c. Integrate across systems
2. Release planning
Agile Release Train
Slide 33
Slide 33 text
c. Integrate across systems
4. Managing dependencies
Working with Waterfall Teams
Slide 34
Slide 34 text
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”
Slide 35
Slide 35 text
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?