What are the key change order scope metrics that you track and report on your projects?

1 Scope Baseline

The scope baseline is the original approved scope of your project, including the project deliverables, requirements, and work breakdown structure (WBS). It serves as a reference point for measuring and controlling any changes that occur during the project execution. You should track and report the scope baseline as part of your change order management process, and update it whenever a change order is approved. This way, you can compare the current scope with the original scope, and identify any deviations or variances that need to be addressed.

2 Scope Change Requests

Scope change requests are formal documents that describe the proposed changes to the project scope, and the reasons, benefits, and impacts of those changes. They are usually initiated by the project stakeholders, such as the client, the contractor, the subcontractors, or the suppliers. You should track and report the number, status, and source of scope change requests as part of your change order management process, and evaluate them according to your change control procedures. This way, you can prioritize and approve the changes that are necessary, feasible, and beneficial for your project, and reject or defer the ones that are not.

3 Scope Change Orders

Scope change orders are formal documents that authorize the approved changes to the project scope, and specify the revised scope, schedule, budget, quality, and risk parameters. They are usually issued by the project manager, after obtaining the approval of the project sponsor and the affected parties. You should track and report the number, value, and impact of scope change orders as part of your change order management process, and implement them according to your change management plan. This way, you can adjust your project plan, resources, and deliverables to accommodate the changes, and communicate them to your project team and stakeholders.

4 Scope Variance

Scope variance is the difference between the planned scope and the actual scope of your project, measured at a given point in time. It can be positive or negative, depending on whether the actual scope is more or less than the planned scope. You should track and report the scope variance as part of your change order management process, and analyze its causes and consequences. This way, you can identify and correct any errors, omissions, or misunderstandings in your scope definition, and prevent or mitigate any scope creep or gold plating that may affect your project performance.

5 Scope Performance Index

Scope performance index (SPI) is a ratio that compares the earned value (EV) and the planned value (PV) of your project scope, calculated as SPI = EV / PV. It indicates how efficiently you are completing your project scope, relative to your plan. You should track and report the SPI as part of your change order management process, and use it as a tool for forecasting and controlling your project scope. This way, you can assess your progress and performance, and take corrective actions if your SPI is less than one, which means you are behind schedule or over budget.

6 Scope Quality Metrics

Scope quality metrics are quantitative or qualitative measures that evaluate the quality of your project scope, in terms of its completeness, accuracy, clarity, consistency, and validity. They can include criteria such as the number of defects, errors, rework, or customer complaints related to your project scope. You should track and report the scope quality metrics as part of your change order management process, and use them as a basis for improving your scope management processes and practices. This way, you can ensure that your project scope meets the expectations and requirements of your project stakeholders, and delivers the desired value and benefits.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?