Scrumban - What it is and when to use it.

Scrumban
What it is and when to use it.

2
The Scrumban [R]Evolution
Pearson Education (2015)
65,000+ users and counting
Your friendly neighborhood Scrum
and Scrumban tool
The game trusted by trainers and coaches
A quick peak at our products, services & affiliations
Boutique IT Solutions & Services firm that
builds high-performing teams & organizations.
Who We Are
Official Licensed Material © CodeGenesys, LLC@ajrdy ajay.reddy@codegenesys.com

3
A snapshot of organizations we’ve helped
Who We Help

Vague and False Impressions
4

VersionOne’s State of Agile across the industry
6

-Ken Schwaber
7
“ 75% of organizations using Scrum will not succeed in
getting the benefits they hope for from it. ”

Consistent Problem Areas
8
Productivity or Perceived Productivity
Predictability
TRUST
Disconnection with economics
Cargo Cult implementations
Organizational Apathy
Worker or Work focus not value focused
Cargo Cult implementations

Starting With The End In Mind
How can you tell if you’re on the right path if you don’t know where you’re going?
9
Would you tell me, please, which way I ought to go from here?” asked Alice.
"That depends a good deal on where you want to get to," said the Cat.
"I don't much care where –" said Alice.
"Then it doesn't matter which way you go," said the Cat.
"– so long as I get somewhere," Alice added as an explanation.
"Oh, you're sure to do that," said the Cat, "if you only walk long enough."

Scrumban
A misunderstood concept
What’s Your Perspective?
Which of these descriptive labels would
you apply to “scrumban”?
10
Agile without Sprints / Time-boxes
No estimation
kanban inside Scrum
Scrum inside Kanban
No project burn downs
No Scrum Master or equivalent role

Scrumban : Original manifestation
2008
11
Backlog Defined In Progress Done Accepted
Blocked
Limit = 4 Limit = 3 Limit = ∞ Limit = ∞
Blocked
Pull System
Single piece flow

Framework Values
Supporting successful outcomes
Focus
Courage
Scrum
Team-centric & focused on promoting agility.
Kanban
Service delivery & evolutionary change
12
Openness
Commitment
Respect
Understanding
Agreement
Respect
Leadership
Flow
Transparency
Balance
Customer Focus
Collaboration
TRUST

Framework Values
Supporting successful outcomes
Empiricism
Empirical approaches are always favored over
theories, and verifiable results over dogma.
Scrumban
Grow sustainably
13
Humility
Systems are complex and constantly changing,
and we are constantly learning. We must always
be ready to challenge our beliefs. Improved
understandings and approaches can come from
any source.
Constructive Interaction
There will always be competing management
frameworks and methods. Scrumban
emphasizes constructive debate that improves
understanding of the strengths and limitations of
each over blind acceptance that any one
framework represents the “only” or “best” way of
achieving a particular outcome.
TRUST

What is Scrumban?
Three Essential Flavors
14
1
A framework for introducing and
adopting Scrum as a software
development methodology.
2
A framework for evolving from Scrum to
a unique set of processes and practices.
3
Recognized Manifestations
Using Kanban as a lens through which we can view
and manage a Scrum work process.
A framework for overcoming common
challenges with scaling Scrum across
an Enterprise.

The Kanban Method
Agendas, values & practices
Serviceability1
Survivability2
Sustainability3
3 Main Agendas
Transparency1
Balance2
Understanding3
Flow4
9 Primary Values
Visualize1
Manage Flow2
Make Process Policies Explicit3
Develop Feedback Loops4
6 Core Practices
15
Customer Focus5
Agreement6
Respect7
Leadership8
Collaboration9
Limit Work in Progress5
Improve Collaboratively &
Evolve Experimentally
6

Applying the Kanban Lens to Scrum
Different lenses for different perspectives
16
Using Kanban as a lens
into existing systems
enables us to focus on the
“right” things – even
when they’re outside of
our defined processes.

Lead Time
A productivity measure
17

Lead Time Histogram
A forecasting measure
18

What is Scrumban?
19
1
2
3
an Enterprise.

Amplify ScrumUnderstand, Identify and Improve

Scrum commonly does well around
These bring additional perspectives and capabilities to the Scrum context
21
Team focus aiding vision alignment
Importance of cadence, rhythm
Focus on shorter term planning compared to traditional methods
Call for customer participation; Value from customer’s stand point
Focus on smaller batches.
Collaboration enabler
Shared ownership, Cross functional work
Key Enabler: High trust
environment

Scrum commonly does not do well around
These bring additional perspectives and capabilities to the Scrum context
22
Nature of work- specifically - It’s arrival, it’s unpredictability
Longer term considerations such as architecture
Addressing psychological barriers in implementation
Product owner role effectiveness and scale
Scaling constructs unreliable beyond the team
Sprint ‘Commitments’ relationship to Market Risks
Longer term quality considerations
Deterministic planning
Share ownership emergence
Reliance on top down/vertical buy-in with affirmations of servant
leadership

A Scrumban Case Study- Mammoth
Success in different contexts

24
Case Study – Mammoth Bank
Overcoming Common Challenges
The State of Scrum at Mammoth
• In third phase of an “Agile Transformation” that began 8 years
earlier.
• Scrum had not been adopted throughout the organization, and the
objective was to now have all development teams practicing Scrum
at the conclusion of this latest initiative.
• Major source of dissatisfaction for business lay with a perceived
slow and unreliable delivery from a variety of teams within the IT
organization.
• Major source of dissatisfaction for the IT teams lay with constantly
shifting priorities from the business unit, forcing frequent context
shifts of work in progress.
• Teams were also suffering from “improvement fatigue.”

Scrumban: Amplify Scrum
A framework for evolutionary change and continuous improvement
Four familiar principles
25
Start with SCRUM you already
do
Agree as a Scrum team to pursue
incremental changes to improve the
way you work
Respect the Scrum Master,
Product Owner and other current
roles
Encourage acts of leadership at all
levels

A Financial Services Institution
Digital Data Team
Served a large number of different
business owners.
Majority of incoming work related to
enhancing existing high-profile
applications and services.
Constantly shifting priorities across
business owners resulted in frequent
“project” interruptions.
Quality of delivered work was high,
but lead times were very slow.
26
Reported Project Size
Time Waiting
in Project Queue
Actual
Development Time
Total Customer
Lead Time
Small 14 16 30
Small 24 9 33
Medium 16 14 30
Medium 15 27 42
Medium 23 17 40
Medium 24 36 60
Large 20 30 50
Large 25 42 67
Average 20 24 44
Median 22 22 41

Started with Improved Visualization
Understanding the current context
27

New Metrics Exposed New Understandings
Understanding the current context
28

Evolved Existing Visualizations
Responding to improved understandings
29

More Metrics, Deeper Understandings
Using Kanban as a lens, the team better understood what to focus upon in terms of addressing challenges.
30
Sprint Flow Efficiency
Working Time
___________________________________________
Working Time + Waiting Time
63%

Initial Improvements
Effects from using Kanban as a lens after just 10 weeks
31
Key Enablers
Trust in the workers and the system
Mapped the Value Stream
Analyzed Flow, Visualized External
Dependencies
Captured Objective Data and
Negotiated SLEs

Visualizing Improvement
Adding discipline & visualization to continuous improvement
32
1. Challenges and
opportunities are
identified and added
to a “backlog” of
potential efforts.
2. Potential efforts are
contextualized as to whether
they are reactive or pro-active
(top vs. bottom quadrants)
and paradigm-changing or
paradigm-consistent (left vs.
right quadrants)
3. Team prioritizes
change efforts and
undertakes a
disciplined, iterative
approach toward
target conditions.

33
Common Scrum functions /
practices can be “visualized” to
reflect core mechanisms to try
using as “countermeasures” for
moving from current condition to
target condition.

34
Harmonizing with other methods and frameworks
This Mammoth Bank Team
incorporated A3 Problem Solving
and the Cynefin Complexity
Management framework as part
of their continuous improvement
discipline.
This worksheet was developed
through the point of
implementing and measuring the
impact of their countermeasures.
Note the visualization of current
conditions.

35
Harmonizing with other methods and frameworks
Note the continued emphasis on
visualizing of results and
identification of next steps in this
iterative process.

36

37
@ajrdy ajay.reddy@codegenesys.com Official Licensed Material © CodeGenesys, LLC
Common
Challenges
Amplifying Scrum
Cargo Cult
Implementations
Scrumban
 Emphasis on systems
thinking and understanding
of current context helps
assure teams and
organizations don’t just
blindly apply prescribed
roles and ceremonies.
Broken
Commitments
Scrumban
 Active risk recognition and
management improves
ability to attack highly
variable work items early.
 Expanded opportunities to
build trust through
probabilisticly determined
SLEs vs. just a Sprint
commitment.
Disruptive
Implementations
Scrumban
 Core principles of “start
with what you do now” and
“respect current roles and
responsibilities” minimizes
psychological barriers.
 Preference for evolutionary
vs. revolutionary change
minimizes disruption.
Inexperienced
Product Owner
Scrumban
 No longer reliant on
individual capabilities of
Product Owner. Risk and
economic prioritization is
visualized and can be
actively managed at every
phase of the value stream.
Arbitrary
Team Size
Scrumban
 Not all systems are created
equal, and sometimes the
right size falls outside of -
Scrum’s recommended 7-12
person limit.
Long
Standups
Scrumban
 Visual board radiates
status.
 Emphasis on the flow of
work over the activities of
individual workers mitigates
risk of meaningless
conversations on status. Forced
Co-location
Scrumban
 Additional practices and
mechanics allow teams to
effectively collaborate from
diverse geographic
locations.
 Scrumban aids in building
trust.

Adopt ScrumUnderstand, Identify and Improve

A Scrumban Case Study-
Simpli-safe, Capital One, State Street
Success in different contexts

-Tobias Mayer
40
“ Scrum is a good example of an organizational framework. It has
well-defined components, namely roles, meetings, artifacts, and
values. These are fixed, and failure to embrace the whole usually
results in a collapse of the framework. ”

41
1. Challenges and
opportunities are
identified and added
to a “backlog” of
potential efforts.
2. Potential efforts are
contextualized as to whether
they are reactive or pro-active
(top vs. bottom quadrants)
and paradigm-changing or
paradigm-consistent (left vs.
right quadrants)
3. Team prioritizes
change efforts and
undertakes a
disciplined, iterative
approach toward
target conditions.

42
Common Scrum functions /
practices can be “visualized” to
reflect core mechanisms to try
using as “countermeasures” for
moving from current condition to
target condition.

46
What iteration size makes the most sense for a given team / type of work ?
How many stories to plan for a given Sprint?
How many iterations are going to be needed to deliver a full release?
How many resources will be needed to complete this project within a given
time frame?

What is Scrumban?
47
1
2
3
an Enterprise.

Scale ScrumUnderstand, Identify and Improve

50
Starting
conditions:
Scrum and ‘kanban’
teams interoperability
Scaling with
Scrumban

52
Present
conditions:
Scrum
Implementation
route: Scrumban
Dependencies
visualized
Value chain
Smaller batches Systems Visualized Cost of delay
prioritization

What is Scrumban?
53
A framework for introducing and adopting
Scrum as a software development
methodology.
1
challenges with scaling Scrum across an
Enterprise.
2
A framework for evolving from Scrum to a
unique set of processes and practices.
3

Why Do you care
The market
54
Interest from the market1
Mike Cohn recommended2
Kanban classes vs Scrumban book3
Here are some indicators
Scrumban is growing

Enhanced Perspectives &
Capabilities
Frameworks, methods & disciplines we can “plug-in” to Kanban

The GetScrumban Game
Experience Scrumban evolutions
97
10 Minutes
Now let’s experience some common
evolutions in action by walking through a small
portion of the GetScrumban Game…
Introduction
Brief overview on what we’ll see.
Game Play
Experience a typical evolution.
Retrospective
Observations and learnings from the experience.

57

Scrumban - What it is and when to use it.

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Scrumban - What it is and when to use it.

Semelhante a Scrumban - What it is and when to use it. (20)

Último

Último (14)

Scrumban - What it is and when to use it.

Notas do Editor