Scrum-ban

mixing agile and lean

By Vidas Vasiliauskas
About me
• Product manager at Eylean board
• Started career as a developer
• 8 years in software industry
• Doing “lean startup”
Why you should hear this?
Why you should hear this?

• You are doing product development

Why you should hear this?

• You are doing product development

• You are in a startup

Why you should hear this?

• You are doing product development

• You are in a startup

• Your team is less or equal to 8 people

Why you should hear this?

• You are doing product development

• You are in a startup

• Your team is less or equal to 8 people

• Uncertainty is a daily thing for you

Why you should hear this?

• You are doing product development

• You are in a startup

• Your team is less or equal to 8 people

• Uncertainty is a daily thing for you

• You have heard or practiced agile and lean

Scrum vs Scrum-ban
Scrumban 101

Goals: Features:
• Minimum delivery time • Event/demand driven
• Fully loaded team • Empowers team roles
• Lean like hell
 YES
Backlog
-------- 5-15% of
-------- Task board overall time Triage
-------- left until
release No
--------
date? Feature
freeze

Daily
Planning Task board Production
meeting
Stabilization

Kaizen No No Planning
trigger?
Release
YES Kaizen?
YES
Task board
To do Doing Done
Analyze Initiate
requirements agreement

Develop project
plan

Develop project
plan
Planning on demand

GOLDEN RULE:
Demand goes first before supply
 To do Doing Done
Create design Analyze Initiate
guidelines requirements agreement

Create design Define

docs specifications
 To do Doing 2 Done
Create design Analyze Initiate
guidelines requirements agreement

Create design Define

docs specifications
 To do
Buffer Doing 2 Done
Create design
Develop project Analyze Initiate
guidelines plan requirements agreement

Transfer Define
Create design
documents specifications
docs
To do Buffer 2 Doing 2 Done
Create design Develop project Analyze Initiate
guidelines plan requirements agreement

Transfer Define
Create design documents
docs specifications
 To do Buffer 2 Doing 2 Done
Create design Develop project Analyze Initiate
guidelines plan requirements agreement

TRIGGER!!!
Transfer Define
Create design
documents specifications
docs
Less planning and concentrated release
Points

Points done

Time
Tasks

Items
Tasksdone
done

Time
 Feature
freeze
Triage
Stabilization

Tasks

Tasks done

Time
Estimating is easy…
 Product, project or
support?

Product Project Support

Assembly Single Do you

know the Yes
line product
deadline? Do you
prioritize by
No estimate?
Features or No
Do you
knowledge
need to
?
know it? No
Knowledge Features
Yes Yes

Average No estimate,
Estimate focus on goals
estimate
 Lead time

Planning on
demand

Cycle time

Task Task Task

created started delivered
4 guidelines to control cycle time
1. Prefer completed task to
starting new
4 guidelines to control cycle time
2. Grab second task only if the
first one is blocked
*can overcome rule 1.
4 guidelines to control cycle time
3. Late resource binding
4 guidelines to control cycle time
4. Avoid critical path
 NO! To early binding
+STRESS

-ENERGY
-TIME
* Mind the impact
Push system Pull system
3 kings to rule them all
Daily meeting

Planning meeting
(on demand)

Kaizen
Aligned vision
Scrum Kanban Scrumban

Iterations 1-4 week sprints Continuous work Continuous work with with decoupled
planning and release

Work routines Pull principle Pull principle or late binding to resources Pull principle or late binding to resources

Scope limits Sprint limits total work amount Work in progress limits current work amount Work in progress limits current work
amount,
Buffer defines triggers for planning
Planning routines Sprint planning Release/iteration planning, demand Planning on demand for new tasks
planning
Estimation Backlog and sprint planning Optional Average or no-estimation
Performance metrics Burndown, Velocity Cumulative flow diagram, lead time cycle Average cycle time
time
Continuous improvement Retrospective Optional Kaizen
Meetings Sprint planning, daily scrum, sprint review, Kaizen Daily, on demand planning, kaizen
retrospective
Roles Product owner, Scrum master, team Team leader, team Team leader, team
Team members Cross-functional team members Specialized team members Specialization or preference to tasks

Task size Should be less than 8 hours to see progress Any size Any size
New items during iteration Forbidden in most cases Allowed whenever queue allows it Allowed through buffer swap
Ownership Owned by a team Supports multiple teams ownership Supports multiple teams ownership
Board Defined/reset each sprint Persistent Persistent
Prioritization During backlog and sprint planning Optional Always open
Roles Scrum master, product owner, team Not defined, may vary Not defined, may vary
Rules Constrained process Only a few constraints, flexible process Slightly constrained process

Fit for Enterprise maturity for teams working on Support and maintenance teams, Startups, fast-pace projects, continuous
product or especially project which is longer continuous product manufacturing product manufacturing
than a year
THANK YOU

www.aboutscrumban.com

@Vasiliauskas
vidas@eylean.com

+370 600 37066