5 Things You Need To Do To Scale Your Agile Adoption  Organizations can improve their Agile scaling efforts by focusing on 5 common challenges: the way teams are chartered, how people come together to form teams, how their values and working agreements are protected, how they are helped to remove impediments, and how they learn to improve what they deliver based on feedback. These common challenges can derail and distract the efforts of the organization to reap the benefits of agile, empirical product delivery. This presentation discusses these challenges and strategies organizations can use to overcome them. Structure of the Session  Manage your portfolio with Outcomes (not Output) Help teams and stakeholders to self-organize Support and protect Agile values with strong leadership Systematically remove sources of waste and delay faced by Agile teams Measure and improve value delivered with frequent feedback (Inspect and Adapt)  Learning Outcomes  To understand why focusing on outcomes delivers better results than focusing on outputs. To learn how to switch to using an outcome-based approach to portfolio management. To learn how to help teams come to agreements on how they will work with each other and stakeholders. To learn what leaders must do to support and protect Agile teams. To understand what support Agile teams need from their organization. To understand how measuring value delivered helps teams learn where they need to improve.

1. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved@ScrumDotOrg 1
Kurt Bittner | kurt.bittner@scrum.org | @ksbittner
5 Things You Need To Do
To Scale Your Agile Adoption

2. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
5 Things You
Need to do to
scale your
Agile Adoption
2
1. Support and protect agile values with
strong leadership
2. Help teams and stakeholders to self-
organize
3. Manage toward Outcomes (not Output)
4. Systematically remove waste
5. Improve through frequent feedback

3. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 3
“Whether you think you can,
or you think you can’t,
you’re right!”
- Henry Ford
Support and protect Agile values with strong
leadership

4. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Consider this…
4
https://www.millerheimangroup.com/blog/2016/10/use-digital-disruption-open-doors-sales-efforts/

5. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
And this…
5

6. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 6
One person’s threat
is another person’s
opportunity

7. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
7
CustomersCompetitors
Organizations must become more responsive to survive

8. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Why is change hard?
8
“Culture eats strategy for
breakfast.”
- Peter Drucker
Agile

9. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 9
“People don't resist change.
They resist being changed.”
– Peter M. Senge

10. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
What people do
is more important than
What people say
10
What Shapes Culture?
https://si.wsj.net/public/resources/images/RV-AN417_CUBICL_P_20140509201519.jpg

11. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Leaders make the difference
11
Leaders help steer toward shared goals
Leaders make it safe to change
Leaders model the change

12. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 12
2
“If one does not know to which port one is sailing, no
wind is favorable.”
- Seneca
Help teams and stakeholders to self-organize

13. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 13
“The organizational structure we use today is
over 100 years old.
It was not built to be fast and agile.”
- Dr. John Kotterhttps://www.youtube.com/watch?v=Pc7EVXnF2aI

14. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
What drives creative work?
14
https://www.youtube.com/watch?v=KgGhSOAtAyQ

15. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
The Traditional Organization
15
To Become Agile, Invert The Organization
The Agile Organization
Customers
Customers
Delivery Teams
Managers
CEO
CEO
VPs
Middle
Managers
Line Managers
Employees

16. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Helping everyone to self-organize unleashes energy, creativity
16
Development
Team
16
Stakeholders
Scrum
Master
Product
Owner
Mutual respect
Shared values, goals, commitments
Shared working agreements

17. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 17
3
“One must, from time to time, attempt things that are
beyond one’s capacity.”
= Pierre-August Renoir
Manage toward Outcomes
(not Output)

18. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Most features don’t improve outcomes
Source: http://www.exp-platform.com/Documents/2015%20Online%20Controlled%20Experiments_EncyclopediaOfMLDM.pdf
Improves
outcome
nothingthings
worse

19. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Beware of HiPPOs!
https://s-media-cache-ak0.pinimg.com/originals/67/f3/05/67f3053febdf5048ef696e87537c9e55.jpg
Highly Paid Person’s Opinions

20. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 20
An Outcome is some state
experienced by the user of a Product.

21. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 21
Mind The Gap
Current Experience
Desired Outcome
Satisfaction
Gap
Opportunity
=
Value of Closing
Satisfaction Gap
Another technique: Empathy Mapping
https://www.uxpin.com/studio/blog/the-practical-guide-to-empathy-maps-creating-a-10-minute-persona/
Persona

22. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 22
4
“Master technique, then forget it.”
- Matsuo Basho
Systematically remove waste

23. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 23
Why is scaling hard?
Output
Sprints
Team 4
Team 5
Team 1
Team 2
Team 3

24. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 24
Cross-Team Dependencies
Team 4
Team 5
Team 1
Team 2
Team 3

25. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Where does waste occur?
Customer
Idea
Everywhere!
Understand
Needs
Wait
For
Feedback
Wait
For
Approval
Architect
Solution
Excessive
Design
waste
Review/
Approval
Code
Multi-
Tasking
inefficiency
Over-
engineering
Test
Mis-
Understood
Requirements
Test
Env.
Set-up
Defect
Fixing
Deploy
Deployment
Failures
Config.
Errors

26. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Outcome: ? ₹
How effective are most organizations?
26
WHAT
HOWWHO
AGILITY
Input (Budget): 8,000 ₹
35%
Building the Right Features
50%
Effective
Collaboration 30%
Building New Features

27. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
What Kinds of Support Do Agile Teams Need?
27
https://www.scrum.org/resources/scrum-studio-model-innovation

28. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 28
5
“Good judgment comes from experience, most of
which comes from bad judgment.”
- anonymous
Improve through frequent feedback

29. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 29
2 challenges:
(1) Build the right thing
(2) Build the thing right

30. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 30
(1) Build the right thing

31. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 31
Product Owner
Idea!
Customer
Product Releases
Economic Value,
Feedback
?

32. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Expressing Hypotheses
Adapted from Gothelf and Seiden: Lean UX
We believe [doing this] for [these
people] will achieve [this outcome] We
will know that this is true when we see
[this measurement] changed
Feature
Persona
Outcome
Measure

33. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Using Outcomes to plan Sprints
33
Product
Owner
Development
Team
Here’s the
outcome I’d like
us to achieve this
Sprint …
Great! We think
that if we build
these PBIs that
we can achieve
that outcome…
Scrum
Master

34. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Using Outcomes to focus Sprint Reviews
34
Product
Owner
Development
Team
What were the
results of our
experiments?
What did we
learn?
Scrum
Master

35. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 35
(2) Build the thing right

36. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Use Retrospectives to ”Build the thing right”
36
Product
Owner
Development
Team
What did we
learn?
What do we need
to do to get
better?
Scrum
Master

37. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
5 Things You
Need to do to
scale your
Agile Adoption
37
1. Support and protect agile values with
strong leadership
2. Help teams and stakeholders to self-
organize
3. Manage toward Outcomes (not Output)
4. Systematically remove waste
5. Improve through frequent feedback

38. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Questions?

39. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved 39
Improving the Profession of
Software Delivery

40. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
The lightweight framework for scaling Scrum
by Scrum.org
• Nexus –noun
ˈnek-səs
: a relationship or connection between people or
things
• For 3 to 9 teams (Nexus+ for more than 9 teams)
• It’s Scrum with extensions
(Events, Roles, etc.)
40
Nexus™
https://www.scrum.org/resources/nexus-guide

41. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Recently Published – December 2017
• Provides techniques and practices for scaling
Scrum and adopting Nexus in your organization
• Helps you build on your Agile knowledge to apply
Scrum in larger and more complex situations
• Walks through different challenges and scenarios
organizations face when scaling Scrum through a
case study
https://www.scrum.org/Resources/The-Nexus-Guide

42. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Coming soon…
• Cutting-edge guidance for product owners and
other team members: from product vision to first
sprint
• A powerful approach to measuring product value
and bringing greater empiricism to development
• Practical resources for product backlog
management as well as release management

43. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Scrum.org is a community. Connect.
Twitter
@scrumdotorg
LinkedIn
LinkedIn.com
/company/Scrum.or
g
Facebook
Facebook.com
/Scrum.org
Forums
Scrum.org
/Community
RSS
Scrum.org/RSS

44. v 3.4 © 1993 – 2018 Scrum.org All Rights Reserved
Thank You!
44