|
|
|
|
|
4.2.2P Manage Scope / Medium Projects
Define Scope (4.2.2P.P1)
|
|
Role |
Scope Definition (Medium Projects) |
|
1 |
Project Manager |
Collect requirements. The requirements provide further details regarding the nature of the deliverables. See 2.1.3.1P Collect Requirements for more information. |
|
2 |
Project Manager |
Verify scope. The scope must be verified (approved). This includes approval of the Project Charter and the business requirements. See 4.2.3.1P Verify Scope for more details. |
Control Scope (4.2.2P.P2)
Medium projects usually encounter scope change requests.
|
|
Role |
Scope Change Management (Medium Projects) |
|
1 |
Project Manager |
Identify scope change request Solicit potential scope changes from any project stakeholders, including the project team, clients, sponsors, etc. Potential scope changes should be documented in writing to the project manager through a short Scope Change Request Form (optional) or email. |
|
2 |
Project Manager |
Validate it is a scope change The project manager validates that the request is, in fact, a scope change. |
|
3 |
Project Manager |
Enter the request in the Scope Change Log Enter the item into the Scope Change Log for tracking purposes. |
|
4 |
(Person making request) |
Request the business value of the change The person making the scope change request should define the business value to the project. The sponsor will need this information to make a final decision. |
|
5 |
Project Manager, Team Member |
Assign the scope change to a project team member for investigation The project manager assigns the request to a team member for investigation of the impact to the project. If the project manager understands the request and the implications he could assign it to himself. |
|
6 |
Project Manager, Client Manager |
(Optional) Resolve small change requests if there is no impact on schedule and budget If the impact on project cost, effort and duration falls below a threshold (say less than 20 hours) and the project will still be completed within the agreed upon cost and duration, the project manager and client manager may approve the scope change request. This threshold needs to be identified and approved in advance by the project sponsor. The purpose of this step is to keep from sending many small changes to the sponsor for approval. However, the sponsor must have agreed to delegate this responsibility – usually up to a certain threshold of dollars or effort. |
|
7 |
Sponsor |
Take the information to the sponsor Take the scope change request, alternatives, business value and project impact to the project sponsor for a resolution (if the project manager and client manager did not approve, as above). |
|
8 |
Project Manager |
Document the resolution on the Scope Change Log The sponsor should approve or deny the request. Document the resolution in the Scope Change Log. |
|
9 |
Project Manager |
Add the incremental work (if any) to the schedule If the scope change request is approved, the appropriate activities are added to the schedule to ensure the change is implemented. The project budget and deadline should also be updated, if necessary. |
|
10 |
Project Manager |
Add incremental cost (if any) to the budget If the scope change request is approved, the incremental cost needs to be added to your project budget. |
|
11 |
Project Manager |
Update the Abbreviated Project Charter, if necessary The current Abbreviated Project Charter should be updated if an approved scope change results in a substantial change to the scope of the project. |
|
12 |
Project Manager |
Communicate through your Status Reports Communicate scope change status and resolution to project team members and other appropriate stakeholders through the methods established in the Communications Plan, including the project Status Report. |



