What to do when you have more products than Scrum teams? With multiple products and a few Scrum teams. During the Meetup we gave a very brief overview of Agile Scaling Frameworks Less SAFe Spotify Nexus Scrum @ Scale. See the slidedeck for recommended training on any of these. Next, as a community we came to the conclusion that it's actually not only a bad thing to have multiple products in one team. The blog Multi Products Scrum teams at Scale you can read our conclusions about If you have Multiple products per Scrum team, what could be advantages and disadvantages for the Scrum team, the Organization and the Customer?
Read more in the blog https://xebia.com/blog/multiple-products-scrum-teams-how-do-you-deal-with-that/
Or gain deep knowledge with Scaling Frameworks trainings; an overview training or a specific framework: either Less - Nexus - Scaled Scrum - or - SAFe
https://xebia.com/academy/en/training/agile-scaling-frameworks-overview
12. Get to know each other
17
Standup
Pair up
Per pair together 6 minutes
Share both thoughts on:
What big challenge do you bring to this
gathering?
What do you hope to get from and give this
group or community?
Change from partner
13. Products versus teams
How many products do you have in your team(s)
On what criteria do you distinguish a product?
18
?
14. Scrum Guide
“The heart of Scrum is a Sprint, a time-box of one month or less
during which a "Done", useable, and potentially releasable product
Increment is created. ”
19
21. What do Scaling Frameworks have in common
Documented knowledge what works in practice around to
manage multiple teams and products.
Organize teams around value / product
Set a heartbeat to the organisation
Assumption teams > products
26
22. LeSS Framework
The end of the ‘contract game’
Product oriented
Enforces organizational change
Self-organizing
Creates team-independence
Craig Larman & Bas Vodde
27
23. Spotify Engineering Culture
Trust over control
Community over structure
What’s the minimal viable bureaucracy?
Focus on motivation
Loosely coupled, tightly aligned squads
Learning as a craftsman explicitly
addressed in Chapters and Guilds
As Spotify was organized in 2012, with
Agile coach Henrik Kniberg on board
28
24. Nexus
By Ken Schwaber, founder of Scrum
Like LeSS: Scaled Scrum is still Scrum
Limited definition of Scaling
Only gives the structure (what) but a lot
of freedom in the how in implementation
Described in the Nexus Guide:
https://www.scrum.org/resources/nexus-
guide
29
25. Scaled Agile Framework
Well maintained, great book of knowledge,
Great presentation, great overview
Appeal ‘at management level’
Pragmatic from a change point of view
Quarterly planning of increments (PI Planning)
Many formal roles
Criticism from ‘Agilists’
- Prescriptive, it is a solution vs a learning framework
- Old-school implementations
- Classic ‘more’ solution, adding complexity
30
26. Scrum at Scale
Collaboration: how do you work with
multiple/larger teams according to
Scrum@Scale?
Backlog: what is a Transformation
Backlog and how do you prioritize on a
large scale?
Measuring results: learn to measure
results in any environment, large or small.
Roles / layers of Scrum
- Scrum of Scrum Masters
- Chief Product Owner
31
27. Trainings around Scaling
Agile Scaling Frameworks overview
Certified Leading SAFe
Certified LeSS Practitioner: Principles to
Practices
Scaled Professional Scrum (Nexus)
Scrum@Scale
Continuous Delivery and DevOps
technical practices and tools to integrate
software
32