Practicing agile theory

Limiting WIP & reasons for high WIP My first post on Kanban  deserved a sequel for sure! While it isn’t possible to have literally no work in progress, the overall goal of a project team is to finish as many things as they can, and not be in a state of continually starting. Having too much #WIP makes this goal even more difficult.  The impact of too much WIP on efficiency and throughput is one of the reasons it is often regarded as a concern. According to studies, the cost of context change is frequently far more than people anticipate. It is evident that dropping one object and taking up another cannot be done in such a way that no time or energy is spent between the two. However, there is sufficient evidence to suggest that the loss is rarely worth the gain. These apparent consequences of having too much going on are easy to identify once you know what you're looking at. Looking around the team, you'll notice that there are many tasks open, few of which are done, and man...

  A wise man once said-   Agile is more than just standing up and burning down!  Talking of KANBAN, one of the key principles is – Visualize the flow of work In other words,  "manage work instead of people" . It says "people tend to manage people because it's visible . If the work cannot be seen, the human nature tends to measure what can be seen, but that doesn't make it the right thing to measure"      Best,    Jasdev Singh ( S crum S ervant)