Close

2023-08-20

The Power of Visualizing Work: Implementing Kanban and Time-Boxed Approaches

The Power of Visualizing Work: Implementing Kanban and Time-Boxed Approaches

Kanban Systems and Time-boxed approaches are often discussed in software development, and there has been some debate about the relationship between these methods and the concept of iteration. Some people have referred to Kanban Systems as “Waterfall 2.0,” There have been suggestions that a Lean perspective might view iteration as rework and, therefore, as waste.

The description of iteration provides a valuable framework for understanding these concepts. Iteration is used to find or improve a single solution while incrementing is used to build additional solutions. This distinction highlights that both Kanban Systems and Time-boxed approaches can be used to manage the delivery of software solutions incrementally and iteratively.

Time-boxed approachA product backlog is typically defined based on pre-determined solutions.
User Stories are prioritized to build up the functionality for those solutions incrementally. This approach prioritizes work to generate knowledge and feedback, which helps to discover or refine solutions.
However, the relationship between Minimal Marketable Features (ROI Components) and User Stories may be implicit rather than explicit.
A Kanban System A Kanban System explicitly visualizes the work at both levels (MMFs and User Stories) and provides a clear picture of how solutions are delivered incrementally and iteratively.
The MMFs can be prioritized and limited as Work In Progress, and the User Stories can be prioritized, managed, and determined to iterate the MMFs.
The User Stories can eventually be collapsed together to deliver the MMF incrementally.

Kanban Systems and Time-boxed approaches can be used to manage the delivery of software solutions incrementally and iteratively. The main difference is that a Kanban System explicitly visualizes the relationship between MMFs and User Stories, while this relationship may be implicit in a Time-boxed approach. Regardless of the method used, the goal is continually prioritizing work to generate knowledge and feedback and refine solutions.