Kanban ja Scrum
Ahti Haukilehto
Sovelto
Microsoft Regional Director, Finland
Microsoft Certified Trainer
Professional Scru...
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...
Kanban Requirements
1. Visual representation of your ACTUAL process
2. Limit “Work in Progress” (WIP)
3. Track and optimiz...
Mitä on kanban
• Visualizing the Workflow.
• Iterationless development.
• Limiting work-in-progress.
• Monitoring cycle ti...
Scrum-ban
Scrum:n ja Kanban:n yhdistelmä
Isoin haaste: Srumin sprintit vrs. Kanbanin jatkuva prosessi
Sprintin vaihtoehtoja
Kalvo: Henrik Kniberg:n luento

Sprints

week 1

week 2

week 3

week 4

Sprint 1
Plan & commit

Sep...
Connecting Scrum & Kanban
Kalvo: Henrik Kniberg:n luento

Step 1
Feature
team 1
Scrum

Feature
team 2
Scrum

Step 2
Featur...
Yhteenveto
• Scrum ja Kanban tarkkailevat hieman eri asioita
• Mutta on paljon yhteistä
• Scrumia on helppo säätää Kanbani...
Kanban ja Scrum
Kanban ja Scrum
Upcoming SlideShare
Loading in...5
×

Kanban ja Scrum

232

Published on

Sovelto Iltapäiväseminaari 7.2.2014
Ahti Haukilehto

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
232
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kanban ja Scrum

  1. 1. Kanban ja Scrum Ahti Haukilehto Sovelto Microsoft Regional Director, Finland Microsoft Certified Trainer Professional Scrum Trainer
  2. 2. 2
  3. 3. Scrum 3
  4. 4. Scrum 4
  5. 5. Scrum Board 6
  6. 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
  7. 7. Kanban Requirements 1. Visual representation of your ACTUAL process 2. Limit “Work in Progress” (WIP) 3. Track and optimize “flow” 8
  8. 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
  9. 9. Scrum-ban Scrum:n ja Kanban:n yhdistelmä Isoin haaste: Srumin sprintit vrs. Kanbanin jatkuva prosessi
  10. 10. 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)
  11. 11. 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
  12. 12. 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×