Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Scrumban Style

Shani Raba
September 15, 2013

Scrumban Style

scrum and kanban - making the most of both

Shani Raba

September 15, 2013
Tweet

More Decks by Shani Raba

Other Decks in Technology

Transcript

  1. • Split your Organization • Split your work • Split

    Time • Optimize the release • Optimize the Process Scrum
  2. • What is the meaning of Kanban? • What is

    Kanban? – Signaling System – Visual – Limited Supply Kanban
  3. DEEP DIVE Let’s learn about the tools - Time Boxed

    iterations\sprints - Limit WIP - Lead Time - Resist a change - Poker Planning - Velocity
  4. Time Boxed iterations • Origin: Scrum • Idea: choose a

    length and stick with it • Why: Establish a Rhythm
  5. Free Style: Time Boxed #1 Week 1 Week 2 Week

    3 Week 4 Week 5 Week 6 Week 7 Week 8 Retro Plan Release aka: Fastrekanization
  6. Free Style: Time Boxed #2 Week 1 Week 2 Week

    3 Week 4 Week 5 Week 6 Week 7 Week 8 Retro Plan Release On demand
  7. Limits WIP • Origin: Kanban • Idea: limit the amount

    of items that can be in- progress • Why: GTD => get the current items done before starting new stuff (eliminating waste)
  8. Limit WIP • In Quality Software Management: Systems Thinking, Gerald

    Weinberg proposed a rule of thumb to calculate the waste caused by project switching
  9. Lead Time • Origin: Kanban • Idea: Measure the average

    time for an item to reach to DONE • Why: Metric for measuring productivity and improvement
  10. Lead Time - Experiments • Experiment #1: – Developers =

    2 – WIP Limit = 1 • Experiment #2: – Developers = 4 – WIP Limit = 8 • Experiment #3: – Developers = 4 – WIP Limit = 4 We’ve got 2 new developers Let’s increase the limit to 8 Let’s limit to 4
  11. Resists a Change (and response time) • Origin: Scrum •

    Idea: Scrum resists a change within and iteration • Why: scrum team commits to a sprint to get something DONE
  12. Resists a Change (and response time) • How long will

    it take to react to Feature E (new feature)?
  13. Estimations and Velocity (Poker Planning) • Origin: Scrum • Idea:

    Poker Planning • Why: In order to measure yourself (scale) • Why: based on the past (velocity) you can predict the future
  14. Velocity • Origin: Scrum • Idea: amount of work a

    TEAM can do from time to time. • Why: based on the past (velocity) you can predict the future
  15. Velocity • My team can do 25 SP per sprints,

    how long will it take me to run 100SP?
  16. • Visualize your Flow • Prioritize • Measure your Execution

    (either lead time or Velocity) • Limit your Work • Communicate During a change Tips
  17. • Don’t be afraid o Experiment and fail • Retro

    It The Only big failure is the failure to learn from a failure Final Words
  18. Appendix The rest • Multi tasking with humans – •

    http://www.codinghorror.com/blog/2006/09/the-multi-tasking-myth.html • http://www.joelonsoftware.com/articles/fog0000000022.html • http://foreachbiscuit.wordpress.com/2007/12/20/context-switching-on-multiple- projects/