Intrenion

A Guide to the Project Management Body of Knowledge (PMBOK Guide) (Project Management Institute)

Table of Contents

Copy Doctrine

Source

A Guide to the Project Management Body of Knowledge (PMBOK Guide) (Project Management Institute)

Practice 1: Use the standard as the foundation for project management

Problem
Projects become inconsistent without shared guidance.

Action
Apply the standard as the common foundation for managing projects.

Outcome
Project practices become more consistent.

Chapter: The Standard for Project Management - Introduction - Purpose of The Standard for Project Management

Practice 2: Use standard project management terminology

Problem
Different meanings create misunderstandings.

Action
Use the standard definitions for key project management terms.

Outcome
Communication becomes more accurate.

Chapter: The Standard for Project Management - Introduction - Key Terms and Concepts

Practice 3: Apply the standard to its intended audience

Problem
Guidance loses value when applied without considering its users.

Action
Use the standard in ways that fit its intended audience.

Outcome
The guidance becomes easier to apply.

Chapter: The Standard for Project Management - Introduction - Audience for this Standard

Practice 4: Connect project work to value delivery

Problem
Projects can produce outputs without creating organizational value.

Action
Align project activities with the organization's value delivery system.

Outcome
Project results contribute more business value.

Chapter: The Standard for Project Management - A System for Value Delivery - Audience for this Standard

Practice 5: Prioritize work that creates value

Problem
Low-value activities waste project resources.

Action
Select and prioritize work based on the value it delivers.

Outcome
Project effort produces more meaningful outcomes.

Chapter: The Standard for Project Management - A System for Value Delivery - Creating Value - Value Delivery Components

Practice 6: Share information with the right people at the right time

Problem
Delayed information slows project decisions.

Action
Provide accurate project information to the people who need it.

Outcome
Decision-making becomes faster and better informed.

Chapter: The Standard for Project Management - A System for Value Delivery - Creating Value - Information Flow

Practice 7: Follow the organization's governance framework

Problem
Projects can drift away from organizational expectations.

Action
Apply the governance requirements that guide the project.

Outcome
The project remains aligned with organizational direction.

Chapter: The Standard for Project Management - A System for Value Delivery - Organizational Governance Systems

Practice 8: Provide continuous oversight and coordination

Problem
Project issues grow when oversight is weak.

Action
Monitor and coordinate project activities throughout execution.

Outcome
Problems are identified and addressed earlier.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Provide Oversight and Coordination

Practice 9: Communicate objectives and seek feedback

Problem
Teams lose focus when project goals are unclear.

Action
Explain project objectives and encourage regular feedback.

Outcome
Everyone stays aligned on project goals.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Present Objectives and Feedback

Practice 10: Remove barriers that slow the team

Problem
Obstacles reduce team productivity.

Action
Provide the support needed for the team to complete its work.

Outcome
Project work progresses more smoothly.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Facilitate and Support

Practice 11: Capture lessons while the work is being done

Problem
Useful experience is lost when it is not documented.

Action
Record practical insights throughout project execution.

Outcome
Future projects benefit from accumulated knowledge.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Perform Work and Contribute Insights

Practice 12: Use expert knowledge where it adds value

Problem
Complex work suffers without specialized expertise.

Action
Engage qualified experts for work that requires specialized skills.

Outcome
Project decisions and deliverables improve.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Apply Expertise

Practice 13: Base project decisions on business priorities

Problem
Projects can lose alignment with business goals.

Action
Use business priorities to guide project decisions.

Outcome
The project better supports the organizational strategy.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Provide Business Direction and Insight

Practice 14: Provide the resources needed for success

Problem
Projects cannot succeed without adequate support.

Action
Supply the people, resources, and direction the project requires.

Outcome
The team can execute effectively.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Provide Resources and Direction

Practice 15: Maintain governance throughout the project

Problem
Governance becomes ineffective when it is neglected.

Action
Review and maintain governance activities end-to-end.

Outcome
Project oversight remains effective.

Chapter: The Standard for Project Management - A System for Value Delivery - Functions Associated with Projects - Maintain Governance

Practice 16: Consider the organization's internal environment

Problem
Internal conditions influence project success.

Action
Evaluate organizational factors before making project decisions.

Outcome
Project plans fit the organization more effectively.

Chapter: The Standard for Project Management - A System for Value Delivery - The Project Environment - Internal Environment

Practice 17: Monitor external conditions that affect the project

Problem
External changes can disrupt project progress.

Action
Track external factors that may influence the project.

Outcome
The project adapts more effectively to change.

Chapter: The Standard for Project Management - A System for Value Delivery - The Project Environment - External Environment

Practice 18: Align project work with product management

Problem
Projects can become disconnected from product direction.

Action
Coordinate project decisions with product management priorities.

Outcome
Delivered results better support product goals.

Chapter: The Standard for Project Management - A System for Value Delivery - Product Management Considerations

Practice 19: Act as a responsible steward

Problem
Careless decisions reduce trust.

Action
Manage resources responsibly and treat people with respect.

Outcome
Trust in project leadership increases.

Chapter: The Standard for Project Management - Project Management Principles - Be a Diligent, Respectful, and Caring Steward

Practice 20: Build a collaborative team environment

Problem
Poor collaboration limits team performance.

Action
Create an environment that encourages teamwork and mutual support.

Outcome
The team works together more effectively.

Chapter: The Standard for Project Management - Project Management Principles - Create a Collaborative Project Team Environment

Practice 21: Build strong relationships with stakeholders

Problem
Stakeholder support declines when engagement is inconsistent.

Action
Communicate regularly and involve stakeholders throughout the project.

Outcome
Stakeholder commitment becomes stronger.

Chapter: The Standard for Project Management - Project Management Principles - Effectively Engage with Stakeholders

Practice 22: Make value the basis for project decisions

Problem
Projects waste effort when value is overlooked.

Action
Choose actions that maximize value for customers and the organization.

Outcome
Project benefits increase.

Chapter: The Standard for Project Management - Project Management Principles - Focus on Value

Practice 23: Consider the effects of every project decision

Problem
Changes in one area can create problems elsewhere.

Action
Evaluate how each decision affects the overall project system.

Outcome
Project decisions become more balanced.

Chapter: The Standard for Project Management - Project Management Principles - Recognize, Evaluate, and Respond to System Interactions

Practice 24: Demonstrate effective leadership every day

Problem
Teams lose confidence without consistent leadership.

Action
Model the behaviors you expect from the project team.

Outcome
The team works with greater confidence.

Chapter: The Standard for Project Management - Project Management Principles - Demonstrate Leadership Behaviors

Practice 25: Adapt project management to the situation

Problem
One approach does not fit every project.

Action
Tailor project management practices to the project's context.

Outcome
Project performance improves.

Chapter: The Standard for Project Management - Project Management Principles - Tailor Based on Context

Practice 26: Build quality into everyday work

Problem
Finding defects late increases cost and effort.

Action
Include quality activities throughout project processes and deliverables.

Outcome
Deliverables meet expectations more consistently.

Chapter: The Standard for Project Management - Project Management Principles - Build Quality into Processes and Deliverables

Practice 27: Break down complex situations before acting

Problem
Complex projects are difficult to manage.

Action
Analyze complex situations before selecting a response.

Outcome
Project decisions become more effective.

Chapter: The Standard for Project Management - Project Management Principles - Navigate Complexity

Practice 28: Prepare responses before risks occur

Problem
Unmanaged risks threaten project objectives.

Action
Identify risks early and implement planned responses.

Outcome
Project disruption is reduced.

Chapter: The Standard for Project Management - Project Management Principles - Optimize Risk Responses

Practice 29: Adapt quickly to changing conditions

Problem
Rigid plans become ineffective as conditions change.

Action
Revise project plans when new information becomes available.

Outcome
Project progress stays on track.

Chapter: The Standard for Project Management - Project Management Principles - Embrace Adaptability and Resiliency

Practice 30: Help people adopt change successfully

Problem
Projects fail when stakeholders do not embrace change.

Action
Guide stakeholders through the transition to the desired future state.

Outcome
Change is adopted more successfully.

Chapter: The Standard for Project Management - Project Management Principles - Enable Change to Achieve the Envisioned Future State

Practice 31: Learn how the guide is organized

Problem
Guidance is difficult to use without understanding its structure.

Action
Study the structure of the PMBOK® Guide before applying it.

Outcome
Relevant guidance is easier to find.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Introduction - Structure of the PMBOK® Guide

Practice 32: Use the guide together with the standard

Problem
Using only one source limits project guidance.

Action
Apply the PMBOK® Guide together with The Standard for Project Management.

Outcome
Project management becomes more complete.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Introduction - Relationship of the PMBOK® Guide and The Standard for Project Management

Practice 33: Keep project practices current

Problem
Outdated practices reduce project effectiveness.

Action
Review and adopt the changes introduced in the latest guide.

Outcome
Project management stays current.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Introduction - Changes to the PMBOK® Guide

Practice 34: Use additional PMI guidance when needed

Problem
Some project situations require more detailed guidance.

Action
Consult PMIstandards+ for practical implementation support.

Outcome
Project decisions become better informed.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Introduction - Relationship to PMIstandards+

Practice 35: Balance all performance domains

Problem
Focusing on one area weakens overall project performance.

Action
Manage all project performance domains together.

Outcome
Project performance becomes more balanced.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains

Practice 36: Understand stakeholder expectations continuously

Problem
Stakeholder expectations change during the project.

Action
Identify and manage stakeholder expectations throughout the project.

Outcome
Stakeholder satisfaction improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Stakeholder Performance Domain - Stakeholder Engagement

Practice 37: Integrate stakeholder engagement with project work

Problem
Stakeholder activities lose effectiveness when managed separately.

Action
Coordinate stakeholder engagement with related project activities.

Outcome
Project alignment improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Stakeholder Performance Domain - Interactions with Other Performance Domains

Practice 38: Evaluate stakeholder engagement regularly

Problem
Engagement efforts may not achieve their purpose.

Action
Review stakeholder engagement against project objectives.

Outcome
Stakeholder management improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Stakeholder Performance Domain - Checking Results

Practice 39: Lead and support the project team

Problem
Teams perform inconsistently without effective leadership.

Action
Provide clear direction and support throughout the project.

Outcome
Team performance improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Project Team Management and Leadership

Practice 40: Build a culture of trust and respect

Problem
Weak team culture reduces collaboration.

Action
Encourage trust, respect, and shared responsibility within the team.

Outcome
The team collaborates more effectively.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Project Team Culture

Practice 41: Develop the habits of a high-performing team

Problem
Teams underperform without effective ways of working.

Action
Establish shared behaviors that promote accountability and collaboration.

Outcome
Team performance improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - High-Performing Project Teams

Practice 42: Apply leadership skills consistently

Problem
Leadership is ineffective when it is inconsistent.

Action
Use leadership skills every day to guide and support the team.

Outcome
The team performs with greater confidence.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Leadership Skills

Practice 43: Adjust your leadership style to the situation

Problem
A single leadership style does not fit every team.

Action
Adapt your leadership approach to the team's needs and maturity.

Outcome
Leadership becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Tailoring Leadership Styles

Practice 44: Align team management with the rest of the project

Problem
Team activities can become disconnected from other project work.

Action
Coordinate team management with the other performance domains.

Outcome
Project execution becomes more integrated.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Interactions with Other Performance Domains

Practice 45: Review team performance regularly

Problem
Team weaknesses remain unnoticed without evaluation.

Action
Assess team performance against expected results.

Outcome
Continuous improvement becomes possible.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Team Performance Domain - Checking Results

Practice 46: Choose a development life cycle that fits the project

Problem
An unsuitable life cycle reduces project effectiveness.

Action
Select the development life cycle that matches the project's characteristics.

Outcome
Project execution becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Development, Cadence, and Life Cycle Relationship

Practice 47: Establish a delivery cadence that fits stakeholder needs

Problem
Poor delivery timing reduces project value.

Action
Set a delivery cadence that matches stakeholder expectations and project goals.

Outcome
Value is delivered more consistently.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Delivery Cadence

Practice 48: Select the right development approach

Problem
The wrong development approach creates unnecessary risk.

Action
Choose the development approach that best fits the project.

Outcome
Project work progresses more efficiently.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Development Approaches

Practice 49: Evaluate project conditions before selecting an approach

Problem
Choosing an approach without evaluation increases project risk.

Action
Assess project characteristics before selecting a development approach.

Outcome
The selected approach better supports project success.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Considerations for Selecting a Development Approach

Practice 50: Define the project life cycle and phases clearly

Problem
Unclear phases create confusion during execution.

Action
Document the project life cycle and the purpose of each phase.

Outcome
Project work becomes easier to coordinate.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Life Cycle and Phase Definitions

Practice 51: Keep the life cycle, development approach, and delivery cadence aligned

Problem
Misaligned delivery practices reduce project efficiency.

Action
Coordinate the life cycle, development approach, and delivery cadence.

Outcome
Project execution becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Aligning of Delivery Cadence, Development Approach, and Life Cycle

Practice 52: Consider how life cycle decisions affect the whole project

Problem
Life cycle choices influence many project activities.

Action
Evaluate life cycle decisions across all performance domains.

Outcome
Project decisions become more balanced.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Interactions with Other Performance Domains

Practice 53: Measure development outcomes against expectations

Problem
Development progress is difficult to judge without evidence.

Action
Compare development results with planned outcomes.

Outcome
Project performance becomes easier to evaluate.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Development Approach and Life Cycle Performance Domain - Measuring Outcomes

Practice 54: Build a planning approach before execution

Problem
Projects lose direction without structured planning.

Action
Develop a planning approach before project work begins.

Outcome
Execution becomes more organized.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Planning Overview

Practice 55: Account for the factors that influence planning

Problem
Ignoring planning variables leads to unrealistic plans.

Action
Evaluate the factors that affect project planning before finalizing the plan.

Outcome
Plans become more realistic.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Planning Variables

Practice 56: Organize the team to support the planned work

Problem
An unsuitable team structure reduces execution efficiency.

Action
Design the team structure to match the planned work.

Outcome
Responsibilities become clearer.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Project Team Composition and Structure

Practice 57: Plan project communication early

Problem
Unplanned communication creates misunderstandings.

Action
Define how project information will be shared before execution begins.

Outcome
Communication becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Communication

Practice 58: Plan physical resources before they are needed

Problem
Missing resources delay project work.

Action
Identify and schedule required physical resources in advance.

Outcome
Work continues with fewer interruptions.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Physical Resources

Practice 59: Plan procurement before project execution

Problem
Late procurement delays project delivery.

Action
Define procurement activities during project planning.

Outcome
Required goods and services are available on time.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Procurement

Practice 60: Define how project changes will be managed

Problem
Uncontrolled changes disrupt project progress.

Action
Establish a clear approach for managing project changes during planning.

Outcome
Changes are handled with greater control.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Changes

Practice 61: Define metrics that support project objectives

Problem
Projects cannot be evaluated without meaningful measures.

Action
Select metrics that reflect the project's objectives and expected outcomes.

Outcome
Project performance becomes easier to assess.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Metrics

Practice 62: Keep planning aligned with project objectives

Problem
Misaligned plans create conflicting priorities.

Action
Review planning decisions to ensure they support the project's objectives.

Outcome
Project efforts remain focused.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Alignment

Practice 63: Coordinate planning across all performance domains

Problem
Independent planning creates inconsistent execution.

Action
Align planning activities with the other performance domains.

Outcome
Project execution becomes more coordinated.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Interactions with Other Performance Domains

Practice 64: Review planning results regularly

Problem
Weak planning can remain unnoticed.

Action
Evaluate planning results against project expectations.

Outcome
Planning quality improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Planning Performance Domain - Checking Results

Practice 65: Execute work through disciplined project processes

Problem
Inconsistent execution leads to avoidable errors.

Action
Follow the defined project processes throughout the project.

Outcome
Execution becomes more predictable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Project Processes

Practice 66: Balance competing project constraints

Problem
Improving one constraint can weaken another.

Action
Evaluate tradeoffs before changing project priorities.

Outcome
Project decisions become more balanced.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Balancing Competing Constraints

Practice 67: Keep the team focused on priority work

Problem
Frequent distractions reduce productivity.

Action
Direct the team's attention to the highest priority work.

Outcome
Project progress becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Maintaining Project Team Focus

Practice 68: Communicate continuously during project execution

Problem
Poor communication delays project work.

Action
Share timely information with team members and stakeholders.

Outcome
Project coordination improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Project Communications and Engagement

Practice 69: Manage physical resources throughout execution

Problem
Poor resource management interrupts project work.

Action
Monitor and adjust the use of physical resources throughout the project.

Outcome
Resources remain available when needed.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Managing Physical Resources

Practice 70: Manage procurement relationships actively

Problem
Weak supplier coordination delays project delivery.

Action
Work closely with procurement providers throughout the project.

Outcome
External support becomes more reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Working with Procurements

Practice 71: Evaluate new work before approving changes

Problem
Uncontrolled changes increase project risk.

Action
Review new work and proposed changes before approval.

Outcome
Project scope remains under control.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Monitoring New Work and Changes

Practice 72: Learn continuously throughout the project

Problem
Waiting until the end delays improvement.

Action
Capture and apply lessons throughout project execution.

Outcome
Project performance improves continuously.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Learning throughout the Project

Practice 73: Integrate project work across performance domains

Problem
Project activities become fragmented when managed separately.

Action
Coordinate project work with the other performance domains.

Outcome
Execution becomes more integrated.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Interactions with Other Performance Domains

Practice 74: Compare execution results with expectations

Problem
Execution issues remain hidden without review.

Action
Evaluate completed work against planned outcomes.

Outcome
Project performance improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Project Work Performance Domain - Checking Results

Practice 75: Deliver outcomes that create value

Problem
Completed work may fail to produce meaningful benefits.

Action
Prioritize deliveries that provide measurable value.

Outcome
Stakeholder satisfaction increases.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Delivery of Value

Practice 76: Verify deliverables before release

Problem
Incomplete deliverables reduce project success.

Action
Confirm that deliverables meet agreed requirements before delivery.

Outcome
Delivered results become more reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Deliverables

Practice 77: Build quality into every delivery

Problem
Defective outputs reduce project value.

Action
Verify the quality of deliverables before they are released.

Outcome
Delivered quality improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Quality

Practice 78: Correct weak outcomes promptly

Problem
Poor results reduce project success.

Action
Improve deliverables that fall short of expectations.

Outcome
Project outcomes become stronger.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Suboptimal Outcomes

Practice 79: Coordinate delivery with all project activities

Problem
Delivery decisions can conflict with other project work.

Action
Align delivery activities with the other performance domains.

Outcome
Project execution becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Interactions with Other Performance Domains

Practice 80: Confirm that deliveries achieve their intended value

Problem
Completed deliveries may not produce the expected benefits.

Action
Review delivered results against the expected value.

Outcome
Future deliveries become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Delivery Performance Domain - Checking Results

Practice 81: Establish measures that support project decisions

Problem
Poor measures fail to guide project management.

Action
Define measures that reflect project objectives and support decision-making.

Outcome
Project performance becomes easier to manage.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Establishing Effective Measures

Practice 82: Measure what matters most

Problem
Tracking unnecessary data wastes effort.

Action
Measure the indicators that best reflect project success.

Outcome
Performance reporting becomes more useful.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - What to Measure

Practice 83: Present performance information clearly

Problem
Poorly presented information leads to weak decisions.

Action
Communicate project performance in a clear and understandable format.

Outcome
Stakeholders understand project status more quickly.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Presenting Information

Practice 84: Check measurement methods for weaknesses

Problem
Poor measurement practices create misleading conclusions.

Action
Review measurement methods for accuracy and relevance.

Outcome
Performance information becomes more reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Measurement Pitfalls

Practice 85: Find the root cause of performance problems

Problem
Performance issues continue when their causes remain unknown.

Action
Investigate the underlying cause before taking corrective action.

Outcome
Corrective actions become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Troubleshooting Performance

Practice 86: Improve performance through measurement

Problem
Projects miss opportunities for improvement without learning from results.

Action
Use measurement results to identify and implement improvements.

Outcome
Project capability increases over time.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Growing and Improving

Practice 87: Use measurement across all performance domains

Problem
Performance data loses value when used in isolation.

Action
Apply measurement results across the other performance domains.

Outcome
Project decisions become more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Interactions with Other Performance Domains

Practice 88: Verify that measurement supports project success

Problem
Measurement activities may not improve project outcomes.

Action
Review whether measurement practices achieve their intended purpose.

Outcome
Performance management becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Measurement Performance Domain - Checking Results

Practice 89: Plan for uncertainty from the start

Problem
Unexpected events can affect any project.

Action
Consider uncertainty when planning and managing the project.

Outcome
The project becomes more resilient.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - General Uncertainty

Practice 90: Resolve ambiguity before making decisions

Problem
Unclear information leads to poor decisions.

Action
Clarify uncertain information before taking action.

Outcome
Project decisions become more reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Ambiguity

Practice 91: Analyze complexity before responding

Problem
Complex situations create unexpected outcomes.

Action
Study complex conditions before selecting a response.

Outcome
Project responses become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Complexity

Practice 92: Adjust plans when conditions change

Problem
Rapid change can make existing plans ineffective.

Action
Update project activities when conditions change significantly.

Outcome
Project progress remains steady.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Volatility

Practice 93: Manage risks before they become issues

Problem
Unmanaged risks threaten project objectives.

Action
Identify, assess, and respond to project risks early.

Outcome
Potential disruption is reduced.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Risk

Practice 94: Integrate uncertainty management across the project

Problem
Uncertainty affects every area of project work.

Action
Coordinate uncertainty management with the other performance domains.

Outcome
Project management becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Interactions with Other Performance Domains

Practice 95: Review uncertainty responses regularly

Problem
Risk responses become less effective as projects evolve.

Action
Evaluate uncertainty management against expected results.

Outcome
Project resilience improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Project Performance Domains - Uncertainty Performance Domain - Checking Results

Practice 96: Tailor project management to the project

Problem
Standard practices do not fit every project.

Action
Adapt project management to the project's specific context.

Outcome
Project effectiveness increases.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring

Practice 97: Understand the project before tailoring

Problem
Poor tailoring begins with poor understanding.

Action
Assess project characteristics before adapting project management.

Outcome
Tailoring decisions becomes more appropriate.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Overview

Practice 98: Tailor practices only when they improve results

Problem
Using standard practices without adjustment can reduce effectiveness.

Action
Modify project practices when they better fit the project's needs.

Outcome
Project management becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Why Tailor

Practice 99: Identify what should be tailored

Problem
Not every project element benefits from customization.

Action
Determine which project elements require adaptation.

Outcome
Tailoring effort stays focused.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor

Practice 100: Choose the life cycle and development approach that fit the project

Problem
An unsuitable development approach limits project success.

Action
Select the life cycle and development approach that best match the project's characteristics.

Outcome
Project delivery becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor - Life Cycle and Development Approach Selection

Practice 101: Adapt project processes to fit the work

Problem
Standard processes may create unnecessary effort.

Action
Customize project processes to match the project's needs.

Outcome
Project work becomes more efficient.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor - Processes

Practice 102: Tailor stakeholder engagement to each situation

Problem
One engagement approach does not fit every stakeholder.

Action
Adjust stakeholder engagement methods to match stakeholder needs.

Outcome
Stakeholder participation improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor - Engagement

Practice 103: Select tools that fit the project

Problem
Unsuitable tools reduce project efficiency.

Action
Choose tools that support the project's objectives and constraints.

Outcome
Project work becomes easier to manage.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor - Tools

Practice 104: Adapt methods and artifacts to the project

Problem
Standard methods and documents can create unnecessary work.

Action
Customize methods and artifacts to support the project's needs.

Outcome
Project management becomes more practical.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - What to Tailor - Methods and Artifacts

Practice 105: Follow a structured tailoring process

Problem
Unplanned tailoring creates inconsistent project practices.

Action
Use a defined process when adapting project management.

Outcome
Tailoring decisions becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - The Tailoring Process

Practice 106: Select the initial development approach early

Problem
Late development decisions delay effective planning.

Action
Choose the initial development approach before detailed planning begins.

Outcome
Project direction becomes clearer.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - The Tailoring Process - Select Initial Development Approach

Practice 107: Align project practices with the organization

Problem
Projects lose support when they ignore organizational expectations.

Action
Tailor project management to fit organizational requirements.

Outcome
Organizational alignment improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - The Tailoring Process - Tailor for the Organization

Practice 108: Adapt project management to project conditions

Problem
Projects differ in size, complexity, and risk.

Action
Tailor project management to the project's characteristics.

Outcome
Project execution becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - The Tailoring Process - Tailor for the Project

Practice 109: Tailor each performance domain deliberately

Problem
Applying the same approach to every performance domain reduces effectiveness.

Action
Adjust each performance domain to match the project's needs.

Outcome
Project management becomes more balanced.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains

Practice 110: Customize stakeholder management practices

Problem
Stakeholder needs vary from project to project.

Action
Adapt stakeholder management to the project's environment.

Outcome
Stakeholder relationships improve.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Stakeholders

Practice 111: Adapt team practices to the team

Problem
Teams require different management approaches.

Action
Tailor team management practices to the people on the project.

Outcome
Team performance improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Project Team

Practice 112: Tailor the development approach and life cycle

Problem
A fixed life cycle does not suit every project.

Action
Adapt the development approach and life cycle to project needs.

Outcome
Project delivery becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Development Approach and Life Cycle

Practice 113: Scale planning for the project

Problem
Too much or too little planning reduces effectiveness.

Action
Adjust planning activities to match project complexity.

Outcome
Planning provides better support.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Planning

Practice 114: Tailor execution practices to project needs

Problem
Standard execution methods do not fit every project.

Action
Adapt project work practices to the project's conditions.

Outcome
Execution becomes more efficient.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Project Work

Practice 115: Tailor delivery to maximize value

Problem
Standard delivery practices may not produce the greatest value.

Action
Adjust delivery practices to support project objectives.

Outcome
Delivered value increases.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Delivery

Practice 116: Match uncertainty management to project conditions

Problem
Projects face different types of uncertainty.

Action
Adapt uncertainty management to the project's risks and environment.

Outcome
Project resilience improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Uncertainty

Practice 117: Tailor performance measurement

Problem
Standard metrics may not reflect project success.

Action
Select measurement practices that fit the project's objectives.

Outcome
Performance information becomes more useful.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Tailoring the Performance Domains - Measurement

Practice 118: Use diagnostics to identify improvements

Problem
Project weaknesses remain hidden without evaluation.

Action
Assess project performance with diagnostic techniques.

Outcome
Improvement opportunities become clear.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Diagnostics

Practice 119: Reassess tailoring decisions throughout the project

Problem
Project conditions change over time.

Action
Review and update tailoring decisions as the project evolves.

Outcome
Project practices remain appropriate.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Tailoring - Summary

Practice 120: Choose models, methods, and artifacts with purpose

Problem
Poor technique selection reduces project effectiveness.

Action
Select models, methods, and artifacts that fit the project's needs.

Outcome
Project management becomes more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts

Practice 121: Understand the available project management techniques

Problem
Poor technique selection leads to weaker project decisions.

Action
Review the available models, methods, and artifacts before choosing them.

Outcome
The selected techniques better support the project.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Overview

Practice 122: Choose models that fit the project situation

Problem
No single model works well in every situation.

Action
Select models that match the project's context and needs.

Outcome
Project decisions become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models

Practice 123: Adapt leadership to the team's readiness

Problem
A fixed leadership style reduces team effectiveness.

Action
Adjust your leadership style to the team's capability and needs.

Outcome
Team performance improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Situational Leadership Models

Practice 124: Use communication models to improve understanding

Problem
Poor communication creates misunderstandings.

Action
Apply structured communication models when sharing information.

Outcome
Messages become clearer.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Communication Models

Practice 125: Match motivation to individual needs

Problem
People are motivated by different factors.

Action
Apply motivational models that fit the team's needs.

Outcome
Team engagement increases.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Motivation Models

Practice 126: Guide change with a structured approach

Problem
Poorly managed change creates resistance.

Action
Use change models to plan and support organizational change.

Outcome
Change is adopted more successfully.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Change Models

Practice 127: Analyze complexity before making decisions

Problem
Complex situations produce unexpected outcomes.

Action
Use complexity models to understand project conditions.

Outcome
Responses become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Complexity Models

Practice 128: Support team development at every stage

Problem
Teams need different support as they mature.

Action
Adjust management practices to the team's stage of development.

Outcome
Team capability improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Project Team Development Models

Practice 129: Expand your approach with additional models

Problem
Common models cannot solve every project challenge.

Action
Use other models when they fit the situation better.

Outcome
Problem solving becomes more flexible.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Models - Other Models

Practice 130: Apply models across multiple performance domains

Problem
Models lose value when used in isolation.

Action
Use appropriate models across the project's performance domains.

Outcome
Project management becomes more consistent.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Models Applied Across Performance Domains

Practice 131: Select methods that fit the project

Problem
Poor method selection reduces project effectiveness.

Action
Choose methods that match the project's objectives and context.

Outcome
Project execution improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Methods

Practice 132: Base decisions on reliable data

Problem
Weak information leads to poor decisions.

Action
Gather and analyze relevant project data before making a decision.

Outcome
Decision quality improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Methods - Data Gathering and Analysis

Practice 133: Develop realistic estimates

Problem
Poor estimates create unrealistic expectations.

Action
Estimate project work using reliable information and appropriate techniques.

Outcome
Project plans become more accurate.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Methods - Estimating

Practice 134: Give every meeting a clear purpose

Problem
Unfocused meetings waste project time.

Action
Define a clear objective before each meeting.

Outcome
Meetings produce better results.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Methods - Meetings and Events

Practice 135: Use specialized methods when needed

Problem
General methods cannot solve every project challenge.

Action
Choose specialized methods that fit the specific situation.

Outcome
Project solutions become more effective.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Methods - Other Methods

Practice 136: Coordinate methods across the project

Problem
Independent methods create inconsistent practices.

Action
Apply compatible methods across multiple performance domains.

Outcome
Project execution becomes more integrated.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Methods Applied Across Performance Domains

Practice 137: Create only artifacts that add value

Problem
Unnecessary documentation increases project effort.

Action
Use artifacts that directly support project management and delivery.

Outcome
Documentation becomes more useful.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts

Practice 138: Document the project's strategic direction

Problem
Projects lose focus without clear strategic guidance.

Action
Create strategy artifacts that explain project direction.

Outcome
Project decisions remain aligned.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Strategy Artifacts

Practice 139: Keep project logs and registers current

Problem
Outdated records reduce project visibility.

Action
Maintain accurate logs and registers throughout the project.

Outcome
Project information remains reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Logs and Registers

Practice 140: Keep project plans up to date

Problem
Outdated plans no longer reflect project reality.

Action
Update project plans when significant changes occur.

Outcome
Project execution stays aligned.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Plans

Practice 141: Use hierarchy charts to organize project information

Problem
Complex project information is difficult to understand.

Action
Use hierarchy charts to show the relationships between project elements.

Outcome
Project structure becomes easier to understand.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Hierarchy Charts

Practice 142: Establish baselines before measuring performance

Problem
Progress cannot be measured without a reference point.

Action
Create baselines for the project's key performance measures.

Outcome
Performance comparisons become meaningful.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Baselines

Practice 143: Present project information visually

Problem
Large amounts of project data are difficult to interpret.

Action
Use clear visual displays to communicate important project information.

Outcome
Stakeholders understand project status more quickly.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Visual Data and Information

Practice 144: Report information that supports decisions

Problem
Poor reporting limits effective project oversight.

Action
Prepare reports that highlight the most important project information.

Outcome
Decision-making improves.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Reports

Practice 145: Define agreements and contracts clearly

Problem
Unclear agreements create misunderstandings.

Action
Document responsibilities, expectations, and obligations in agreements and contracts.

Outcome
Working relationships become more reliable.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Agreements and Contracts

Practice 146: Create additional artifacts only when they add value

Problem
Extra documentation increases unnecessary work.

Action
Use additional artifacts only when they support the project's objectives.

Outcome
Documentation remains efficient.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Commonly Used Artifacts - Other Artifacts

Practice 147: Apply artifacts consistently across performance domains

Problem
Disconnected artifacts create inconsistent project information.

Action
Use project artifacts consistently across all performance domains.

Outcome
Project management becomes more coordinated.

Chapter: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) - Models, Methods, and Artifacts - Artifacts Applied Across Performance Domains