Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Scaling Agile without frameworks
by @jmbeas
23/Nov/2015
TEAM
Product
Owner
Product
Backlog Product
Increment
Feedback
1 team & 1 product
2 teams & 2 products
# of teams
#ofproducts/projects
1
1
2
2
N teams & N products
# of teams
#ofproducts/projects
1
1
2
2
N
N
x N
1 team
per product
1 team & 2 products
1 team & 3 products
How many
products per
product owner
are feasible?
On how many products can
one team work effectively?
1 team & N products
The more
number of POs
the more
coordination is
needed.
Too many context switching
lowers productivity.
1 team & N products
POs and Teams need focus to do their job.
- Small projects are easier to schedule.
- Don’t split teams...
# of teams
#ofproducts/projects
1
1
2
2
N
N
x N
1 team & N products
FOCUS IS THE LIMIT
2 teams & 1 product
TEAM A
TEAM B
Dependencies
will become
impediments
between
teams.
A new risk
activity appears:
integra...
3 teams & 1 product
TEAM A
TEAM B
How many
teams can a
PO attend
effectively?
How many projects can
be integrated without ...
TEAM A
TEAM B
TEAM C
N teams & 1 product
You’ll need to
synchronize
deliveries of all
teams.
You’ll need a
strategy to div...
# of teams
#ofproducts/projects
1
1
2
2
N
N
x N
FOCUS IS THE LIMIT
N teams & 1 product
TEAM A
TEAM B
TEAM C
INDEPENDENCY I...
REMEMBER: 9 women can’t have a baby in 1 month.
- Divide your product in other independent sub-products.
- Scrum of scrums...
DISCLAIMER
This approach only considers
Delivery processes, not Discovery
You can use Lean Startup, Design Thinking,
Agile...
AND REMEMBER…
Jf you want to stay Agile,
check with the Agile Manifesto.
But if you still want a framework…
Scrum-based:
- SAFe : http://scaledagileframework.com/
- Nexus : https://www.scrum.org/...
Thank you!
hola@jmbeas.es
@jmbeas
http://linkedin.com/in/jmbeas
Upcoming SlideShare
Loading in …5
×

Scaling Agile without frameworks

2,104 views

Published on

You don't need to start scaling using a framework. Actually it's better to gain experience understanding the forces that won't let you scale calmly.

Published in: Business

Scaling Agile without frameworks

  1. 1. Scaling Agile without frameworks by @jmbeas 23/Nov/2015
  2. 2. TEAM Product Owner Product Backlog Product Increment Feedback 1 team & 1 product
  3. 3. 2 teams & 2 products # of teams #ofproducts/projects 1 1 2 2
  4. 4. N teams & N products # of teams #ofproducts/projects 1 1 2 2 N N x N 1 team per product
  5. 5. 1 team & 2 products
  6. 6. 1 team & 3 products How many products per product owner are feasible? On how many products can one team work effectively?
  7. 7. 1 team & N products The more number of POs the more coordination is needed. Too many context switching lowers productivity.
  8. 8. 1 team & N products POs and Teams need focus to do their job. - Small projects are easier to schedule. - Don’t split teams too early/late: look at their cycle time. - Don’t overflow POs. If needed, create a Product Management Team.
  9. 9. # of teams #ofproducts/projects 1 1 2 2 N N x N 1 team & N products FOCUS IS THE LIMIT
  10. 10. 2 teams & 1 product TEAM A TEAM B Dependencies will become impediments between teams. A new risk activity appears: integration.
  11. 11. 3 teams & 1 product TEAM A TEAM B How many teams can a PO attend effectively? How many projects can be integrated without a significant quality degradation? TEAM C
  12. 12. TEAM A TEAM B TEAM C N teams & 1 product You’ll need to synchronize deliveries of all teams. You’ll need a strategy to divide your product among your teams.
  13. 13. # of teams #ofproducts/projects 1 1 2 2 N N x N FOCUS IS THE LIMIT N teams & 1 product TEAM A TEAM B TEAM C INDEPENDENCY IS THE LIMIT
  14. 14. REMEMBER: 9 women can’t have a baby in 1 month. - Divide your product in other independent sub-products. - Scrum of scrums improve communication between teams. - Release train synchronizes all teams although it can slow the whole production. - Automate integrations. N teams & 1 product
  15. 15. DISCLAIMER This approach only considers Delivery processes, not Discovery You can use Lean Startup, Design Thinking, Agile Inceptions, User Story Mapping… any technique to DISCOVER what you think your product is.
  16. 16. AND REMEMBER… Jf you want to stay Agile, check with the Agile Manifesto.
  17. 17. But if you still want a framework… Scrum-based: - SAFe : http://scaledagileframework.com/ - Nexus : https://www.scrum.org/Resources/The-Nexus-Guide - Less : http://less.works/ Kanban-based: - ESP : http://www.djaa.com/introducing-enterprise-services-planning
  18. 18. Thank you! hola@jmbeas.es @jmbeas http://linkedin.com/in/jmbeas

×