Which phase is primarily responsible for scoping, requirements gathering, and obtaining authorization?

Which phase is primarily responsible for scoping, requirements gathering, and obtaining authorization?

• A. Execution phase
• B. Closure phase
• C. Planning phase
• D. Deployment phase

Answer: (C)

Defining what will be done, agreeing on what counts as finished, and securing formal approval to proceed all belong to planning. In this phase you set the project’s scope, which defines boundaries and objectives to prevent drift later on. You also gather requirements from stakeholders to understand what the solution must deliver and how success will be measured. Finally, obtaining authorization happens here through sign‑offs, budgets, and governance approvals that authorize moving from proposal to actual work. The other phases focus on different work: execution is where the plan is carried out and deliverables are produced, closure wraps up the project and evaluates outcomes, and deployment/implementation occurs when the solution is released to users.

Defining what will be done, agreeing on what counts as finished, and securing formal approval to proceed all belong to planning. In this phase you set the project’s scope, which defines boundaries and objectives to prevent drift later on. You also gather requirements from stakeholders to understand what the solution must deliver and how success will be measured. Finally, obtaining authorization happens here through sign‑offs, budgets, and governance approvals that authorize moving from proposal to actual work.

The other phases focus on different work: execution is where the plan is carried out and deliverables are produced, closure wraps up the project and evaluates outcomes, and deployment/implementation occurs when the solution is released to users.