• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Kanban/Scrumban - taking scrum outside its comfort zone
 

Kanban/Scrumban - taking scrum outside its comfort zone

on

  • 27,339 views

Kanban is a way to implement a Lean process, focused on flow, time to ...

Kanban is a way to implement a Lean process, focused on flow, time to
market, and waste removal. Understand the Lean principles behind Kanban, its
relation to Agile/Scrum, and how the two can complement each other into
Scrumban. Understand where Kanban should be considered.

Statistics

Views

Total Views
27,339
Views on SlideShare
25,998
Embed Views
1,341

Actions

Likes
39
Downloads
805
Comments
5

26 Embeds 1,341

http://www.projectmanagement.com 566
http://www.agilesparks.com 196
http://landike.blogspot.com 161
http://www.slideshare.net 123
http://www.scoop.it 67
http://agilesparks.com 64
http://ubuntu.samity.org 51
http://agilesparks.wordpress.com 43
http://nessitolleri.blogspot.com 19
http://nessitolleri.blogspot.fi 14
http://germanflores.com 6
http://yuvalyeret.com 5
http://www.mefeedia.com 4
http://www.agilesparks.co.il 4
http://www.iliokb.com 3
http://landike.blogspot.in 2
http://wiki.limbicnutrition.com 2
https://twimg0-a.akamaihd.net 2
http://iscrum.ning.com 2
http://www.lmodules.com 1
http://clickwatchlearn.blogspot.com 1
http://paper.li 1
http://agilesparks.co.il 1
http://landike.blogspot.ca 1
http://translate.googleusercontent.com 1
http://landike.blogspot.de 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

15 of 5 previous next Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Scrum doesn’t

Kanban/Scrumban - taking scrum outside its comfort zone Kanban/Scrumban - taking scrum outside its comfort zone Presentation Transcript

  • Scrumban
    Taking Scrum outside it’s comfort zone
  • About Me
    Agile Coach, Certified Scrum Practitioner, Certified Scrum Product Owner
    13 years experience leading R&D organizations (including VP R&D) focusing on System-level software and products.
    Focusing on:
    Change Management and effective Agile Transitions
    Enterprise-scale Agility
    Lean, Kanban, and agility for special circumstances
    Using Retrospectives and Systems Thinking to identify and address deep issues with how product development organizations execute
    Agile Management
    Find me on:
    yuval@agilesparks.com
    @yuvalyeret
    http://www.linkedin.com/in/yuvalyeret
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How does it complementScrum?
  • Scrum’s Comfort Zone
    Event-driven
    Scrum
    Enterprise Project Development
    R&D
  • What is event-driven?
    Helpdesk/Support activities (driven by cases opened by customers, under SLA)
  • What is event-driven?
    Hardening/Packaging phases (driven by defects found in testing)
  • Backlog Pains
    How do we manage the flow around the backlog?
    How do we ensure we have enough analysis/stories ready for development?
    How do we avoid preparing/analysing too many stories for the development to work on (Waste)?
    We love the visibility Scrum provides us for the development lifecycle. How do we extend it to the backlog / story elaboration phases?
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How does it complementScrum?
  • Kanban
  • Toyota Production System
    “The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation. The tool used to operate the system is kanban.”
    TaiichiOhno, Toyota Production System (adopted 1962)
  • Scrum Task Board
    Elad
    Inbar
    Mushon
    Inbar
    Elad
    Mushon
  • What’s the problem?
    Elad
    Inbar
    Mushon
    Inbar
    Elad
    Mushon
    Mushon
    Mushon
    Inbar
    Inbar
    Mushon
    Elad
    Inbar
    Inbar
    Inbar
    http://moduscooperandi.com
  • Late-binding, Multi-tasking limits
    Inbar
    Elad
    Mushon
    Inbar
    Mushon
    Elad
    http://moduscooperandi.com
  • Voila! Kanban!
    Inbar
    Elad
    Mushon
    Elad
    http://moduscooperandi.com
    http://moduscooperandi.com
  • Pull
    Mushon
    Mushon
    Inbar
    Elad
    Elad
    http://moduscooperandi.com
    http://moduscooperandi.com
  • Workflow
    Inbar
    Elad
    Mushon
    Inbar
  • Throughput
  • Teamwork
    Enhances Teamwork
    Team focus on goals that add value not individual tasks
    Encourages Swarming
    http://www.flickr.com/photos/markop/2523825358/
  • When Blocked…
    Lower priority work…
    Spikes
    Analysis
    Production Capability Improvement work…
    Tool Automation
    Refactoring
    Personal Development
    Innovation
    But NOT
    Anything which will create work downstream
    NOTE: This doesn’t mean you should ONLY “sharpen the knife” when Blocked!!!
  • Cumulative Flow Diagrams
    http://www.agilemanagement.net
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How does it complementScrum?
  • Easier transition for Scrum teams/organizations
    Step by step migration – see http://leansoftwareengineering.com/ksse/scrum-ban/
  • Team Cadence/Heartbeat
  • Board reset
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How does it complementScrum?
  • When should I use Kanban?
    Extend Scrum to the whole value stream
    Upstream - Manage the Backlog process - All the steps preceding the actual development sprints
    Downstream – Manage system testing, packaging, deployment
  • When should I use Kanban?
    During hardening sprints
    For the support/helpdesk teams/activities
    For periods of heavy R&D
  • When should I use Kanban?
    Another angle to start your transition from
    Add visibility and WIP controls to current workflow
    Inspect the constraints/bottelenecks
    Adapt the workflow, resources, processes – Scrum It if it makes sense!
    Drive for maximum throughput and fastest time to delivery
    Repeat
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How does it complementScrum?
  • Why do we need to look outside Scrum?
    When would we want to use it?
    What is this Kanban/Scrumban?
    How to managein Kanban using TOC
    Kanban Release Planning
    Kanban and Commitment/ Velocity
    Flow of business value using Kanban
    Scrumbanimplementation Details
    Advanced Kanban Concepts
    How does it complementScrum?
    Detailedcomparison between Scrum and Kanban
  • Kanban Deep Dive…
    Coming Soon…
    How to managein Kanban using TOC
    Kanban Release Planning
    Kanban and Commitment/ Velocity
    Flow of business value using Kanban
    Scrumbanimplementation Details
    Advanced Kanban Concepts
    Detailedcomparison between Scrum and Kanban
  • Ask us how
    info@agilesparks.com, yuval@agilesparks.com
    Get the slides at http://www.slideshare.net/yyeret/
  • References and Material
    Scrumban - http://leansoftwareengineering.com/ksse/scrum-ban/
    kjscotland@yahoo.co.ukhttp://availagility.wordpress.com
    aaron@sanders.namehttp://aaron.sanders.name/
    http://groups.yahoo.com/group/kanbandev/