Professional Documents
Culture Documents
3
PROJECT MANAGEMENT
Purpose Project
Plans Process Area Sampling of Work
describes the purpose of the process Products – graphic showing a
area sampling of work products in
Relevant Terminology relation to PA specific practices
definitions of important terms DAR SP 1.6 Process Area Sampling of
from the model glossary Select
Solutions PA Relationships – graphic
When a PA Is Not Done Well… showing a sampling of PA
discussion points for when a relationship to PA specific
PA is not done well practices
Managing the
PAs Project
REQM,
PP,PMC Organizing
Managing
and
RSKM the Work
SAM,IPM
Improvement
PAs Infrastructure
OPF
OPD Enabling
Improvement of
IPM the Work
OT
Requirement Management
Purpose
Manage requirements of the project’s products and product
components and to ensure alignment between those
requirements and the project’s plans and work products.
Requirements Traceability
A discernable association between requirements and
related requirements, implementations, and verifications.
Bidirectional Traceability
An association among two or more logical entities that
is discernable in either direction (i.e., to and from an
entity).
Manage Requirements
SG 1 Requirements are managed and inconsistencies
with project plans and work products are identified.
Manage Requirements
SP 1.1 Understand Requirements
SP 1.2 Obtain Commitment to Requirements
SP 1.3 Manage Requirements Changes
SG 1 SP 1.4 Maintain Bidirectional Traceability of
Requirements
SP 1.5 Ensure Alignment Between Project
Work and Requirements
Requirements Management
Manage
Requirements
SP 1.1 SP 1.2
Obtain
Understand Commitment
Requirements to
Requirements
Requirements Traceability
Matrix
RD SP 2.1
Establish
Product and
RD SP 3.3 SP 1.1 SP 1.2 SP 1.3 Product
Component
Obtain Manage Requirements
Analyze Understand Commitment Requirements
Requirements Requirements to Changes
Requirements CM SP 2.1
Track
SP 1.4 SP 1.5 Change
Ensure Requests
Maintain Alignment
Bidirectional Between Project
Traceability of Work and
Requirements Requirements
Manage Requirements
SP 1.1 Understand Requirements
SP 1.2 Obtain Commitment to Requirements
SG 1 SP 1.3 Manage Requirements Changes
Focus
Area SP 1.4 Maintain Bidirectional Traceability of
Requirements
SP 1.5 Ensure Alignment Between Project
Work and Requirements
Requirement Management
Purpose
Establish and maintain plans that define project activities.
Product
Planning
Project
A managed set of interrelated activities and resources, including
people, that delivers one or more products or services to a customer
or end user.
A project has an intended beginning (i.e., project startup) and end.
Projects typically operate according to a plan. Such a plan is
frequently documented and specifies what is to be delivered or
implemented, the resources and funds to be used, the work to be
done, and a schedule for doing the work. A project can be composed
of projects.
In some contexts, the term “program” is used to refer to a project.
Future projects cannot learn from completed projects because there are no
lessons learned.
Establish Estimates
SG 1 Estimates of project planning parameters are
established and maintained.
Establish Estimates
SP 1.1 Estimate the Scope of the Project
SP 1.2 Establish Estimates of Work Product and
SG 1 Task Attributes
SP 1.3 Define Project Lifecycle Phases
SP 1.4 Estimate Effort and Cost
Project Planning
Project Planning
• Identified Risks
Identify Project Risks • Risk Impacts and Probability of Occurrence
• Risk Priorities
Project Planning
1. Tools
2. Budget/funding
3. Staff
4. Project plans
5. Facilities
Requirement Management
Purpose
Provide understanding of the project’s progress so that
appropriate corrective actions can be taken when the
project’s performance deviates significantly from the plan.
Plan vs Actual
Monitor Commitments
• Records of Commitment Reviews
Monitor Stakeholder
• Records of Stakeholder Involvement
Involvement
Goals
Practices
Conduct Progress Reviews • Documented Project Review Results
Typical Work Products
Goals
Issues and
Project Plans Corrective
Actions
Requirement Management
Purpose
Identify potential problems before they occur so that risk
handling activities can be planned and invoked as needed
across the life of the product or project to mitigate adverse
impacts on achieving objectives.
Risks
Risks that are known to project staff are often not known to
management.
Mitigate Risks
SG 3 Risks are handled and mitigated as appropriate to
reduce adverse impacts on achieving objectives.
Mitigate Risks
SG 3 SP 3.1 Develop Risk Mitigation Plans
SP 3.2 Implement Risk Mitigation Plans
Risk Management
Determine Risk Sources and • Risk Source Lists (external and internal)
Categories • Risk Categories List
Establish a Risk
Management Strategy • Project Risk Management Strategy
Goals
Practices
Risk Management
Goals
Practices
Risk Management
Plans Risk
Repository
Requirement Management
Purpose
The purpose of Supplier Agreement Management (SAM) is
to manage the acquisition of products and services from
suppliers.
PA
S S
Supplier
An entity delivering products or performing services being acquired.
An individual, partnership, company, corporation, association, or
other entity having an agreement with an acquirer for the design,
development, manufacture, maintenance, modification, or supply of
items under the terms of an agreement.
Supplier agreement
A documented agreement between the acquirer and supplier.
The management and technical staff do not have insight into supplier
activities.
Supplier products are accepted even when they do not meet the
product requirements.
• Market studies
• List of Candidate Suppliers
Select Suppliers • Preferred Supplier List
• Rationale for Selection of Suppliers
• Solicitation materials and requirements
• Statements of Work
Establish Supplier • Contracts
Agreements • Memoranda of Agreement
• Licensing agreement
Goals
Practices
Typical Work Products
• Transition Plans
Goals Ensure Transition Products • Training Reports
• Support and Maintenance Reports
Practices
Requirement Management
Purpose
Establish and manage the project and the involvement of relevant
stakeholders according to an integrated and defined process that
is tailored from the organization’s set of standard processes.
Project B
Project C
Organizational
Organizational
Process Assets
Process Assets
Project A
Coordinate and
Use the
Collaborate
Project’s
With Relevant
Defined Process
Stakeholders
• Agendas and Schedules for Collaborative Activities
• Documented Issues (e.g., issues with customer requirements,
product and product-component requirements, product architecture,
Manage Stakeholder and product design)
Involvement • Recommendations for Resolving Relevant Stakeholder Issues
Practices
Resolve Coordination • Relevant Stakeholder Coordination Issues
Typical Work Products Issues • Status of Relevant Stakeholder Coordination Issues
PMC SP 1.2
Monitor
Commitments
Projects (IPM)
Requirement Management