Sovelto Iltapäiväseminaari 7.2.2014 Ahti Haukilehto

1. Kanban ja Scrum
Ahti Haukilehto
Sovelto
Microsoft Regional Director, Finland
Microsoft Certified Trainer
Professional Scrum Trainer

2. 2

3. Scrum
3

4. Scrum
4

6. Scrum Board
6

7. 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

8. Kanban Requirements
1. Visual representation of your ACTUAL process
2. Limit “Work in Progress” (WIP)
3. Track and optimize “flow”
8

9. 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

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

11. Sprintin vaihtoehtoja
Kalvo: Henrik Kniberg:n luento
Sprints
week 1
week 2
week 3
week 4
Sprint 1
Plan & commit
Separate cadences
week 5
week 6
week 7
week 8
Sprint 2
Review
(release?)
Retrospective
week 1
week 2
week 3
week 4
week 5
week 6
week 7
week 8
week 1
week 2
week 3
week 4
week 5
week 6
week 7
week 8
Retrospectives (4w)
Planning cadence (2w)
Release cadence (1w)
Event-driven
Retrospectives (4w)
Planning (on demand)
Release (on demand)

12. Connecting Scrum & Kanban
Kalvo: Henrik Kniberg:n luento
Step 1
Feature
team 1
Scrum
Feature
team 2
Scrum
Step 2
Feature
team 2
Scrum
Feature
team 1
Scrum
Feature
team 2
Scrum
Step 3
Feature
team 2
Scrum
Operations / support team
Scrum
Feature
team 1
Scrum
Feature
team 2
Scrum
Feature
team 2
Scrum
Operations / support team
Kanban
12

14. 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