• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Kanban introduction - FE/MF team

Kanban introduction - FE/MF team






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Kanban introduction - FE/MF team Kanban introduction - FE/MF team Presentation Transcript

    • Introducing Kanban
      On process tuning, WIP limits and getting things done
    • Introducing Kanban
      a picture says more than a thousand words
    • Overview
      Why scrum isn’t enough
      Extending the process
      Limiting WIP
      Daily stand-up
      Deploy when ready
      Visualizing the flow
      Continuous process improvement
    • Why scrum isn’t enough
      Hard to commit to a two-week plan
      New issues on a daily basis
      Failing sprints due to unexpected tasks
       Iterative (scrum) process seems to make no sense for a team with a high maintenance load
    • Extending the process
      the scrum process
    • Extending the process
      our kanban process
    • Limiting WIP
      Creating code =/= creating value
      Limit WIP for each state
      Get Things Done by aiming to reduce the WIP
      Reduce story size (1  5 days of development)
      Go with the flow, drop the time-boxing
      Managing WIP limits
    • Daily stand-up
      Scrum: (individual)
      What did you do yesterday
      What are you going to do today
      Are you stuck somewhere
      Kanban: (team)
      What is likely to go on and off the board today
      What is likely to move on the board
      Where is traffic stuck and how can we fix it
    • Deploy when ready
      Adding a WIP limit to the final step
      Help each other to finish the stories in the flow
      Not allowed to start working on new stories
      Self-improvement, documentation, getting coffee or food, prepare deploy, ...
       Deploy when ready and tested  immediate value vs. Iterative deployment
    • Visualizing the flow
      Identify bottlenecks and help where needed
      Clear indication of project evolution to the business
      Recurring bottlenecks can be identified and avoided on a higher level
    • Continuous process improvement
      Managing WIP
      Managing steps in the flow
      Creating a consistent development pace
      Explicit process policies allow for critical analysis, discussion and improvement
      Ideas? Speak up!