Kanban introduction - FE/MF team

903 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
903
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kanban introduction - FE/MF team

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

×