Contribute process related experiences to organizational process assets.
Refer to the Organizational Process Definition process area for more information about establishing organizational process assets, establishing the organization’s measurement repository, and establishing the
organization’s process asset library.
Refer to the Organizational Process Focus process area for more information about incorporating experiences into organizational process assets.
This specific practice addresses contributing information from processes in the project’s defined process to organizational process assets.
Example Work Products
1. Proposed improvements to organizational process assets
2. Actual process and product measures collected from the project
3. Documentation (e.g., exemplary process descriptions, plans, training
modules, checklists, lessons learned)
4. Process artifacts associated with tailoring and implementing the
Integrated Project Management (IPM) 170
Subpractices
1. Propose improvements to the organizational process assets.
2. Store process and product measures in the organization’s
measurement repository.
Refer to the Measurement and Analysis process area for more information about obtaining measurement data.
Refer to the Project Monitoring and Control process area for more information about monitoring project planning parameters.
Refer to the Project Planning process area for more information about planning data management.
These process and product measures typically include the following: Planning data
Replanning data
Examples of data recorded by the project include the following: Task descriptions
Assumptions Estimates Revised estimates
Definitions of recorded data and measures Measures
Context information that relates the measures to the activities performed and work products produced
Associated information needed to reconstruct the estimates, assess their reasonableness, and derive estimates for new work
3. Submit documentation for possible inclusion in the organization’s
process asset library.
Examples of documentation include the following: Exemplary process descriptions
Training modules Exemplary plans Checklists and templates Project repository shells Tool configurations
4. Document lessons learned from the project for inclusion in the
organization’s process asset library.
5. Provide process artifacts associated with tailoring and implementing
the organization’s set of standard processes in support of the organization’s process monitoring activities.
Refer to the Monitor the Implementation specific practice in the
Organizational Process Focus process area for more information about the organization’s activities to understand the extent of deployment of standard processes on new and existing projects.
SG 2 Coordinate and Collaborate with Relevant Stakeholders
Coordination and collaboration between the project and relevant stakeholders are conducted.
SP 2.1 Manage Stakeholder Involvement
Manage the involvement of relevant stakeholders in the project.
Stakeholder involvement is managed according to the project’s integrated plan and defined process.
Refer to the Project Planning process area for more information about planning stakeholder involvement and obtaining plan commitment.
Example Work Products
1. Agendas and schedules for collaborative activities
2. Recommendations for resolving relevant stakeholder issues
3. Documented issues (e.g., issues with stakeholder requirements,
product and product component requirements, product architecture, product design)
Subpractices
1. Coordinate with relevant stakeholders who should participate in project
activities.
The relevant stakeholders should already be identified in the project plan.
2. Ensure work products that are produced to satisfy commitments meet
the requirements of the recipients.
Refer to the Verification process area for more information about verifying selected work products.
The work products produced to satisfy commitments can be services. This task typically includes the following:
Reviewing, demonstrating, or testing, as appropriate, each work product produced by relevant stakeholders
Reviewing, demonstrating, or testing, as appropriate, each work product produced by the project for other projects with representatives of the projects receiving the work product
Resolving issues related to the acceptance of the work products
3. Develop recommendations and coordinate actions to resolve
Integrated Project Management (IPM) 172
SP 2.2 Manage Dependencies
Participate with relevant stakeholders to identify, negotiate, and track critical dependencies.
Example Work Products
1. Defects, issues, and action items resulting from reviews with relevant
stakeholders
2. Critical dependencies
3. Commitments to address critical dependencies
4. Status of critical dependencies
Subpractices
1. Conduct reviews with relevant stakeholders.
2. Identify each critical dependency.
3. Establish need dates and plan dates for each critical dependency
based on the project schedule.
4. Review and get agreement on commitments to address each critical
dependency with those who are responsible for providing or receiving the work product.
5. Document critical dependencies and commitments.
Documentation of commitments typically includes the following: Describing the commitment
Identifying who made the commitment
Identifying who is responsible for satisfying the commitment Specifying when the commitment will be satisfied
Specifying the criteria for determining if the commitment has been satisfied
6. Track the critical dependencies and commitments and take corrective
action as appropriate.
Refer to the Project Monitoring and Control process area for more information about monitoring commitments.
Tracking critical dependencies typically includes the following:
Evaluating the effects of late and early completion for impacts on future activities and milestones
Resolving actual and potential problems with responsible parties whenever possible Escalating to the appropriate party the actual and potential problems not resolvable by the responsible individual or group