scrumban - taking scrum outside of its comfort zone

35
Scrumban Taking Scrum outside it’s comfort zone

description

Intro to Kanban, Scrumban and why/how to use them in practice to improve agility whre plain scrum doesn't work

Transcript of scrumban - taking scrum outside of its comfort zone

Page 1: scrumban - taking scrum outside of its comfort zone

Scrumban

Taking Scrum outside it’s comfort zone

Page 2: scrumban - taking scrum outside of its comfort zone

About Me• Agile Coach, Certified Scrum Practitioner, Certified Scrum Product Owner• 13 years experience leading R&D organizations (including VP R&D) focusing on

System-level software and products. • Focusing on:

– Change Management and effective Agile Transitions– Enterprise-scale Agility– Lean, Kanban, and agility for special circumstances– Using Retrospectives and Systems Thinking to identify and address deep issues with

how product development organizations execute– Agile Management

• Find me on:– [email protected] – @yuvalyeret – http://www.linkedin.com/in/yuvalyeret

Page 3: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS DONE

Why do we need to look outside Scrum?

What is this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Page 4: scrumban - taking scrum outside of its comfort zone

Enterprise Project Development

Scrum’s Comfort Zone

Scrum

Event-driven

R&D

Page 5: scrumban - taking scrum outside of its comfort zone

What is event-driven?• Helpdesk/Support activities

(driven by cases opened by customers, under SLA)

Page 6: scrumban - taking scrum outside of its comfort zone

What is event-driven?• Hardening/Packaging phases

(driven by defects found in testing)

Page 7: scrumban - taking scrum outside of its comfort zone

Backlog Pains

FlowReady?

Waste?Visibility

Page 8: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS DONE

Why do we need to look outside Scrum? What is

this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Page 9: scrumban - taking scrum outside of its comfort zone

Kanban

Page 10: scrumban - taking scrum outside of its comfort zone

Toyota Production System“The two pillars of the Toyota

production system are just-in-time and automation with a human touch, or autonomation. The tool

used to operate the system is kanban.”

Taiichi Ohno, Toyota Production System (adopted 1962)

Page 11: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS DONE

Scrum Task Board

Elad Inbar

Mushon Inbar

Elad

Mushon

Page 12: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS DONE

What’s the problem?

http://moduscooperandi.com

Elad Inbar

Mushon

Inbar

Elad

Mushon

Mushon

Mushon

Inbar

Inbar Mushon

Elad

Inbar Inbar

Inbar

Page 13: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS DONE

Late-binding, Multi-tasking limits

http://moduscooperandi.com

Inbar

Elad

MushonInbar

Mushon

Elad

Page 14: scrumban - taking scrum outside of its comfort zone

TO DO READY IN PROGRESS DONE

http://moduscooperandi.com http://moduscooperandi.com

Inbar

Elad

Mushon

Elad

(2) (4)

Voila! Kanban!

Page 15: scrumban - taking scrum outside of its comfort zone

TO DO READY IN PROGRESS DONE

Pull

http://moduscooperandi.com http://moduscooperandi.com

Inbar

Elad

Elad

MushonMushon

(2) (4)

Page 16: scrumban - taking scrum outside of its comfort zone

TO DO READY DESIGN CODING TESTING DONE

Workflow

Elad

Mushon

Inbar

Elad

Mushon

Inbar

(2) (2) (3) (3)

Page 17: scrumban - taking scrum outside of its comfort zone

Throughput

Work in Progress

Throughput

Page 18: scrumban - taking scrum outside of its comfort zone

Teamwork

• Enhances Teamwork– Team focus on goals that add

value not individual tasks• Encourages Swarming

http://www.flickr.com/photos/markop/2523825358/

Page 19: scrumban - taking scrum outside of its comfort zone

When Blocked…

• Lower priority work…– Spikes– Analysis

• Production Capability Improvement work…– Tool Automation– Refactoring– Personal Development– Innovation

• But NOT– Anything which will create

work downstream

NOTE: This doesn’t mean you should ONLY “sharpen the knife” when Blocked!!!

Page 20: scrumban - taking scrum outside of its comfort zone

Cumulative Flow Diagrams

http://www.agilemanagement.net

Page 21: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS(1)

DONE

Why do we need to look outside Scrum?

What is this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Page 23: scrumban - taking scrum outside of its comfort zone

• Easier transition for Scrum teams/organizations– Step by step migration – see

http://leansoftwareengineering.com/ksse/scrum-ban/

Page 24: scrumban - taking scrum outside of its comfort zone

Team Cadence/Heartbeat

Page 25: scrumban - taking scrum outside of its comfort zone
Page 26: scrumban - taking scrum outside of its comfort zone

Board reset

Page 27: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS(1)

DONE

Why do we need to look outside Scrum?

What is this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Page 28: scrumban - taking scrum outside of its comfort zone

When should I use Kanban?Extend Scrum to the whole

value stream– Upstream - Manage the

Backlog process - All the steps preceding the actual development sprints

– Downstream – Manage system testing, packaging, deployment

Page 29: scrumban - taking scrum outside of its comfort zone

When should I use Kanban?

• During hardening sprints• For the support/helpdesk teams/activities• For periods of heavy R&D

Page 30: scrumban - taking scrum outside of its comfort zone

When should I use Kanban?

• Another angle to start your transition from– Add visibility and WIP controls to current

workflow– Inspect the constraints/bottelenecks– Adapt the workflow, resources, processes – Scrum

It if it makes sense!– Drive for maximum throughput and fastest time to

delivery– Repeat

Page 31: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS(1)

DONE

Why do we need to look outside Scrum?

What is this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Page 32: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS(1)

DONE

Why do we need to look outside Scrum?

What is this Kanban/Scrumban ?

How does it

complement

Scrum?

When would we want to use it?

Detailed comparison between Scrum and Kanban

How to

manage in Kanban using TOC

Kanban Release Planning

Kanban and

Commitment/ Velocity

Flow of business value using Kanban

Scrumban implementation

Details

Advanced Kanban Concepts

Page 33: scrumban - taking scrum outside of its comfort zone

TO DO IN PROGRESS(1)

DONE

Detailed comparison between Scrum and Kanban

How to

manage in Kanban using TOC

Kanban Release Planning

Kanban and

Commitment/ Velocity

Flow of business value using Kanban

Scrumban implementation

Details

Advanced Kanban Concepts

Kanban Deep Dive

…Coming Soon

Page 35: scrumban - taking scrum outside of its comfort zone

www.agilemanagement.nethttp://leansoftwareengineering.com/ksse/scrum-ban

www.limitedwipsociety.orgavailagility.wordpress.com

aaron.sanders.name/ groups.yahoo.com/group/kanbandev/

www.diigo.com/user/yyeret/kanban

References and Material