Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
© 1993 – 2017 Scrum.org All Rights Reserved@ScrumDotOrg , @DevOpsInstDavid West – Jayne Groll
SCRUMOPS
© 1993 – 2017 Scrum.org All Rights Reserved 2
Improving the Profession of
Software Delivery
© 1993 – 2017 Scrum.org All Rights Reserved
3© 1993-2017 Scrum.org, All Rights Reserved
1,800,000+ Assessments Taken
17,000+ Professional Scrum Product Owners
4,000+ Professional Scrum Developers
105,000+ Professional Scrum Masters
The Home of Scrum
90% Agile Teams Use Scrum
189 Professional Scrum Trainers
Over 83,000 Taught
Americas, Europe, Africa, Oceania & Asia
© 1993 – 2017 Scrum.org All Rights Reserved 4
There is no such thing as ScrumOps
© 1993 – 2017 Scrum.org All Rights Reserved
And That Means..
5
© 1993 – 2017 Scrum.org All Rights Reserved
At the Heart of the Super Nova
6
Customer
needs change
Frequent
adaptation is
essential
The Firm
Customer The Firm
Customer
This radical shift in focus
is leading to vast economic, social and political change
© 1993 – 2017 Scrum.org All Rights Reserved
But Customers Are NOT predictable
7
© 1993 – 2017 Scrum.org All Rights Reserved 8
Decision-Making in an Uncertain World
Source: Stacey RD. Strategic Management and
Organizational Dynamics: The Challenge of
Complexity. 3rd ed. Harlow: Prentice Hall, 2002.
An Empirical
Approach it
Required..
© 1993 – 2017 Scrum.org All Rights Reserved
Deploy and Measure
Build at Least Part Of It
EvaluatePossible Solutions
Understand Desired Outcomes
Identify an Opportunity
9
An Empirical Approach - Inspect and Adapt (Transparency)
Continue
learning
1
2
3
4
5
© 1993 – 2017 Scrum.org All Rights Reserved 10
But….
© 1993 – 2017 Scrum.org All Rights Reserved
Where do you sit ?
11
High Medium Low
Deployment
Frequency
On Demand 1 per week to 1 per
month
1 per week to 1 per
month
Lead time for
change
< 1 Hour 1 Week to 1 Month 1 Week to 1 Month
Mean Time To
Recovery
< 1 Hour < 1 Day 1 day to 1 week
Change Failure Rate 0 – 15% 0 – 15% 31-45%
2017 State of DevOps Report -
DORA
Note – Low performers were lower on
average, but had the same medium
© 1993 – 2017 Scrum.org All Rights Reserved
But maybe there is a problem…
12
Delivery
Speed
Time
Yearly
Quarterly
Monthly
Weekly
Daily
Hourly
Minutly
1970 1980 1990 2000 2007 2010 2017
Desired Release Ability
© 1993 – 2017 Scrum.org All Rights Reserved
And we budget…
13
"Uncertainty—in the economy,
society, politics—has become so
great as to render futile, if not
counterproductive, the kind of
planning most companies still
practice: forecasting based on
probabilities.”
Peter Drucker, 1992 The Wall Street
Journal
© 1993 – 2017 Scrum.org All Rights Reserved
Shouldn’t It Be Simple ?
14
© 1993 – 2017 Scrum.org All Rights Reserved
OK, Someone Has To Pay For It
15
© 1993 – 2017 Scrum.org All Rights Reserved
And it might be in an existing organization
16
© 1993 – 2017 Scrum.org All Rights Reserved
Which in fact might feel like….
17
© 1993 – 2017 Scrum.org All Rights Reserved 18
Let’s play a thought experiment…
What does a
customer centric
organization look
like ?
© 1993 – 2017 Scrum.org All Rights Reserved
It All Begins With Agile Teams
19
© 1993 – 2017 Scrum.org All Rights Reserved
Shouldn’t It Be Simple ?
20
© 1993 – 2017 Scrum.org All Rights Reserved
The Reality of Scrum is…
21
Water Scrum Fall
© 1993 – 2017 Scrum.org All Rights Reserved 22
Not Surprising Really…
Project Management and funding
lifecycles add complexity
Service Management and
Release Process are designed
to slow stuff down
© 1993 – 2017 Scrum.org All Rights Reserved 23
Organizations are not built to support an empirical approach
© 1993 – 2017 Scrum.org All Rights Reserved
• Legacy –
• Evolved complexity of the software / systems
• People
• Cultural norms, silos, management traditions and finance :-)
• Market
• Pressure on short term needs and lack of understanding by owners
24
Traditional Organizations…
© 1993 – 2017 Scrum.org All Rights Reserved 25
Inspect
Frequently
Release
Frequently
Scrum has always focused on releasing software to learn
• Release Frequently
• Sprint review IS NOT a release gate
• Professional Scrum requires technical excellence
• Scrum aspires to DONE = Released
• Inspect Frequently
• PBI’s should include the way to measure value
• Measurement is required to be empirical
© 1993 – 2017 Scrum.org All Rights Reserved
•At the Agile 2008 conference Andrew Clay Shafer and Patrick Debiosdiscussed ‘Agile Infrastructure’
•Which led to DevOps Days in Belgium in 2009
26
DevOps Came From Agile
DevOps
Agile
© 1993 – 2017 Scrum.org All Rights Reserved 27
Initial Focus Was To Solve the Scrum / Agile Fall Problem
• Applying Agile development approach to release management and infrastructure
• Taking the practices of Continuous Integration and adding a deployment orientation
• Led to Continuous Delivery
Scrum Fall
© 1993 – 2017 Scrum.org All Rights Reserved 28
But this problem is much harder than it looks
• Operations are focused on stability and TCO
• Running IT has lots of moving parts (other software)
• What about Helpdesks, Security, Infrastructure vendors, etc..Inspect
Frequently
Release
Frequently
Operations
© 1993 – 2017 Scrum.org All Rights Reserved 29
DevOps Values In Response To The Problem
DevOps Values
CULTURE
AUTOMATION
LEANMEASUREMENT
SHARING
© 1993 – 2017 Scrum.org All Rights Reserved 30
Where is Agile in this picture ?
© 1993 – 2017 Scrum.org All Rights Reserved 31
You Will Find Professional Scrum All Over This…
Team
© 1993 – 2017 Scrum.org All Rights Reserved 32
And What About The Scrum Team
• Self-organized• We do not tell them what to do, we tell
them what outcomes we seek.
• Has all the necessary skills to deliver the work
• Is small 7 +/- 2• Small enough that communication is not a
huge overhead
• Is safe• Feels empowered to make decisions
without fear
• Has a clear focus on outcomes• A clear vision for success with
measurements
• Can get stuff done• Supported by an organization that
removes impediments
© 1993 – 2017 Scrum.org All Rights Reserved
Easy to say, hard to do
33
Has All The Skills Necessary to Deliver the Work !
Front End, Back End
Mobile
Security, performance
Operations and Infrastructure
Release Management
UX / Design
Business / Customer knowledge
Testing
7 + / - 2
People Dependencies
© 1993 – 2017 Scrum.org All Rights Reserved 34
Self-Organize to Form Teams
What motivates people?
1. Autonomy
2. Mastery
3. Purpose
Source: Daniel H. Pink, Drive: The Surprising
Truth About What Motivates Us, Riverhead
Hardcover, 2009
Form teams naturally with:
• Team members who want change (Opt-in)
• Team members who want to work together (self-organization)
• Mutually-agreed commitments and decision processes (self-direction)
Guided by business goals
© 1993 – 2017 Scrum.org All Rights Reserved 35
The Need For Comb Shaped Team Members
http://www.irisclasson.com/wp-content/uploads/2013/07/skills.jpg
© 1993 – 2017 Scrum.org All Rights Reserved
• Infrastructure
• Supplier management
• Automation
• Architecture
• User Experience
36
Enabled by Ever Changing Shared Services
Agility is
undermined by
queues
© 1993 – 2017 Scrum.org All Rights Reserved 37
Supporting Teams - The Spotify Tribe Model
• Squad similar to a Scrum Team
• Tribe collection of Squads that work in a related area. Similar to a Nexus
• Chapter, small family of people inside a Tribe with similar skills
• Guild is a community of practice cross Tribe
© 1993 – 2017 Scrum.org All Rights Reserved
Communities Connect People Across Teams To Share And Improve
Team 1
Team 2
Team 1
Team 4
Team 3
Team 1
Team 2
Community
• Share experiences and grow skills through immersion & pairing
• Use peer coaching to share knowledge and increase professionalism, consistency
• Remove common impediments
© 1993 – 2017 Scrum.org All Rights Reserved
But What About Processes….
39
CustomerProduct
Owner
Idea
Product
Backlog
Developer
SCM
Dev
tools
Build
Automated
Tests
Test
Environments
Testers
Test Results
Release
Decision
Stakeholders
Business leaders,
Marketing, Security,
Ops, Legal, …
Production
Environments
Deploy
Automation supports competency
© 1993 – 2017 Scrum.org All Rights Reserved
Tool Providers Also Recognize the Need for Alignment
40
© 1993 – 2017 Scrum.org All Rights Reserved
Moving to a customer centric organization
41
• Agility is required to respond to the challenges of the modern world
• Scrum provides a way to build a process on top of a inspect and adapt loop
• DevOps was ALWAYS required to be effective
• But introducing frequently release and feedback loops is difficult
Some Ideas…
• Focus on Teams and Nexus
• DONE means DONE
• Look to DevOps for improving flow
• Skill up those teams with Security and operations
• Support with STRONG community
• Enable with SHARED services that will always be changing (agile too)
© 1993 – 2017 Scrum.org All Rights Reserved
Thank You!
42
© 1993 – 2017 Scrum.org All Rights Reserved 43
Working SlideFund
Frequently
Inspect
Frequently
Release
Frequently