ezds.com : Kintana HP PPM Project Scope Change

HP PPM Project Scope Change

ZDS

PPM Overview

HP Project Management comes with out-of-the-box 'best practice request types and workflows that can be used as-is or copied and customized to match your business process.
The Project Scope Change Process workflow manages changes (usually additions!) to a project's scope through request, justification, impact analysis and approval or rejection.

ppm prj scope change request process workflow

Default workflow steps

1. Identify and Document Change Request. The initiator builds a case for the change and sets the change request level.

2. Evaluate CR Level. The scope change's impact is evaluated. Depending on the level, the scope change is routed to a different branch of the workflow, each of which includes steps to create or update an impact analysis of the scope change. This ensures that decisions regarding the scope change are well-founded.

3. Create/Update Impact Analysis. Once the impact analysis has been created and updated, the scope change is analyzed and a recommendation issued. Often this will be the selection of a specific option or a recommendation not to pursue.

4. Submit Recommendation. The scope change is either submitted for approval or escalated for additional analysis.

5. Approve Request. The scope change may be rejected, deferred, or accepted. Usually a change control board issues the final approval.

6. Close. The scope change is closed.

Customization

Customization typically involves adding or removing steps, and changing step names, notifications and security groups (the people who can act on each step).

Fields on the project control request types can be configured to be visible or editable