The question often put before Lean-Agile coaches or consultants is – what does Lean-Agile say about Estimation? Good, bad… or ugly? In general, the Lean-Agile community is negative about Estimation.
I have spoken about this topic in several conferences in India in the last year. After my talk, I would get several requests to share a “template” of the Upstream
Digité products have been the core execution platform for many IT service companies in India. We have a leadership position in the market, given that 4 of the Top 5
I have seen people focus a lot on what the WIP limit should be for a Value Stream stage of a Kanban system. However, once the WIP limit is known,
Personal productivity and time management tools/methods have always been a subject of interest. Numerous methods and tools have been developed over the years. However, few seem to stick over time.
One of the important aspects of The Kanban Method is Class of Service (CoS). CoS is a risk categorization mechanism for any work item. We identify 4 Classes of Service
Many teams adopting Kanban come from Agile background. Agile thinking has discouraged the use of Due Dates. Due Dates breed undesirable behavior. Focus on Due Dates results in teams working
Projects are often executed by dynamic teams. They start with a small core team and as the project gains momentum, add resources over time. This is commonly seen in IT
Over the last few years of steady-state usage of Kanban in our product management and engineering teams, we have achieved a number of dramatic improvements. Even considering that for us,
Software development using Kanban principles has not focused on Effort Tracking (though there hasn’t been a strong position against the same). At Digité, we were practitioners of Iterative Software Development.
Try SwiftKanban Enterprise Plan FREE for 30 days.