Learn How to Manage Backlog from Toyota Kanban Concepts, Agile Roots 2014

  • 2,092 views
Uploaded on

Here is the deck I presented at Agile Roots 2014 event. …

Here is the deck I presented at Agile Roots 2014 event.
http://www.agileroots.com/
http://www.agileroots.com/presentation/learn-how-to-manage-backlog-from-toyota-kanban-concepts/

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,092
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. [June 20, 2014]
  • 2. Japanese edition written by me  Korean edition
  • 3. English edition Japanese edition translated by me 
  • 4. English edition Japanese edition translated by us 
  • 5. Entrance Exit Development period
  • 6. Task Task Task Task Task Task Task Task Task Task and Box them all by the exit as planned Plan them at the entrance
  • 7. Task Task Task Task Task Task Task Task Task Task Task Task Task Development period
  • 8. Correct!!
  • 9. Correct!! If quality or schedule is in danger, you have to reduce the scope to keep the quality and schedule.
  • 10. “Punt” was general term and common sense for updating plan when I worked for Microsoft.
  • 11. 全開発期間 i t e r Sprint a t i o Sprint n ; i t Sprint Development period Iterative sprint running boxes brimming tasks into the next buckets. All buckets would be full and the workload can be leveled.
  • 12. http://pc.watch.impress.co.jp/docs/2005/1121/gyokai142.htm http://www.chunichi.co.jp/hold/2008/yui_no_kokoro/list/200805/CK2008051402011210.html in a Basket. Laminated.
  • 13. Parts Parts Parts Production Division Building Division Completed Consumed Stick on Remove draw next parts Kanban mainly shows: - Model # of the parts - Location of Building Division the parts sent to, like a post office tag
  • 14. Stick Kanban as soon as you completed the parts Parts must be matched with Kanban one-to-one Don’t start production of the parts w/o Kanban Make parts in order of Kanban arrival Pay attention to non- circulating Kanban! Reduce the number of the Kanban Don’t send defective to downstream Coordinate quantity of the inventory w/ season
  • 15. To prevent losing the parts you completed.
  • 16. Total # of parts should equals to total # of Kanban for accurate parts tracking.
  • 17. Even if you have spare time, making parts w/o Kanban is just making excess inventory. You can make the parts only when you have the Kanban.
  • 18. Kanban arrival order should be respected as parts production order. Changing the order might save your time, but it can cause waiting time in the downstream as well.
  • 19. Less quantity of inventory can be achieved w/ this rule. But too less Kanban makes the parts not arriving on time, so Reduce the Kanban bit by bit carefully to find suitable volume of inventory.
  • 20. If you lost any Kanban, the parts won't be arrived on time. Important to circulate all Kanban w/o delay.
  • 21. If you make any defect, the # of parts will be not enough and that would stop downstream of production line.
  • 22. You can do it by coordinating # of Kanban according to the seasonal demand. (ex. air conditionar)
  • 23. Electronic Kanban must exist physically. It cannot be fully electronized.
  • 24. This is not essential.
  • 25. He is about to start production of the parts described on the Kanban. Kanban can be stored on a Wall or in a Basket. Ticket can be stored on a Wall or in ITS as well. http://itpro.nikkeibp.co.jp/article/JIREI/20080924/315302/
  • 26. Correct!!
  • 27. Correct!!
  • 28. triaged by lead Issue Issue Issue Tester Lead Found Closed draw next issues Piled as test cases resolved by dev verified by test Stick on Ticket mainly shows: - Details of the issue - Name of person the issue sent to, like a post office tag
  • 29. File Ticket as soon as you found an issue Issues must be matched with Ticket one-to-one Don’t start act against the issue w/o Ticket Do issues in order of Ticket priority Pay attention to non- circulating Ticket! Reduce the number of the Ticket Don’t send defective to downstream Coordinate quantity of the backlog w/ velocity
  • 30. To prevent forgetting the issue you found.
  • 31. Total # of issues should equals to total # of Tickets for accurate issue tracking.
  • 32. You can start the task only when you have the Ticket. If you have no Ticket for it, you have to file Ticket first. You can see who is doing what in ITS w/ this rule.
  • 33. Ticket priority order should be respected. Changing the order w/ only your convenience might save your time, but it can cause waiting time in the downstream as well.
  • 34. # of Ticket have to hit zero by exit of the sprint.
  • 35. If you neglect any Tickets, the issue won't be resolved by the exit. Watch any issues left undone for long time at one person. Important to circulate all Tickets w/o delay.
  • 36. If you make any defect or blocker issue, that would stop downstream of production line.
  • 37. Velocity means capacity of time box or capacity of your team in one sprint. You can plan the amount of backlog according to the velocity.
  • 38. Stick Kanban as soon as you completed the parts Parts must be matched with Kanban one-to-one Don’t start production of the parts w/o Kanban Make parts in order of Kanban arrival Pay attention to non- circulating Kanban! Reduce the number of the Kanban Don’t send defective to downstream Coordinate quantity of the inventory w/ season Please find the similarities with the Ticket!!
  • 39. File Ticket as soon as you found an issue Issues must be matched with Ticket one-to-one Don’t start act against the issue w/o Ticket Do issues in order of Ticket priority Pay attention to non- circulating Ticket! Reduce the number of the Ticket Don’t send defective to downstream Coordinate quantity of the backlog w/ velocity Please find the similarities with the Kanban!!
  • 40. Backlog → Backlog → Backlog →
  • 41. days altitude 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 The glide path is approaching!! glide path flight path Backlog We have to have all backlog landed by the exit.
  • 42. Note: both includes WIP. (Inventory items that are Working in Progress.)
  • 43. Eventually, build and deliver to the customer.
  • 44. How can we do that w/o resolving issues increasing during sprint? Hey, what magic happens?
  • 45. Keep the Suitable Quantity of the Inventory Items (Remaining Sprint Backlog)!!
  • 46. days quantity 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 0 5 10 15 20 25 30 35 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 glide path flight path The glide path shows Suitable Quantity of remaining backlog roughly. If flight path is deviating far from the glide path, you need to update the plan.
  • 47. Feel free to Contact Me if you have any question, concern or interests.