Integrate Scrum and Kanban to maximize business value as early as possible by analyzing, developing, delivering, and maintaining complex products and IT services. Open ScrumBan Manifesto Delivering the finished product Over reviewing the artifacts On-demand release Over scheduled release Value flow Over following dogmas Progressive improvement Over mutation driven by Model Open ScrumBan Principles Lean Agile Implement lean thinking into agile practice, pursue value-added and eliminate waste, such as workflow, stable system, etc. Pursue system thinking, identify various systems and systems of systems, and make decisions based on context Iteration Rhythm Pursue single-piece flow, single-piece can be entered into the plan, but single-piece release is not mandatory, and batch delivery is performed at fixed intervals by default Focus on value delivery, each iteration must have an actual release increment, no longer requiring only potential release increments like Scrum Respect present Use Kanban to show the delivery value stream, and analyze improvement opportunities from the perspective of the value stream, such as lead time When starting, it is not required to immediately change the team according to any team model, and choose the roles and practice according to the situation of the team Evolutionary optimization Use evolution instead of revolution to optimize and help teams develop various practices that are suitable for them Not to tolerate the deficiencies and dysfunctions exposed by Scrum, but to combine the specific environment of different teams to find effective ways to solve them

1. V2020/12
December 2020 Update Note: The Scrum Guide was updated in November 2020, and this guide references
the Scrum Guide, so it's a companion update, with another significant change being the change in the name
of the guide from ScrumBan SimpleOpen Edition Guide to Open ScrumBan Guideline, with a shorter new
name, highlighting Open, and another release date.
The December 2019 edition is written earlier:
Having chatted about ScrumBan many times in the WeChat group, there are always groups of friends who
say they don't know ScrumBan, and given that there really is really no clear and concise ScrumBan
description, draft this document and welcome feedback.
Considering that ScrumBan has been elaborated by many parties and does not have absolute authority, this
edition has been added to the SimpleOpen edition, which means simple and open. To highlight Kanban,
change the common Scrumban to ScrumBan, which refers to ScrumBan SimpleOpen.
Producer：Zhang Mike， Chen Yong， Xu Wilson， Xiong Dragan
Wechat
us
Open ScrumBan Guideline

2. Table of Contents
Preface
Open ScrumBan Manifesto
Open ScrumBan Overview
Open ScrumBan 1234
Open ScrumBan Principles
End

3. Preface
History：
• Book-Scrumban，Author: Corey Ladas， 2009
• Book-The Scrumban [R]Evolution，Author: Ajay Reddy，2015
• eBook-IBQMI Certified Scrumban Practitioner®: The official training material，2019/2
• In 2019 14th Annual State of Agile Report，Scrumban 8%，Scrum 54%，Kanban 5%
• In 2020 15th Annual State of Agile Report，Scrumban 10%，Scrum 58%，Kanban 7%
Purpose：
• Integrate Scrum and Kanban to maximize business value as early as possible by analyzing,
developing, delivering, and maintaining complex products and IT services.
Question：
• Is ScrumBan a Scrum？ Or a Kanban？
• What’s relationship between Open ScrumBan and other Scrumban？

4. Open ScrumBan Manifesto
Delivering the finished product
Over reviewing the artifacts
On-demand release
Over scheduled release
Value flow
Over following dogmas
Progressive improvement
Over mutation driven by Model

5. Abbreviations
• PB – Product Backlog
• DoS – Definition of Start
• DoR – Definition of Ready
• DoD – Definition of Done
• WIP – Work In Progress
• PM – Product Manager
• SL - ScrumBan Leader

6. Open ScrumBan Overview
Explore Analyze [5] Queue
[1-5]
Implement[5] Test[5] Release
Intent Selected Doing Done Doing Done Doing Done Doing Done
accelerating
DoR DoD DoD
release
DoD
normal
Other swimlane
Epic
Story
Epic
Story
Story
Story
Story
Story
Story Epic
Epic
Story
Epic
Epic
Explore
PB
Epic
Batch
Delivery by
cadence
Show
by Card
propert
ies
Different
swimlane
different
priorities
Limit WIP to promote
collaboration and
acceleration
Queue WIP sets a low
limit, so that implement
does not wait
Meet DoR
to queue
Transition
need DoD
Assignee
WIP
restrictions
bring Focus
Epic
Visualize all
steps
Limit
current
cards of
one person
ScrumBan
Leader，
Lead team
by
ScrumBan
Retrospective
and
adjustment
On demand
Planning
meetings
Story
The review takes place
as early as possible
Scheduled
Meeting before
Kanban
V2020/12
出品人：张克强，陈勇，徐陈飞，熊小龙
Product
Manager，
Host
exploration
and story
analysis
DoS

7. Open ScrumBan 1234
Story Kanban
• Show all steps of stories (including epics). The stories are used by customers. the batch of stories
is selected at the beginning of the iteration, and then added according to the progress
Roles
• Product Manager, Equivalent to Product Owner in Scrum
• ScrumBan Leader，Equivalent to Scrum Master, Team Leader
Recommended Activities
• Clarification，PM clarify story with the dev/test and confirm DoR
• Retrospective，reflect on and look forward to better practices, lead by SL
• Release Planning， plan the coming release with story kanban
• Standup Meeting，update progress, monitor risk before story kanban
Artifacts
• Product Backlog，PB, Collect ideas or requests from all parties
• Story ToDo List，Stories which meet the development DoR after exploring
• Release Batch，meet release DoD to go live

8. • Promote the story to meet the DoR, give
the story priority, explain and verify the
story during the implementation
• The reason for not using Owner is that in
complex products, most of the front-line
requirements leaders do not have the
final decision-making power. It is more
appropriate to use the common product
manager term, which can be either a
decision maker or decision implementer.
It is not mandatory to be responsible for
the ROI of the requirements
2 Key Roles
Product Manager
• Lead the team to carry out on-demand
ScrumBan activities and build a story board.
Can dock with the original Scrum Master, or
with the original project manager and the
original team leader
• ScrumBan Leader leads the team to tailor and
supplement ScrumBan, establish and maintain
a team charter
• SL is the servant style leader, empowers the
team, transparent team work, and shows all
aspects of the team.
ScrumBan Leader
• ScrumBan does not exclude other roles, and even encourages the establishment of different roles based
on process characteristics
• Respect the existing roles of the team and use storyboards to reflect the work of all roles
• Look for role adjustment opportunities based on performance
Other Roles

9. 3 Key Artifacts
Product Backlog
• Collect voices
from users,
collect ideas from
all parties, and
even complain
• PM filter PB and
select to start
analysis
according to DoS
Story ToDo List
• After analysis, the epic
or story that satisfies
the DoR enters the
story to-do list
• It is recommended to
use the egg estimation
method(Same as
NoEstimates), the story
is sorted, and identified
at the same magnitude
level of size
Release Batch
• A group of stories
which are delivered
together,
• Meet Release DoD
• Determine the story
that satisfies the DoD
at the latest before
iteration delivery

10. 4 Recommended Activities
Clarification
• Sort out and
clarify epics
and stories,
and confirm
these meet
DoR
• Ensure to meet
the WIP in the
queue column
• PM Drive this
Retrospective
• Review methods
and tools, etc.,
• Also Review the
product itself
• Revise the team
charter
• PM and SL
Facilitate this
together
Release Planning
• According to the
situation of the
storyboard,
supplement the
story and enter
the development
• Rolling plan
• SL Drive this
Standup
Meeting
• Communicate
progress with the
whole team in
front of the
storyboard
• Identify
collaboration,
obstacles and
risks
• PM and SL
Facilitate this
together

11. Recognition and conversion of epics and stories
• External requirements are often considered for business purposes, so
their granularity is not necessarily consistent with the ability of a
single iteration to complete, so Epic is used to take all kinds of
external requirements, then Epic’s story is identified to each iteration.
• From the point of view of maintaining the consistency of external
communication, it is recommended to try to keep epic, that is, even if
the epic grain is small, do not convert to the story, to avoid external
misunderstandings.

12. Granularity and sorting
• For stories that are estimated to be completed by a single person in the
iteration, the stories are processed in order on the Kanban board instead of
the specific story points, and more attention is paid to whether they can be
delivered quickly for external needs.
• ScrumBan is divided into accelerated swim lane and normal swim lane. In
real work, new and urgent needs are constantly emerging and need to be
cut into the line. Various factors are used to determine how to accelerate.
The identified urgent needs can be cut in the queue and arranged to be
processed on the accelerated lane with high priority. , May therefore
squeeze out other requirements of the current release batch or postpone
the release.
• Compared with Scrum, there is no such thing as “acceleration” in Scrum.
All sprint requirements are often delivered together based on the
commitment value (one of the five Scrum values). The team needs to
commit to complete the planned requirements scope. The response to the
sudden emergence of high-priority needs is slightly slower.

13. Open ScrumBan Iteration and delivery
Iteration
Delivery
Routine iterative delivery is arranged at the end of each iteration, and
on-demand delivery during iterations is also supported.
Determine the delivery batch at the latest before delivery.
Continuous Exploring Continuous Clarify
Iteration
rhythm
Before the iteration, the requirements clarified in advance are sufficient to support
the iteration.
At the end of the iteration, deliver and review according to the iteration rhythm.
Continuous Development Batch Release
Enough
Stories meet
DoR, to Start
Iteration
Supplement
stories based
on progress
during
iteration
At the latest, stories
can be added to catch
up with the delivery
of this iteration
分析轨
实现轨
Check with
Release DoD
Iteration
Release
Iteration
Release
Release on
Demand
Freeze Freeze
Check with
Release DoD
Retros
pective

14. Open ScrumBan Scaling
Unified scheduling, improve
scheduling efficiency, reduce
demand scheduling friction
Unified
Scheduling
Cross-
departmental/upstream and
downstream dependencies,
through unified iteration to
maintain a consistent rhythm
of R&D work
Synchronize
Iteration
Through the version window,
phase goals are kept
consistent, while reducing
R&D complexity and
simplifying communication
Unified Version
The core elements of
scaling

15. ScrumBan Team of Teams-ScrumBan Tribe
Scrum
Ban
Squad
1
D
e
v
Scrum
Ban
Squad
2
Scrum
Ban
Squad
3
Scrum
Ban
Squad
n
Develop
ment
Head
Archit
ect
Test
Head
Test Chapter
Business
Stakeholder
Coach
Cha
pter
2
Cha
pter
1
• Each role in the
picture can be
adjusted, but the
coordination of
product, development,
testing, and
architecture must be
coordinated at the
tribal level.
• Encourage tribal
chiefs to concurrently
serve as tribal coaches
and exert coaching
leadership
• Encourage the
establishment of role
Chapters
Project
Manager
Lead
D
e
v
D
e
v
D
e
v

16. Open ScrumBan Principles
Lean Agile Implement lean thinking into agile practice, pursue value-added and eliminate waste, such as
workflow, stable system, etc.
Pursue system thinking, identify various systems and systems of systems, and make decisions
based on context
Iteration Rhythm Pursue single-piece flow, single-piece can be entered into the plan, but single-piece release is
not mandatory, and batch delivery is performed at fixed intervals by default
Focus on value delivery, each iteration must have an actual release increment, no longer
requiring only potential release increments like Scrum
Respect present Use Kanban to show the delivery value stream, and analyze improvement opportunities from
the perspective of the value stream, such as lead time
When starting, it is not required to immediately change the team according to any team model,
and choose the roles and practice according to the situation of the team
Evolutionary
optimization
Use evolution instead of revolution to optimize and help teams develop various practices that
are suitable for them
Not to tolerate the deficiencies and dysfunctions exposed by Scrum, but to combine the
specific environment of different teams to find effective ways to solve them

17. End
• Scrumban vs Scrum vs Kanban in dispute
• https://www.scrum.org/index.php/forum/scrum-forum/33122/scrumban-same-
scrum-kanban
• Scrumban at Wiki
• https://en.wikipedia.org/wiki/Scrumban
• Scrumban history and purpose
• https://news.ibqmi.org/history-and-purpose-of-the-scrumban-framework