Innovation by integration of Drum-Buffer-Rope (DBR) method with Scrum-Kanban and use of Monte Carlo simulation for maximizing throughput in agile project management

Abstract

Highly volatile, uncertain, complex and ambiguous environments (VUCA) complicate and condition project management. With the emergence of agile project management, it is proposed to co-construct it with the client's active participation. Two used agile methodologies are Scrum and Kanban. Scrum is based on executing fast, interactive cycles (Sprints) for the incremental construction of products. Kanban promotes the balance of the continuous workflow through synchronizing tasks and seeking perfection. The combined use of Scrum-Kanban facilitates the integration of the best of both approaches. The Theory of Constraints (TOC) proposes a method for managing constraints in a system (Constraint Management). The Drum-Buffer-Rope (DBR) method and Buffer Management are practical applications of this theory. This study seeks to maximize the continuous flow of value (Throughput) in agile project management by synergistically integrating the DBR method with Scrum-Kanban. The five-step process is implemented for the planning, executing, and controlling the Kanban board in a Scrum Sprint cycle. Four scenarios are evaluated: (1) Balanced Line; (2) Unbalanced Line; (3) Unbalanced Line Modification 1 - Stable, Robust and Fast; and (4) Unbalanced Line Modification 2 - Focusing and Elevation. Measurement of completed work (Kanban cards in the "Done" column) and final inventory for the Sprint cycle reveals that Simulation 4 is the optimal scenario, achieving the highest average "output" ("Done" cards) with reduced inventory ("Doing" cards). The integration of DBR with Scrum-Kanban maximizes the completed work (Throughput) and minimizes the final inventory of the Sprint cycle, which is corroborated by the principle of Little's Law.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 24 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.