0
Who am I? <ul><li>Tomas Björkholm </li></ul><ul><li>Scrum, Agile & Lean coach/mentor </li></ul><ul><li>Contact: </li></ul>...
Scrum characteristics <ul><li>Transparency –  exposes  problems early and builds trust </li></ul><ul><li>Strict prioritiza...
Kanban characteristics <ul><li>Wanted elements </li></ul><ul><ul><li>Clear priority </li></ul></ul><ul><ul><li>Focus (redu...
Prescriptive vs adaptive More prescriptive More adaptive Tomas Björkholm  XP (13) Scrum (9) Kanban (3) Do Whatever (0) RUP...
Roots of Kanban (Toyota) Buyer Supplier Tomas Björkholm  看板 ” Visual Card” Receive Consume Detach Ship Allocate Manufactur...
Kanban basic Tomas Björkholm Kanban limit of 3 A Kanban = new feature, bug or change request 1 2 3 Product Owner Team
Kanban board for non cross-functional teams Tomas Björkholm Deploy Dev DB Design Req Prod Proj Perf Build Deploy Dingo Fix...
Kanban board  –  Scrum look-a-like - Used for improvement projects within operation teams -  Tomas Björkholm Done To do Pr...
Kanban board  –  A typical scenario Tomas Björkholm Done To do Prod Build Working on qdb sö bmx kjhf woi gi sfs ara jkh hd...
Kanban board – For small stories (< 1w)   - Add a buffer - Tomas Björkholm SAÖF SDJ A-LRJ SAJ On planning meeting break do...
Kanban process Week 1 Week 2 Week 3 Timeline Sprint-planning Review and Retrospective Daily Scrum Daily meeting Tomas Björ...
Result Tomas Björkholm Timeline Time spent Unplanned Daily duties Pre-emptive work
That’s it! Questions?
Upcoming SlideShare
Loading in...5
×

Agile och Kanban på driftavdelningen - Tomas Bjorkholm

818

Published on

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

  • Be the first to like this

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

No notes for slide
  • Varför fungerar inte Scrum
  • In Scrum and Kanban you are supposed to add stuff. In RUP, you are supposed to remove stuff. Scrum + XP Kanban + daily standup Scrum team using use cases or limiting WIP Don’t call it Scrum if it isn’t.
  • blood, arteries, oxygen, heart beat
  • Transcript of "Agile och Kanban på driftavdelningen - Tomas Bjorkholm"

    1. 1. Who am I? <ul><li>Tomas Björkholm </li></ul><ul><li>Scrum, Agile & Lean coach/mentor </li></ul><ul><li>Contact: </li></ul><ul><ul><li>0708-251632 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>10-01-10 Agile/Kanban på driftavdelningen
    2. 2. Scrum characteristics <ul><li>Transparency – exposes problems early and builds trust </li></ul><ul><li>Strict prioritization – the fundamental for focus </li></ul><ul><li>Empirical (invent/implement) & adaptive </li></ul><ul><ul><li>Short feedback loop </li></ul></ul><ul><ul><li>Continuous improvement (Kaizen) </li></ul></ul><ul><ul><li>Frequent & regular delivery of working software </li></ul></ul><ul><ul><li>Plans are needed, but they are always wrong </li></ul></ul><ul><li>Cross-functional self-organizing team </li></ul><ul><li>Pull scheduling – team chooses how much work to commit to </li></ul><ul><li>Timeboxing </li></ul><ul><li>Face-to-face communication </li></ul><ul><li>Simple tools </li></ul>Tomas Björkholm But, operation can’t commit, we don’t know how much support there is Limit work-in-progress Balance demand to capacity
    3. 3. Kanban characteristics <ul><li>Wanted elements </li></ul><ul><ul><li>Clear priority </li></ul></ul><ul><ul><li>Focus (reduce work-in-progress) </li></ul></ul><ul><ul><li>Limit demand after capacity </li></ul></ul><ul><ul><li>Transparency </li></ul></ul><ul><li>Key metrics is cycle time rather than velocity </li></ul>Tomas Björkholm Cycle time = Capacity Work in progress
    4. 4. Prescriptive vs adaptive More prescriptive More adaptive Tomas Björkholm XP (13) Scrum (9) Kanban (3) Do Whatever (0) RUP (120+) <ul><li>Whole team </li></ul><ul><li>Coding standard </li></ul><ul><li>TDD </li></ul><ul><li>Collective ownership </li></ul><ul><li>Customer tests </li></ul><ul><li>Pair programming </li></ul><ul><li>Refactoring </li></ul><ul><li>Planning game </li></ul><ul><li>Continuous integration </li></ul><ul><li>Simple design </li></ul><ul><li>Sustainable pace </li></ul><ul><li>Metaphor </li></ul><ul><li>Small releases </li></ul><ul><li>Scrum Master </li></ul><ul><li>Product Owner </li></ul><ul><li>Team </li></ul><ul><li>Sprint planning meeting </li></ul><ul><li>Daily Scrum </li></ul><ul><li>Sprint review </li></ul><ul><li>Product backlogt </li></ul><ul><li>Sprint backlog </li></ul><ul><li>BUrndown chart </li></ul><ul><li>Visualize the workflow </li></ul><ul><li>Limit WIP </li></ul><ul><li>Measure and optimize lead time </li></ul>
    5. 5. Roots of Kanban (Toyota) Buyer Supplier Tomas Björkholm 看板 ” Visual Card” Receive Consume Detach Ship Allocate Manufacture Kan Ban
    6. 6. Kanban basic Tomas Björkholm Kanban limit of 3 A Kanban = new feature, bug or change request 1 2 3 Product Owner Team
    7. 7. Kanban board for non cross-functional teams Tomas Björkholm Deploy Dev DB Design Req Prod Proj Perf Build Deploy Dingo Fix Dingo Dingo Dingo Product backlog Capacity or Demand limitation Empty slot Used slot Work in progress Waiting for a free kanban in Req’s column. Places on prio order Dingo Dingo Dingo Next
    8. 8. Kanban board – Scrum look-a-like - Used for improvement projects within operation teams - Tomas Björkholm Done To do Prod bmx Build Limit, max 2 tasks per memb. Working on qdb sö dh bmx er kjhf er woi gi sfs ara jkh hd tes SAÖF SDJ A -LRJ SAJ Prio Urgent Daily duty 2 jfh wer Capacity or Demand limitation On planning meeting break down and fill empty slots bmx Perf qdb sö dh sfs jfh wer 1
    9. 9. Kanban board – A typical scenario Tomas Björkholm Done To do Prod Build Working on qdb sö bmx kjhf woi gi sfs ara jkh hd tes SAÖF SDJ A -LRJ SAJ Prio Urgent Daily duty 2 wer On planning meeting break down and fill empty slots bmx Perf qdb sö dh sfs jfh wer 1 hd tes hd 3
    10. 10. Kanban board – For small stories (< 1w) - Add a buffer - Tomas Björkholm SAÖF SDJ A-LRJ SAJ On planning meeting break down and fill empty slots in prepared queue. Team pulls from Prepared queue whenever there is a empty slot. Done To do Prod bmx Build Working on qdb sö dh bmx er kjhf er woi gi sfs ara jkh hd tes Prio Urgent Daily duty 2 jfh wer bmx Perf qdb sö dh sfs jfh wer 1 Prepared Backlog Install Config bmx er kjhf bmx er kjhf
    11. 11. Kanban process Week 1 Week 2 Week 3 Timeline Sprint-planning Review and Retrospective Daily Scrum Daily meeting Tomas Björkholm release 1.3.0 Sprint-planning Releases can still be periodic Week 4 Very important to improve Produkt Backlog
    12. 12. Result Tomas Björkholm Timeline Time spent Unplanned Daily duties Pre-emptive work
    13. 13. That’s it! Questions?
    1. A particular slide catching your eye?

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

    ×