- All
- Agile
- Agile ALM
- Agile Marketing
- Agile Metrics
- Agile Tool
- AI
- ALM
- ALM Tools
- Application Lifecycle Management
- Application Portfolio Management
- Artificial Intelligence
- Blogs
- Bytes
- Capacity Planning
- Collaboration
- Essential SAFe
- Everyday Kanban
- Hybrid Agile
- Kanban
- Kanban board
- Kanban cycles
- Kanban for Distributed Teams
- Kanban Tool
- Leadership
- Lean
- Lean ALM
- Lean Software Development
- Lean SSC
- Lean/ Kanban
- Management
- Modern Management
- News and Events
- Newsletter
- Portfolio Kanban
- Portfolio Management
- PPM
- Process Maturity
- Product Updates
- Product Webinars
- Project Management
- Remote Working
- Requirements Management
- SAFe
- Scaled Agile ALM
- SwiftEnterprise
- SwiftEnterprise Updates
- Uncategorized
- Upcoming Webinars
- Visual Management
- Visualization
- Webinars
- WIP
March 19, 2018
In part 2 of this series, Christophe looks at the very Swedish phenomenon of Kanban going “man-cold”! As teams implement their early Kanban boards, they inevitably face the reality of the gap between what they are actually used to doing vs. what they put on their Kanban board. (We have posted about this phenomenon earlier as well!) Here, Christophe explains why this happens – and what to do about it quickly so as to not fall into the Policy Debt-trap!
March 12, 2018
Is this you? That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past?
October 18, 2017
We are excited to announce the release of SwiftEASe in the recently concluded SAFe® Summit in Texas, held from 2 - 6 October 2017. With this Digité launches a new, tightly integrated tool for planning and managing the entire software delivery process based on the SAFe® framework.
August 20, 2017
Solving the Insulation Challenge of Managed Transformation
June 26, 2017
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, I haven’t seen much thought going into where to put those WIP limits. Hence, this blog!
March 22, 2017
The last couple of updates of SwiftKanban have focused on some key features such as Cycle Time Threshold, revamped ESP Analytics and an enhanced To-Do Board.
February 20, 2017
Cycle time (or System Lead Time as some call it) is one of the most common metrics used to measure the effectiveness of a Kanban system. Cycle time is the time taken by a Kanban card to move from start to end on the board (or some part thereof). As you start using a Kanban system and implementing its principles, ideally the cycle time of the system should reduce. In David Anderson’s initial blogs “http://www.djaa.com/why-kanban-why-focus-lead-time-reduction” he has clearly emphasized the importance of reducing the lead or cycle time of a Kanban system. Besides the obvious advantage of “faster-time-to-market” or faster delivery of value to customer, lead time reduction usually mean reduction of wait times in the overall workflow as the Kanban system helps to highlight and reduce different types of waste, including time between handoffs, blocked time due to waiting on external (or internal) dependencies, etc.
