2013 11 05 getting the biggest bang for the buck out of...
TRANSCRIPT
1 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Getting the Biggest Bang for the Buck Out of Scrum
Agile Austin November 5, 2013
by Kenny Rubin
2
Author
Copyright © 2007 - 2013, Innolution, LLC. All Rights Reserved.
Background of Kenny Rubin
Trainer/Coach Trained more than 20,000 people in Agile/Scrum, SW dev and PM Provide Agile/Scrum coaching to developers and executives
Experience
My first Scrum project was in 2000 for bioinformatics
Former Managing Director
Executive
3
If you here something interesting…
Copyright © 2007-2013, Innolution, LLC. All Rights Reserved.
Please Tweet About It!
Include @krubinagile and #agileaustin in each tweet
4 Copyright © 2013, Innolution, LLC. All Rights Reserved.
5
Scrum Framework
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Art available at: http://www.innolution.com/resources
6 Copyright © 2013, Innolution, LLC. All Rights Reserved.
7
Approaches
Copyright © 2013, Innolution, LLC. All Rights Reserved.
8
ScrumBut(t) – Violations of the Scrum Framework
Copyright © 2013, Innolution, LLC. All Rights Reserved.
We do Scrum, but…
Sprints are 8 weeks
No product owner
Daily scrums on M-W-F
Sprint planning is 2 days
Etc…
9
What If We Had No Scrum “Violations?”
Copyright © 2013, Innolution, LLC. All Rights Reserved.
VIOLATION YOUR USE OF SCRUM VIOLATES A CORE PRACTICE AND IS HEREBY
DEEMED TO BE A SCRUMBUT
YOUR TEAM PHOTO HAS BEEN RECORDED
Do no violations = success with Scrum?
10
Current Industry Results – From Comparative Agility®
Copyright © 2013, Innolution, LLC. All Rights Reserved.
8,558 Surveys at www.comparativeagility.com
11
VersionOne 7th Annual Survey
Copyright © 2013, Innolution, LLC. All Rights Reserved.
0%
20%
40%
60%
1% 1% 1% 2% 2% 2% 2% 4% 4% 7% 9% 11%
54%
Of 4,048 respondents, most are using Scrum or Scrum variants (72%)
12
Inhibitors to Success Using Scrum
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Ignorance or misapplication of core agile principles during development
Failure to apply agile principles throughout the value chain
Failure to structure teams in an economically sensible way
Overall, they don’t apply core agile principles in an economically sensible way
13
Principles
Copyright © 2013, Innolution, LLC. All Rights Reserved.
14
So What is Economically Sensible Scrum?
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Economic Framework Variability
& uncertainty
Prediction &
adaptation
Validated learning
Work in process (WIP)
Progress Performance
15
Economics – The Universal Language of Product Development
Copyright © 2013, Innolution, LLC. All Rights Reserved.
16
We Need a Economic Framework
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Waste
Lead time
Variability
Batch size
Customer sat
…
Lifecycle profits
Based on Reinertsen “The Principles of Product Development Flow: Second Generation Lean Product Development”
Compare effects of different product / process /organizational attributes by converting them all into the same unit of measure
17
Example: Waste
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Waste 1 Waste 2 Waste 3 Waste 4 Multiple forms
of waste
Waste 1 Waste 2 Waste 3 Waste 4 Can’t eliminate
them all
Waste 1 Waste 2 Waste 3 Waste 4
$ $$$$ $$ $$$
Determine which cause most
economic damage
18
Example: Cost of Delay
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Lead time Variability
Money Lead time
If you have to wait 3 weeks for the UX team to design your UIs, and that delay could be eliminated by having a UX designer on your team, what would be the cost of the UX-team delay (in lifecycle profits)?
19 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Ignorance or Misapplication of
Core Agile Principles During
Development
20
Misunderstanding of When Change Occurs
Copyright © 2013, Innolution, LLC. All Rights Reserved.
We like Scrum, because we can make changes anytime we want!
Holly *?&! they can’t just change things whenever they want!
21
Economically Sensible Change
Copyright © 2013, Innolution, LLC. All Rights Reserved.
22
Misunderstanding of Just-in-Time
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Holly *?&! This sounds like total chaos!!!
With Scrum we do everything just-in-time!
23
Balance Up Front Predictive with Adaptive Just in Time
Copyright © 2013, Innolution, LLC. All Rights Reserved.
24
Recognize Inventory (WIP) Waste
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Manufacturing inventory is both physically and
financially visible
Product-development inventory are knowledge assets that
aren’t visible in the same way as physical parts
25
Focus on Idle Work Not Idle Workers
Watch the Baton Not the Runners
Copyright © 2013, Innolution, LLC. All Rights Reserved.
26
Economically Sensible Planning
Copyright © 2013, Innolution, LLC. All Rights Reserved.
27 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Failure to Apply Scrum Principles Throughout the
Value Chain
28
Example Value Chain
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Management
Finance HR Legal
Sales
Marketing
Develop Ops
Cust
Dev Partners Dev
Partners Dev
Partners
Cust
29
Do Agile Here
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Internal Management Misaligned
Develop in an Agile way, but still provide all of the same plan-driven artifacts (e.g., extensive up-front requirements, full budget, and precise schedule) like before to get the project approved
30
Sales Misaligned
Copyright © 2013, Innolution, LLC. All Rights Reserved.
31
Portfolio Planning Misaligned
Copyright © 2013, Innolution, LLC. All Rights Reserved.
32
Downstream Misaligned
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Develop Ops Backlog of potentially
shippable product increments
Cust
Ops
33
Partners Misaligned
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Fixed
Fixed Fixed
Contract
34
Protection of the Fiefdoms
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Sure, we can do Scrum, as long as I don’t have to change anything in my group!
George’s Group
Me too! Me too! Me too! Me too!
35
Failure to See the Whole
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Optimizing locally frequently sub-optimizes the system
36 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Failure to Structure Teams
in an Economically Sensible Way
37
Economically Sensible Teaming
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Reduce multitasking
Scaling teams based on economics, not dogma
Embrace T-shaped Skills
Create and maintain long-lived teams
38
Reduce the Amount of Multi-tasking
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Not about keeping people busy
39 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Multitasking
Clark and Wheelwright (1992) studied multi-tasking and determined that when working on more than two projects, a person’s time spent on value-adding work drops rapidly
40
Teams with T-Shaped Skills
Copyright © 2013, Innolution, LLC. All Rights Reserved.
41
Team Longevity
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Product 1 PB 1 Feature Team A
Product 2 PB 2 Feature Team A
?
42
Economics Favor Long-lived Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
More productive than newly formed groups
Team familiarity can positively impact efficiency and quality of team output
Has a shared velocity and estimating history that can be used during planning
Have established trust and team identity and integrity
43 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Projects with at least 100 people (320 surveys)
44
Scaling With Multiple Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
As the scope of work gets larger and one team is no longer sufficient, what is your scaling strategy?
45
Discipline Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
46
Location Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Sydney New York
Sydney New York Deliberately Distributed
Teams Team 2
Team 1
Team 1 Team 2 Coordinating Collocated
Teams
47
Architectural Layer Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
DB
Middle Tier
GUI
48
Component Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
49
Feature Teams
Copyright © 2013, Innolution, LLC. All Rights Reserved.
50
Don’t Scale Based on Dogma!
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Do you honestly think there is a single answer to scaling that universally applies to all situations (sizes and types of organizations)?
Everyone knows feature teams are better!
Nuts! Component teams promote
conceptual integrity & reuse!
51 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Component Teams (Single Source)
52 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Component Teams (Multiple Sources)
53 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Combined Feature & Component Teams
54
Summary
Copyright © 2013, Innolution, LLC. All Rights Reserved.
Performing all Scrum practices and using generally accepted Scrum approaches is necessary, but not sufficient
If you want to see the real benefits of applying Scrum you need to apply Scrum within an economic framework that allows you to make sensible tradeoffs
55 Copyright © 2013, Innolution, LLC. All Rights Reserved.
Contact Info for Kenny Rubin
Email: [email protected] Website: www.innolution.com Phone: (303) 827-3333 LinkedIn: www.linkedin.com/in/kennethrubin Twitter: www.twitter.com/krubinagile Facebook: www.facebook.com/InnolutionLLC Essential Scrum: A Practical Guide to the Most Popular Agile Process
www.essentialscrum.com
Comparative Agility Website www.comparativeagility.com