One team or a handful of teams may be able to deliver small systems. Large complex systems require teams of teams to deliver significant features.
How can companies benefit from “the team effect” at scale?
Scaling agile presents three main challenges:
+coordinating work across teams
+integrating work across teams
+maintaining technical integrity of the system.
In this presentation, I share principles and practices to help you scale your agile teams for optimum success.
-------------------------------------
About Esther Derby
I consult with you to help you develop a holistic view of your organization and take action to achieve optimum success. I coach you to boost your effectiveness and confidence as a manager, and I deliver workshops that bring insights to life, build skills, and engage your people in learning.
If you have questions about my services, contact me to schedule a free initial conversation. I'd be delighted to share my thoughts with you and learn about your company.
Phone: +1 612.239.1214
Email: esther@estherderby.com
Visit my website to learn more about what I do, browse my blog and sign up for my free email newsletter.
1. Agile Teams at Scale:
Beyond Scrum of Scrums
Esther Derby
esther@estherderby.com
+1 612 239 1214
@estherderby
www.estherderby.com
2. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
One team or a handful of teams may be able to deliver
small systems. Large complex systems require teams of
teams to deliver significant features.
How can companies benefit from “the team effect” at
scale?
3. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Three main challenges in scaling teams:
coordinating work across teams
integrating work across teams
maintaining technical integrity of the system
4. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Principles: Guide stars for scaling team-based work.
Practices: Social and technical practices that enable team-
based work.
Pathways: Steps to get from here to there.
5. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Principles to Address
COORDINATION
• Organize people and work to reduce coordination overhead
• Analyze demand
• Context teams over component teams
• Minimize product dependencies
• Aim for flow
• Build in slack and redundancy
6. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Teams share...
a compelling work goal
responsibility and accountability
an approach to work
teams have...
complementary skills
five-seven members
history
Teams are one sort of goal-oriented social unit.
Teams can form the building blocks for larger goal-oriented social units.
7. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Teams offer possibilities that functional or component
work groups do not.
flexibility
learning
engagement
responsibility
9. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Scrum of Scrums can work with a small number of teams working
within the same context.
13. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
A large system may have several contexts. (Think of context as a feature
group, for example “Student Financial Aid” in a system to track financial
aspects of students registered at a university.)
Form cross-functional, multi-skilled teams within contexts.
15. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Principles to Address
INTEGRATION
•Make cross team and cross context communication
explicit
•Teams that integrate together plan together
•Lateral links
•Design for early learning
16. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Make communication across context boundaries explicit. Use
integrating linkers to agree how to handle the interface and integration
between contexts. Integrating linkers should also agree on and write
acceptances tests that confirm integration across boundaries.
17. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Principles to Address
TECHNICAL INTEGRITY
•Global and local standards
•Technical stewards
•T-shaped people
18. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
When several teams touch the code for services or component, add
Component Stewards or Component Steward Teams.
Component Stewards work to maintain the integrity of components.They
review code, coach, mentor, develop standards and provide guidance to teams.
19. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Large systems usually need both integrating linkers and Component
Stewards.
20. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Tech Councils, made up of integrating linkers, component stewards,
and test experts attend to the integrity of the whole system.
Product Councils look after product integrity.
Define decision boundaries for each sort of group.
21. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Technical Practices
Continuous integration (CI) within context
Integration across contexts at some other interval (keeping in
mind “avoid late learning”)
Mutually agreed upon and developed automated test across
context boundaries
Architectural, UI & coding standards
Technical reviews
22. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Social Practices
Scrum of Scrums within context to surface impediments
Integrating links (keeping in mind “avoid late learning”)
Decision boundaries
Component stewards or teams
Tech councils
Product councils
Planning
Story Mapping
Central AND Local
23. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
•Lateral structures handle coordination and integration.
People close to the issues have both the knowledge and
means to make decisions.
•Scrum of scrums handles impediments.
•Information flows across and through, rather than up and
down.
24. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
How do we get there?
Mid-level planning
Demand analysis
Removing technical dependencies
Smaller chunks
Pathways
28. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
It’s not simple
It’s not easy
There is no one right way
There is no prescriptive plan
You won’t get there in one giant leap
29. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
It is possible
You will get there by adapting, iterating, learning
You will create a more flexible organization
You will increase the speed and ease of communication
You will unleash potential
30. +1 612 239 1214 || esther@estherderby.com || www.estherderby.com || twitter: @estherderby || (c) 2013 Esther Derby
Some useful resources from within the software domain:
Domain Driven Design by Eric Evans
Practices for Scaling Lean & Agile Development by Craig Larman and BasVodde
...and from the field of Organization Development and Design
Images of Organization by Gareth Morgan
DesigningTeam-Based Organizations by Mohrman, Cohen, and Mohrman
Creating Strategic Change by William Pasmore
Leadership and the New Science by Meg Wheatley
Resources and References