According to the Agile Practice Guide and the PMBOK Guide, the choice of an adaptive lifecycle depends on the nature of the work. Support and maintenance environments are characterized by high variability and the need for a " pull-based " system.
Why Choice C is correct: Kanban is the ideal method for " continuous flow " work where tasks cannot be planned in time-boxed iterations (like Scrum Sprints).
Work in Progress (WIP) Limits: The scenario states the team cannot start new issues until they finish existing ones. This is the core principle of WIP limits in Kanban. By limiting how much work can be " In Progress, " the team prevents bottlenecks and ensures they focus on completing tasks before taking on new ones.
On-Demand Planning: Since support issues are unpredictable, Kanban allows the team to pull the next highest- priority item from the backlog as soon as capacity becomes available, rather than waiting for a new sprint cycle.
Analysis of other options:
A (SAFe): The Scaled Agile Framework (SAFe) is designed for large-scale, multi-team development. The description provided in the option ( " it does not allow for scaling " ) is factually incorrect, as SAFe is specifically built for scaling.
B (Extreme Programming - XP): XP is a software development methodology focused on technical excellence (e.g., pair programming, test-driven development). While it emphasizes quality, it does not fundamentally dictate the flow of work for unpredictable support issues as effectively as Kanban.
D (Scrum): Scrum relies on Sprints (time-boxes). If a team cannot plan their work even for a week, Scrum ' s
" Sprint Planning " becomes impossible. Furthermore, the statement that Scrum allows for " completing the whole architecture up front " is incorrect; that describes a Waterfall/Predictive approach, whereas Scrum is iterative.
In a production support environment, the Lead Time and Cycle Time metrics used in Kanban provide the visibility needed to manage a reactive workload without the overhead of rigid sprint structures.