Go Lean IT with Kanban


Published on

Lean IT provides transparency.
Avoids the old games between development and business.
Shows how business and development processes do not have to be poles apart.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Go Lean IT with Kanban

  1. 1. “ … . sprinters believe that, someday, somebody will run the 100 meters and the clock will read 0.00 ”
  2. 2. Lean IT Principles <ul><li>Eliminate waste </li></ul><ul><li>Amplify learning </li></ul><ul><li>Decide as late as possible </li></ul><ul><li>Deliver as fast as possible </li></ul><ul><li>Empower the team </li></ul><ul><li>Build quality in </li></ul><ul><li>See the whole </li></ul>  LEAN is the product of the Toyota Production System (TPS) 
  3. 3. Lean IT Benefits <ul><li>Lean IT provides transparency. </li></ul><ul><li>Avoids the old games between development and business. </li></ul><ul><li>Shows how business and development processes do not have to be poles apart. </li></ul>
  4. 4. Iterative & Incremental <ul><li>Incremental development is where various parts of the system are developed at different times or rates, and integrated as they are completed. </li></ul><ul><li>Iterative development is basically a rework scheduling strategy to revise and improve parts of the system. </li></ul><ul><li>Iterative development helps you improve your product </li></ul><ul><li>Incremental development improves your process. </li></ul>
  5. 5. Where to find them <ul><li>Scrum - Iterative development is is helping to “iterate” towards a final solution. Taking components such as registration, login, account administration and scheduling them into Iterations (1-4 weeks). Instead of delivering completed first version, software is developed in less risky fashion (as long as Sprints are sensibly planned). </li></ul><ul><li>Kanban – Iterative And Incremental development, to enable more efficient management at task level, and utilise cross-functional teams more. CI is essential. Provides even less risk, but more attentive management needed. </li></ul>
  6. 6. Kanban Principles <ul><li>Visualize the workflow </li></ul><ul><li>Limit WIP </li></ul><ul><li>Manage flow </li></ul><ul><li>Make Process Policies Explicit </li></ul><ul><li>Improve Collaboratively </li></ul><ul><li>Work In Progress (WIP) should be limited and something new should be started only when an existing piece of work is delivered or pulled by a downstream function </li></ul>
  7. 7. Roles – what roles? <ul><li>Kanban doesn't define roles, because how can one set of roles suit every company structure? </li></ul><ul><li>Competent management of Kanban process is essential, it cannot be a free-for-all. </li></ul><ul><li>Kanban model can be based on your level of resources. </li></ul><ul><li>Cross-functional teams will give stronger flexibility to your project. </li></ul>
  8. 9. Lean and Value Streams <ul><li>The value stream is an important concept in Lean development practices. </li></ul><ul><li>Analyse your value stream using your Kanban planning board. </li></ul><ul><li>Wastes could be large queues before a bottleneck in the system, or it could be a part of the system that sits idle, waiting for work. </li></ul><ul><li>A typical value stream for developing a feature would be: </li></ul><ul><li>Ready for Development, Development, Code Review, </li></ul><ul><li>Testing, and Demo to Customer </li></ul>
  9. 10. Compatibility <ul><li>Can Lean IT & Kanban work with Waterfall or any other step-down approach? </li></ul><ul><li>Don't throw proverbial baby out with bathwater </li></ul><ul><li>Kanban doesn't care if requirements are coming in dribs and drabs, or completely up-front. </li></ul><ul><li>As with any Agile or Lean process, you can always apply them to development process, at the very least. </li></ul>