streamlining of an organization - scrum with multiple teams (seacon 2013)
DESCRIPTION
These are the slides from my identically named session at the SEACON 2013 conference in Hamburg, GermanyTRANSCRIPT
Streamlining of an OrganisationScrum with multiple teams
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Initial Situation
What are my people working at?
Orientation
When will the next features be delivered?
Which features will that be?
Delivery
Why isn’t that feature ready yet?
Delay
Why do I get deceptive answers?
Deception
“Us” and “Them”
Teams
iOS Android
Server Billing & Monitoring
Website
Release Timeline
iOS AndroidServer
Billing & MonitoringWebsite
Idea to Product - so far
Grab a developer who’s not fast enough to escape
ToDo (2) WIP (4) Deploy (8)Backlog
Kanban
Are we doing the right thing?
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Experiment
Small Feature
Prototype Team
iOS Android ServerBilling & Moni-toring
Hybrid
Co-location
Scrum Basics Workshop
Scrum by the Book
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
“We have never been that fast”
probably because we planned for the first time
“IT delivered promised scope in time”
this has never happened before!
“I want all other engineers work in Scrum teams
from next week”
CEO Approval
Don’t be hasty
Let it grow
Switch whole IT to Scrum
Teams (Wishful Thinking)
iOS Android
Server Billing & Monitoring
Website
iOS Android
Server Billing & Monitoring
Website
iOS Android
Server Billing & Monitoring
Website
Issue: Skills
Teams (Reality)
iOS Android
Server Billing & Monitoring
iOS Android
Server
Billing & Monitoring
Website
Team Identity
Issue: IT-Head
Issue: Adhoc-Tasks
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Product Decision Process
Idea to Product - first try
Company Backlog
Idea Backlog
Scrum Teams
CompanyStrategy
Entries need to be- decided- prepared- prioritized
pull
pull
pull
pull
ProductCircle
Members- CEO- CMO- CTO- Head of Product
Tasks- decide follow up (idea)- ask biz for preparation- Give rough estimate (S-XL)- Move to Company backlog- Prioritize within CB
meets once a week
Idea to Product - currently
Company Backlog
Scrum Teams
CompanyStrategy
Entries need to be- decided- prepared- prioritized
pull
pull
pull
pull
ProductCircle
Members- Head of Product- POs- Marketing
Tasks- decide follow up- Get estimate (S-XL)- Create Epic- Prioritize Epic (with Mgmt)
meets once a week
Head ofProduct
Prepare
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Release Heartbeat
Reliable Releasedates
Sprint 1
Sprint2
Sprint3
Sprint 1
Sprint2
Sprint3
Sprint 1
Sprint2
Sprint3
GreenRelease Yellow
Release
RedRelease
Synchronize Teams
SprintPlanning
Team 1
...
One overall, feature-
based review
with the whole
company
SprintPlanning
Team 2
SprintPlanning
Team n
Release Plan
Release Matrix - First Try
Company Backlog
Team 1
Team 2
Team 3
Team 4
Team 5
Sprint1
Sprint1
Sprint1
Sprint2
Sprint3
Sprint2
Sprint2
Sprint3
Sprint3
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Release Matrix - first try
Company Backlog
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Epic
Team 1
Team 2
Team 3
Team 4
Team 5
Sprint1
Sprint1
Sprint1
Sprint2
Sprint3
Sprint2
Sprint2
Sprint3
Sprint3
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Adressing Bugs
Bug Smashing Sprint
Daily Bug Standup
Agenda
Initital Situation
Experiment
Analyze & Change
Product Decision Process
Heartbeat
Bugs
Next steps
Next Steps
Quality
PO-Empowerment
Marketing & Sales Integration
Product Teams
Billing & Monitoring
iOS Android
Server
Website
iOS Android
Server
Online Product
Sven RöpstorffAgile Project Manager & Coach
Email: [email protected]: @oedel
Agile Lean Europe (ALE)
Get In Touch