PM Earth
 

Project Management Process Requirements

16 January 2009

Take these three steps to define specific process requirements:

1.      Define project management life cycle key stakeholders for process groups. Different groups of processes are significant to different stakeholders. For example, as the PMO is likely to review all projects at the end of each life cycle phase, the PMO is a stakeholder for phase review processes. Similarly, the human resources department might be a stakeholder for all project human resource processes, and the purchasing department for all processes that involve vendors or suppliers. Identify stakeholders for process groups in the specific process requirements table of the Process Execution Plan.

2.      Define compliance requirements. Various groups of processes may be required to be compliant to specific regulations or standards. For example, financial processes may fall under GAAP (generally accepted accounting principles). Also, if the organization has any existing governance rules or process requirements that are either industry-specific or required within the organization, these should be listed, as well.

3.      Define other project manager requirements. If the PMO or any other internal organization has put forth requirements that should apply to a set of processes or a single process, they should be documented as well. These can be identified by reviewing the work notes of the PMO documents to date, paying particular attention to problem and issue identification, goal setting, and brainstorming sessions. It may also be appropriate to review key stakeholder interviews and meet with key stakeholders. When these requirements are added to the specific process requirements table, the documentation of process requirements is complete.


 
 


Copyright © Method123 Ltd 2000-2018