According to the Agile Practice Guide and the PMBOK® Guide, Agile methodologies are generally divided into two main categories: Iteration-based Agile (such as Scrum) and Flow-based Agile (such as Kanban).
Flow-Based Agile: Unlike Scrum, which uses fixed-length, timeboxed iterations (Sprints), Kanban focuses on the continuous flow of work. In a manufacturing or installation context, where tasks might have highly variable durations or depend on physical dependencies (like machine arrival), a flow-based approach is often more practical.
WIP Limits: Instead of timeboxing, Kanban manages the project by limiting Work in Progress (WIP). This ensures the team only takes on new tasks (like installing a specific machine component) when there is capacity, preventing bottlenecks in the factory setup.
Continuous Delivery: In this scenario, the project manager has explicitly decided against timeboxed iterations. Kanban is the most appropriate choice because it allows for the delivery of value as soon as a work item is completed, rather than waiting for the end of a predefined cycle.
Analysis of other options:
Option A: SAFe® (Scaled Agile Framework) is a framework for scaling Agile across large organizations. It is highly structured and typically utilizes PI Planning, which relies on synchronized timeboxed iterations across multiple teams.
Option C: Feature-driven development (FDD) is an iterative approach that, while focused on features, still typically utilizes timeboxes for its design and build cycles.
Option D: Scrum is the definition of a timeboxed iteration methodology. It relies entirely on Sprints (usually 1–4 weeks), which the project manager has specifically stated they do not want to use.
Per PMI standards, when a project requires an adaptive approach but fixed-duration timeboxes are not suitable or desired, Kanban is the recommended methodology to manage the continuous flow of work and optimize delivery efficiency.
