Kanban ja Scrum

Ahti HaukilehtoSovelto

Microsoft Regional Director, FinlandMicrosoft Certified TrainerProfessional Scrum Trainer

2

Scrum

3

Scrum

4

Scrum Board

6

Kanban

“Kanban is not a software development cycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process“

-- David Anderson

(originator of Kanban)

7

Kanban Requirements

1. Visual representation of your ACTUAL process

2. Limit “Work in Progress” (WIP)

3. Track and optimize “flow”

8

Mitä on kanban

• Visualizing the Workflow.

• Iterationless development.

• Limiting work-in-progress.

• Monitoring cycle time (internal)• Lead time (what customer sees)

• Experimenting with the process.

9

Scrum-ban

Scrum:n ja Kanban:n yhdistelmäIsoin haaste: Srumin sprintit vrs. Kanbanin jatkuva prosessi

Sprintin vaihtoehtoja

Sprints

Kalvo: Henrik Kniberg:n luento

week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8

Sprint 1

Plan & commit Review(release?)

Separate cadences week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8

Planning cadence (2w)

Sprint 2

Retrospective

Release cadence (1w)

Retrospectives (4w)

Event-driven week 1 week 2 week 3 week 4 week 5 week 6 week 7 week 8

Planning (on demand)

Release (on demand)

Retrospectives (4w)

Operations / support team

Connecting Scrum & Kanban

12

Featureteam 1

Featureteam 2

Featureteam 2

Featureteam 1

Featureteam 2

Featureteam 2

Scrum Scrum Scrum Scrum Scrum Scrum

Scrum

Operations / support team

Featureteam 1

Featureteam 2

Featureteam 2

Scrum Scrum Scrum

Kanban

Step 1 Step 2 Step 3Kalvo: Henrik Kniberg:n luento

Yhteenveto

• Scrum ja Kanban tarkkailevat hieman eri asioita

• Mutta on paljon yhteistä

• Scrumia on helppo säätää Kanbanin suuntaan (Scrum-but tai Scrum-ban) • Ja niin usein tehdäänkin