kanban vs. scrum - agesis - it solutions vs. scrum.pdf · kanban and scrum, a comparison • kanban...
TRANSCRIPT
Kanban vs. Scrum
3 Copyright Agesis AB
www.agesis.se
Kanban • A change management method,
start from today and evolve stepwise
• Create flow and optimize lead-time
Scrum • A framework in which you should employ
and develop good practices
• Time-boxed: Plan and define scope –
Develop – and Deliver within the time-box
Kanban and Scrum, a comparison
4 Copyright Agesis AB
www.agesis.se
• Both embrace the Agile principles Kanban: also embrace Lean
• Both are empirical and adaptive processes ‒ Adapt by providing transparency and inspections
‒ Management and decisions are based on visualization and feedback
• Both are incremental development processes ‒ Build a “product” stepwise, by incremental development
Kanban: Main focus is to create flow, but cadences can be added if it serves the process
Scrum: Prescribes time-boxed iterations (Sprints)
Kanban and Scrum, a comparison
• Both are based on pull mechanisms Kanban: On demand when WIP limits and policies allow
Scrum: Per Sprint to create a Sprint Backlog
• Both balance workload and capacity Kanban: By pull (above) and by WIP limits on the number of work items in activities and buffers
Scrum: The amount of work is limited per Sprint by team capacity
• Both address process improvements Kanban: Reflect, gather data, analyze and improve the workflow, step by step
Scrum: Retrospectives where different aspects of the process
and/or team work can be addressed
5 Copyright Agesis AB
www.agesis.se
Kanban and Scrum, a comparison
• Kanban is more open Kanban: Does not prescribe any particular sessions or roles Start with today’s process, stimulate improvements and evolve (can be seen as a “change management” process)
Scrum: Pre-defines sessions, artifacts and roles
• Visualization, the board Kanban: A Kanban board can belong to a team or be shared between many teams and resources. The board lives and evolves as long there is work in the process.
Scrum: Each Development Team has their own Scrum Board.
The board is cleared and re-arranged every Sprint.
6 Copyright Agesis AB
www.agesis.se
Kanban and Scrum, a comparison
• The workflow
Kanban: Map out Activities and Buffers that reflect how your process work today, and evolve! Can make use of Swim-lanes, Shared Services, etc. Can state various types of process policies
Scrum: Typically, Planned – Ongoing – Done Backlog Items (Stories) are usually broken down into Tasks Definition of Done (DoD) and Definition of Ready (DoR)
7 Copyright Agesis AB
www.agesis.se
Kanban and Scrum, a comparison
• Preparing Work Items Kanban: Organize work items into stereotypes (Work Item Types), Classes of Services
May state policies for preparing Work Items
Scrum: Refine (groom) the Product Backlog: Set estimates on Backlog Items, and if needed break down bigger items to smaller, if needed re-arrange the Backlog Items, check that items are Ready to be pulled into a Sprint.
• Main metrics Kanban: WIP and lead-time/cycle-time
Scrum: Team estimates on Backlog Items and
Team Velocity/Capacity
8 Copyright Agesis AB
www.agesis.se
Time-boxing vs. WIP limits
9 Copyright Agesis AB
www.agesis.se
Amount of work
is fixed
shorten Lead-time (and improve Throughput)
(WIP Limits)
Pull Work Items
on demand when
WIP limits and
polices allow
Kanban
increase
Amount of work (improve Velocity)
Sprint length (fixed)
Pull a “batch” of
Work Items from
the Product Backlog Scrum
Sprint Backlog
pull
pull
Adopt Scrum roles into Kanban
• Development Team ‒ Cross-functional and self-organizing team
• Kanban coach/facilitator
• Product Owner ‒ Complement the board with a business view
‒ Upstream workflow for Backlog Management
‒ State business policies (e.g. how to prioritize and prepare work)
10 Copyright Agesis AB
www.agesis.se
Adopt Scrum events into Kanban
11 Copyright Agesis AB
www.agesis.se
• Refining (grooming) upcoming Work Items (next to pull) ‒ Upstream Business perspective
‒ Can be triggered by WIP Limits or by a Cadence
• Coordination meetings (Stand-ups) ‒ Manage flow, coordinate work and deal with impediments
‒ Triggered by a Cadence (each day, twice a week, …)
• Review/Demo ‒ Feedback, validation and acceptance from Customer/User
‒ Can be triggered by WIP Limits or by a Cadence
• “Retrospectives” to improve the workflow ‒ Triggered by a Cadence
Scaling Agile
• Can use Kanban to map out and visualize an enterprise workflow, end-to-end perspective ‒ Compare to a ”Agile Release Train” in SAFe
• A subset of the enterprise Kanban workflow can be mapped to, and managed by a Scrum Team
12 Copyright Agesis AB
www.agesis.se
Plannable vs. Unplannable work
Copyright Agesis AB
www.agesis.se 13
Next Ongoing Done
Task
Task
Task
Task
Task
Task
Defect
Defect Defect
Defects (high prio)
Other
stuff Task Task
Task Task
Task Task
Task Capacity for
Plannable work,
pulled from the
Product Backlog
(Sprints)
Capacity for
Unplannable work
(flow)
Feature
Feature
A Development Team in Scrum can add a Kanban workflow for unplanned work as a part of their capacity
Plannable vs. Unplannable work
Buffer for ”plannable” Items (from Product Backlog)
Buffer for ”unplannable” Items (bug-fixes, maintenance, support, etc.)
a
b
Burn-down
Burn-up
Copyright Agesis AB
www.agesis.se 14
?
X = % unplannable work (prediction)
Stagger planning over a Sprint to
create flow
Feature A [8 sp]
Feature B [13 sp]
Feature C [8 sp]
?
…?
Prio
Copyright Agesis AB
www.agesis.se 15
start
next, plan more soon
wait, plan later
Adopt WIP Limits into Scrum
16 Copyright Agesis AB
www.agesis.se
• “Proto Kanban” thinking ‒ Set WIP limit on how many Tasks a person can work on,
<n> Tasks per person
‒ Can make use tokens/avatars
• Kanban and WIP Limits within a Sprint ‒ Set WIP limits on the number of Sprint Items In Progress
‒ Only work with <n> Sprint Items/Stories at the time
Kanban within a Sprint, example
17 Copyright Agesis AB
www.agesis.se
Fill up at Sprint planning (cadence)
Planned Development
Sprint
Backlog
Released
(Done)
In Progress [2]
Task
Waiting for
UAT
Task Task
Task
Feature
Feature
Feature
Task
UAT
Task
Task
Development
policy
Released
policy
UAT policy
Task
Task Task
Feature
Up-stream Kanban for
Backlog Management
Copyright Agesis AB
www.agesis.se 18
New In Progress
(~ 2-4) Refine [~4]
Feature
Feature
Feature
Feature
Feature
Feature
Next to Refine
[~6]
Feature
Feature
Feature
Feature
Feature
Feature
Ready for
Development [~4]
Feature
Done
Feature
Feature
Feature
Feature
Feature
Feature
Ready for Dev.
policy
Prioritization
policy
Done (DoD)
policy