Keep Calm and Use Kanban
•
1 like•871 views
There is much hype about Kanban since it was used by supermarkets and then perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach. As project managers and software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar. In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will dive into concepts such as limiting work in progress, Minimum Viable Product and Minimum Marketable Feature and see how these concepts can make our lives easier. During this session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Keep Calm and Use Kanban
Similar to Keep Calm and Use Kanban (20)
More from Acquate
More from Acquate (16)
Recently uploaded
Recently uploaded (20)
Keep Calm and Use Kanban
- 1. @TJGokcen | @codebyts | CEO
- 2. Keep Calm and Use Kanban Limit Your WIP
- 3. codebyts Software Development Microsoft House • Custom-tailored software solutions • Specializing in business flows, quality and processes Unique Approach • Capability of improving IT Requirements • Making sure it is an improvement for the whole organization
- 4. Process Improvement Collaborate with you to understand • The way you work • What you are working with To improve your quality and value to the customer • Lean • Agile codebyts
- 8. To explore how we can utilize a Kanban Board in our … management efforts
- 9. To explore how we can utilize a Kanban Board in our personal lives
- 10. Based on The Kanban Method
- 12. the interactions
- 13. and the impact of elements in a project
- 15. Lack of planning
- 17. Visualization
- 18. While you are travelling down this road there is a chance that one or more rocks of varying size may fall from the slopes on one or both sides of you. You should be aware of this before you travel this way so that you are cautious of this particular type of hazard.
- 20. A curved line with every point equal distance from the centre
- 30. Supermarkets: Where It All Began
- 35. WIP is the number of jobs you are working on at any one time.
- 36. With the timer ready 1. Write each letter or number on separate lines. letters and numbers would be ABCDEFGHIJ 3 6 9 12 15 18 21 24 27 30 5 10 15 20 25 30 35 40 45 50
- 37. With the timer ready 1. Write each word on separate lines. 2. Write each letter on separate lines, switching from letter to letter or number to number. In this case, first A, then 3, then 5, then B and so on… letters and numbers would be ABCDEFGHIJ 3 6 9 12 15 18 21 24 27 30 5 10 15 20 25 30 35 40 45 50
- 38. • Get into a circle • 3 projects: 1. Alphabet : A…Z 2. 3x: 3, 6, 9, 12… 3. 5x: 5, 10, 15, 20…
- 39. Backlog Analyze Dev ReadyTest Production doing done doing done
- 40. Analyst Developers Tester Our Team Product Owner Continuous Deployment
- 41. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 42. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 43. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 44. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 45. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 46. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 47. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrg
- 48. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 49. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 50. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 51. Backlog Analyze Dev ReadyTest Production doing done doing done dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 52. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2)
- 53. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 54. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 55. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 56. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 57. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 58. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg dfwgwrgrgwrgg
- 59. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg URGENT dfwgwrgrgwrggdfwgwrgrgwrgg
- 60. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg URGENT Expedited
- 61. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg dfwgwrgrgwrgg URGENT
- 62. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg dfwgwrgrgwrgg URGENT
- 63. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg URGENT dfwgwrgrgwrgg
- 64. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrggdfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg
- 65. Backlog Analyze (2) Dev (4) ReadyTest (2) Production doing done doing (2) done (2) dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Feature BUG Maint. Change Request dfwgwrgrgwrgg dfwgwrgrgwrgg Your wait time from here is 24 days
- 66. - 24 stories completed in 3 weeks - 8 stories per week
- 67. - 24 stories completed in 3 weeks - 8 stories per week - 160 stories in backlog - 160 / 8 = 20 weeks to complete (+/-)
- 68. - 24 stories completed in 3 weeks - 8 stories per week - 160 stories in backlog - 160 / 8 = 20 weeks to complete (+/-) - 3 weeks is 15 working days - I have 5 developers, that is 75 developer days
- 69. - 24 stories completed in 3 weeks - 8 stories per week - 160 stories in backlog - 160 / 8 = 20 weeks to complete (+/-) - 3 weeks is 15 working days - I have 5 developers, that is 75 developer days - 75 / 24 = 3.125 avg. developer days per story - This is the load factor in XP
- 71. Kanban Board in Hiring Process © http://kanbantool.com/use-cases/kanban-in-human-resources/interview-process#
- 72. Features Planning Development MarketingLegal Released doing done doing done dfwgwrgrgwrg g dfwgwrgrgwrgg dfwgwrgrgwrg g dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrg g dfwgwrgrgwrgg dfwgwrgrgwrgg Software Dev
- 73. Features Planning Development ReadyTest doing done doing done dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg Software Development Legal Marketing dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg dfwgwrgrgwrgg