Kanban Easyodc.pdf

658 views

Published on

see more on www.easyodc.com

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Kanban Easyodc.pdf

  1. 1. Ethos Technologies © 2010 Kanban brief Find more on www.easyodc.com
  2. 2. Ethos Technologies © 2010 Kanban Concept A Kanban is a physical card used in Toyota Production System (TPS) to support non- centralized "pull" production control. It has spread to the manufacturing industry all over the world as a tool of Lean Manufacturing. Now in Agile software development the visualization of projects, such as posting task cards on a wall, is a commonly seen practice, which is sometimes called "Software Kanban“. © Ethos Technologies 2005
  3. 3. Ethos Technologies © 2010 Terminology Relationship © Ethos Technologies 2005 Kanban: Visualization in Agile Projects
  4. 4. Ethos Technologies © 2010 Lean Principles from Toyota • Eliminate waste unnecessary code and functionality delay in the software development process unclear requirements bureaucracy slow internal communication • Amplify learning (requirement, tech etc.) • Decide as late as possible (until assumptions become facts) • Deliver as fast as possible • Empower the team (listen, encourage, support) • Build integrity in • See the whole © Ethos Technologies 2005
  5. 5. Ethos Technologies © 2010 Task Kanban Board © Ethos Technologies 2005
  6. 6. Ethos Technologies © 2010 Feature Kanban Board © Ethos Technologies 2005
  7. 7. Ethos Technologies © 2010 Burndown Chart © Ethos Technologies 2005
  8. 8. Ethos Technologies © 2010 Niko-niko (Smiley) Calendar © Ethos Technologies 2005
  9. 9. Ethos Technologies © 2010 © Ethos Technologies 2005 Customized Kanbans and E- Kanbans
  10. 10. Ethos Technologies © 2010 Maintenance Project © Ethos Technologies 2005 - sustaining process: Change Requests/Bug Reports come in a queue without schedule, mostly small and medium size. - no dedicated sustaining or maintenance team. Only commitment for a certain percentage of our resources.
  11. 11. Ethos Technologies © 2010 Kanban for maintenance project Experience shared from online Forums: • reduce work-in-progress (in fact it limits it completely, e.g. no more than 3 tasks in progress.) • balance capacity against demand (The number of tasks/cards are based on resource capacity. This number is evolved empirically every release.) • prioritize with color cards based on product owner inputs, service level agreement or external reasons. • More self-organization, less management supervision and better productivity • Resulted in better visual control, objective data measurement. © Ethos Technologies 2005
  12. 12. Ethos Technologies © 2010 Kanban 3 ViewPoints: Time, Task and Team © Ethos Technologies 2005 Team - The whole team should share information on time and tasks. People, more than “resource”, need motivation, positive pressure and a higher purpose (project goal) to work for within the reachable reality. Time Task
  13. 13. Ethos Technologies © 2010 Q&A © Ethos Technologies 2005

×