vspacer
 
vspacer
 

HP PPM Portfolio Project

 
rss xml



HP Portfolio 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 PFM - Proposal workflow covers the planning and execution of the project generally under the control of the project manager.
The PFM -Proposal workflow concludes by creating a PFM - Asset request on the PFM - Asset workflow.

ppm pfm project workflow

Default workflow steps

1. Assign Project Manager. At this step, a project manager should be assigned to the project to manage and coordinate the remaining tasks and deliverables.

2. Detailed Project Definition. During this step, the project manager works with the appropriate team members and stakeholders to build the detailed definition of the project. This might include revisions to the staffing profile, budget, and financial benefit entries for the project. A detailed work plan should be created at this step as well.

3. Business Readiness Sign-Off. At this step, the appropriate stakeholders and IT management are required to sign off on the detailed project definition created in the previous step.

4. Launch Project. If approved, the project is made active at this step.

5. Requirements. At this step, members of the project team define what must be designed and built.

6. Reset to Planning. If the project requirements were rejected, at this step the project and its associated staffing profile, budget, and financial benefit are reset to In Planning status.

7. Design. Once the project is approved, members of the project team design the final output. This step is complete when the project team is ready to begin implementing the end solution of the project.

8. Construct. This step indicates that the project is in implementation phase. This step is complete when the solution is ready for testing.

9. Test. This is the final system and integration testing phase. Rework is done here unless major changes must be made, in which case the process returns to implementation. Otherwise, when testing is done, the step is marked as completed (or approved).

10. Deploy. During this step, the project outputs are released to production.

11. Create Asset. Following deployment of the project, an asset is automatically generated and begins moving along the asset workflow as the project is closed. The asset is responsible for tracking ongoing maintenance and other activities against the end result of the project.

12. Complete Project. The project and its associated staffing profile, budget, and financial benefit are marked Complete.


Customization
*Your project phases will be different from the default process. The workflow can be changed, with due attention to passing the request through request statuses (see Request Statuses and Workflow Steps page 41 for details).
*Customization typically involves adding or removing steps, and changing step names, notifications and security groups (the people who can act on each step).
*Keep the Create Asset step - It supports HP Portfolio Management functionality.

   


Back to top | ZDS Home | This article updated February 28, 2010.