Which project management approach is suitable for fixed scope?

• A. Kanban only
• B. Agile/Scrum for evolving requirements
• C. Hybrid for fixed scope
• D. Waterfall/PMBOK for fixed scope

Answer: (D)

When the scope is fixed, the project benefits from a plan-driven, sequential approach with clear baselines and formal change control. Waterfall provides that structure: you move through defined phases—requirements, design, build, test, and deployment—in a logical order, and you basel ine the scope, schedule, and cost before work starts. Because the scope is locked, changes are typically controlled and documented, which keeps the plan stable and predictable.

PMBOK reinforces this by offering a disciplined framework for managing all aspects of the project—scope management with baselines, schedule and cost planning, quality, risk, and stakeholder engagement—along with a formal change-control process. Together, they create the governance and visibility needed to deliver on a fixed set of deliverables within the agreed time and budget.

Other approaches emphasize flexibility. Kanban and Agile/Scrum focus on flow and iterative development, adapting to evolving requirements and priorities, which conflicts with a truly fixed scope. A hybrid mix can work in some scenarios, but for a genuinely fixed-scope project, the straightforward, controlled path of Waterfall/PMBOK provides the most reliable alignment.