Intro to Project Management: Project Scope Management Scope Management Processes Plan Collect Requirements Define Create WBS Validate Control

What This Is

Scope Management is the process of defining and controlling what work is included in a project. It's crucial for successful project delivery because it ensures everyone involved in the project is working on the right tasks, and that the project meets the stakeholders' expectations. For example, when building a new highway, the scope management process would involve defining the exact route, the number of lanes, and the features such as interchanges and rest stops.

Key Terms & Formulas

• Scope Statement: A document that outlines the project scope, including the work to be done, the deliverables, and the exclusions.
• Scope Creep: The uncontrolled expansion of project scope, which can lead to cost and time overruns.
• WBS (Work Breakdown Structure): A hierarchical decomposition of the project scope into smaller, manageable tasks.
• Scope Verification: The process of ensuring that the project scope is accurately defined and that all stakeholders agree on it.
• Scope Change Control: The process of managing changes to the project scope, including assessing the impact of changes and approving or rejecting them.
• Earned Value (EV): The value of work completed, calculated as EV = % complete × BAC (Budget at Completion).
• Cost Performance Index (CPI): A measure of how well the project is performing in terms of cost, calculated as CPI = EV / AC (Actual Cost).
• Schedule Performance Index (SPI): A measure of how well the project is performing in terms of schedule, calculated as SPI = EV / PV (Planned Value).
• Scope Baseline: The approved scope statement, WBS, and budget at a specific point in time.
• Scope Change Request (SCR): A formal request to change the project scope, which must be assessed and approved or rejected.

Step-by-Step / Process Flow

1. Collect Requirements: Identify and document the project requirements through stakeholder interviews, surveys, and workshops.
2. Define Scope: Develop a scope statement that outlines the project scope, including the work to be done, the deliverables, and the exclusions.
3. Create WBS: Decompose the project scope into smaller, manageable tasks using a hierarchical structure.
4. Validate Scope: Ensure that the project scope is accurately defined and that all stakeholders agree on it.
5. Control Scope: Manage changes to the project scope, including assessing the impact of changes and approving or rejecting them.

Common Mistakes

• Mistake: Failing to define the project scope clearly and concisely.
• Correction: Develop a scope statement that outlines the project scope, including the work to be done, the deliverables, and the exclusions.
• Mistake: Not involving stakeholders in the scope definition process.
• Correction: Conduct stakeholder interviews, surveys, and workshops to ensure that all stakeholders are aware of and agree on the project scope.
• Mistake: Not monitoring and controlling scope changes.
• Correction: Establish a scope change control process to assess and approve or reject changes to the project scope.

Exam Tips

• Tip: Be able to distinguish between scope creep and scope change control.
• Tip: Understand the difference between a scope statement and a scope baseline.
• Tip: Be able to calculate earned value, cost performance index, and schedule performance index.

Quick Practice Questions

1. If the CPI is 0.8, is the project under or over budget? Answer: Under budget. Explanation: A CPI of 0.8 indicates that the project is performing better than expected in terms of cost.
2. If the EV is $100,000 and the BAC is $200,000, what is the % complete? Answer: 50%. Explanation: EV = % complete × BAC, so % complete = EV / BAC = $100,000 / $200,000 = 0.5 or 50%.
3. If the SPI is 1.2, is the project ahead or behind schedule? Answer: Ahead of schedule. Explanation: A SPI of 1.2 indicates that the project is performing better than expected in terms of schedule.

Last-Minute Cram Sheet

• Scope Statement: A document that outlines the project scope, including the work to be done, the deliverables, and the exclusions.
• Scope Creep: The uncontrolled expansion of project scope, which can lead to cost and time overruns.
• WBS (Work Breakdown Structure): A hierarchical decomposition of the project scope into smaller, manageable tasks.
• Scope Verification: The process of ensuring that the project scope is accurately defined and that all stakeholders agree on it.
• Scope Change Control: The process of managing changes to the project scope, including assessing the impact of changes and approving or rejecting them.
• Earned Value (EV): EV = % complete × BAC (Budget at Completion).
• Cost Performance Index (CPI): CPI = EV / AC (Actual Cost).
• Schedule Performance Index (SPI): SPI = EV / PV (Planned Value).
• Scope Baseline: The approved scope statement, WBS, and budget at a specific point in time.
• Scope Change Request (SCR): A formal request to change the project scope, which must be assessed and approved or rejected.
• ⚠️ Decomposition breaks down work, not activities – it creates the WBS, not the activity list.
• ⚠️ Scope creep can lead to cost and time overruns.
• ⚠️ Earned value is a measure of the value of work completed.