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

A Lean Introduction to Scrum and Kanban

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

A Lean Introduction to Scrum and Kanban

Introduction to Agile with Scrum and Kanban as specific examples.

ivargrimstad

May 15, 2014

Transcript

48 slides
  1. @ivar_grimstad A Lean Introduction to Scrum and Kanban A Lean

    Introduction to Scrum and Kanban Ivar Grimstad
  2. @ivar_grimstad A Lean Introduction to Scrum and Kanban Individuals and

    interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  3. @ivar_grimstad A Lean Introduction to Scrum and Kanban Horizon of

    Predictability Predictable Uncertain Totally Unpredictable Time
  4. @ivar_grimstad A Lean Introduction to Scrum and Kanban Scrum groups

    items in Iterations Product Backlog Sprint n Sprint n+1
  5. @ivar_grimstad A Lean Introduction to Scrum and Kanban Kanban pulls

    items from backlog Product Backlog Product
  6. @ivar_grimstad A Lean Introduction to Scrum and Kanban Scrum limits

    WIP per iteration ToDo In Progress Done C D A B E oh…sorry
  7. @ivar_grimstad A Lean Introduction to Scrum and Kanban Kanban limits

    WIP per state 2 2 ToDo In Progress Done C D A B E Get moving! ok
  8. @ivar_grimstad A Lean Introduction to Scrum and Kanban Scrum has

    cross-functional teams ToDo In Progress Done C D A B
  9. @ivar_grimstad A Lean Introduction to Scrum and Kanban Cross-functional teams

    optional in Kanban ToDo In Progress Done C D A B 2 2
  10. @ivar_grimstad A Lean Introduction to Scrum and Kanban Scrum measures

    Velocity Time Sprint 1 Sprint 2 Sprint 3 Sprint 4 V = 8 V = 7 V = 9 V = 8
  11. @ivar_grimstad A Lean Introduction to Scrum and Kanban Kanban measures

    average lead time ToDo In Progress Done 2 2 Flow
  12. @ivar_grimstad A Lean Introduction to Scrum and Kanban It is

    never the process itself that makes a software project succeed or fail

More Decks by ivargrimstad

Other Decks in Programming