Home
GitHub
The Standard for Project Management and PMBOK® Guide
The PMBOK® Guide - Seventh Edition represents a significant evolution in project management guidance, shifting from a process-based to a principles-based approach. This comprehensive guide combines The Standard for Project Management with practical guidance to help project professionals deliver value and navigate today's complex project environments.
Tailoring: Adapting to Project Context
Tailoring is the deliberate adaptation of approach, governance, and processes to make them more suitable for the given environment and the work at hand. Project teams tailor the appropriate framework to enable flexibility while consistently producing positive outcomes within the project's life cycle.
Each Project is Unique
Even when deliverables seem similar, project contexts differ as organizations, customers, and environments are dynamic elements.
Success Through Adaptation
Project success is based on adapting to the unique context of the project to determine the most appropriate methods of producing desired outcomes.
Continuous Process
Tailoring is iterative and therefore a continuous process throughout the project as conditions and requirements evolve.
Why Tailor Your Project Approach?
Adapting to the unique objectives, stakeholders, and complexity of the environment contributes to project success. Tailoring aims to maximize value, manage constraints, and improve performance by using "just enough" processes, methods, templates, and artifacts.
Identify Project Context
Examine the unique set of conditions for each project to determine the most appropriate methods for producing desired outcomes.
Adapt Methodology
Modify existing methodologies or create new approaches that suit the specific project needs while staying within organizational boundaries.
Communicate Decisions
Share tailoring decisions with stakeholders so everyone understands the chosen methods and processes relevant to their roles.
Evaluate and Refine
Collect feedback from stakeholders on how the tailored methods are working and adjust as needed throughout the project lifecycle.
Benefits of Tailored Project Approaches
A tailored project approach can produce direct and indirect benefits to organizations, increasing the probability of success and enhancing overall project performance.
Deeper Team Commitment
Project team members develop stronger commitment when they participate in defining the approach, leading to greater ownership of outcomes.
Reduced Waste
Tailoring eliminates unnecessary actions or resources, focusing only on what adds value to the project and its stakeholders.
Customer-Oriented Focus
The needs of customers and stakeholders become central influencing factors in tailoring the project, increasing satisfaction with outcomes.
Efficient Resource Use
Project teams become more conscious of the weight of project processes, leading to more efficient allocation and use of available resources.
What to Tailor in Your Project
Project teams can tailor various aspects of their approach to best suit the project context and requirements. Understanding what elements can be adapted helps teams make informed decisions about their tailoring strategy.
Life Cycle & Development Approach
Select and adapt the overall project life cycle and development approach based on project characteristics and constraints.
Processes
Modify standard processes to fit the specific needs of the project while maintaining alignment with organizational requirements.
Engagement
Adjust stakeholder engagement approaches to match the communication needs and preferences of project participants.
Tools
Select appropriate tools that support the project's needs while considering team familiarity and organizational standards.
Methods & Artifacts
Choose and adapt methods and artifacts that provide the right level of documentation and support for the project work.
The Tailoring Process
Tailoring is a structured approach that helps project teams adapt their methods to the specific context of their project. Following a systematic process ensures that tailoring decisions are deliberate and well-considered.
Select Initial Development Approach
Choose a starting approach based on project characteristics, constraints, and organizational context. Consider whether predictive, hybrid, or adaptive approaches would be most appropriate.
Tailor for the Organization
Adapt the selected approach to align with organizational culture, governance structures, and existing methodologies. Consider organizational factors that may influence how the project is executed.
Tailor for the Project
Further refine the approach based on specific project factors such as team composition, stakeholder needs, complexity, and risk profile. Make adjustments as the project progresses and conditions change.
Selecting the Initial Development Approach
The first step in tailoring is to select an initial development approach that aligns with the project's characteristics. This provides a foundation that can be further refined as tailoring progresses.
Predictive Approach
Best suited for projects with:
  • Well-understood requirements
  • Low uncertainty
  • Stable technology
  • Experienced teams with domain expertise
  • Clear governance and compliance needs
Hybrid Approach
Appropriate for projects with:
  • Mixed clarity of requirements
  • Moderate uncertainty
  • Multiple components with different needs
  • Teams with varied experience levels
  • Balance of governance and flexibility
Adaptive Approach
Ideal for projects with:
  • Emergent requirements
  • High uncertainty
  • Innovative or evolving technology
  • Self-organizing teams
  • Emphasis on customer collaboration
Tailoring for the Organization
After selecting an initial approach, project teams must adapt it to fit within the organizational context. This ensures alignment with existing structures, processes, and culture.
Assess Organizational Culture
Evaluate the organization's values, norms, and working practices to understand how they might influence project execution.
2
Review Governance Structures
Identify organizational governance requirements, decision-making processes, and reporting expectations.
Understand Policies and Standards
Review existing organizational policies, methodologies, and standards that may constrain or guide tailoring decisions.
Engage with PMO and Leadership
Collaborate with the Project Management Office and organizational leadership to ensure tailoring decisions have necessary support.
Tailoring for the Project
The final step in the tailoring process is to refine the approach based on the specific characteristics and needs of the project itself. This ensures the approach is optimized for the unique project context.

Project characteristics
Size, complexity, importance, and novelty
Team factors
Size, location, experience, and capabilities
Risk considerations
Risk profile, constraints, and dependencies
Stakeholder needs
Expectations, engagement, and communication
Business constraints
Budget, schedule, and resource availability
Implementing Ongoing Improvement
Tailoring is not a one-time activity but an ongoing process of refinement throughout the project lifecycle. Continuous evaluation and adjustment help ensure the approach remains optimal as conditions change.
Evaluate Current Approach
Assess how well the current tailored approach is working for the project and team
Gather Feedback
Collect input from team members and stakeholders about what's working and what could be improved
Make Adjustments
Implement changes to processes, methods, and artifacts based on evaluation and feedback
Monitor Results
Observe the effects of the adjustments and their impact on project performance
Tailoring the Performance Domains
Each of the eight project performance domains can be tailored to suit the specific needs of the project. Understanding how to adapt each domain helps create a cohesive and effective project approach.

Stakeholders
Adapt engagement strategies based on stakeholder influence, interest, and communication preferences
Team
Tailor team structures, roles, and collaboration approaches to match project needs
Development Approach
Select and modify life cycle and development methods to suit project characteristics
Planning
Adjust planning detail and frequency based on project complexity and uncertainty
Project Work
Customize work processes and coordination methods to optimize efficiency
Tailoring the Remaining Performance Domains
Continuing from the previous section, the remaining performance domains also require tailoring to create a comprehensive project approach that addresses all aspects of project management.

Delivery
Adapt delivery methods, quality approaches, and value demonstration to meet stakeholder expectations
Uncertainty
Tailor risk management approaches based on project risk profile and organizational risk appetite
Measurement
Select appropriate metrics and reporting methods that provide meaningful insights for decision-making
Each performance domain requires specific consideration during tailoring to ensure it supports the overall project approach while addressing the unique aspects of that domain.
Tailoring the Stakeholder Performance Domain
The Stakeholder Performance Domain focuses on activities and functions associated with stakeholder engagement. Tailoring this domain ensures appropriate stakeholder identification, analysis, and engagement strategies.
Stakeholder Identification
Adjust the depth and frequency of stakeholder identification based on project complexity, organizational structure, and stakeholder landscape.
Analysis Methods
Select appropriate stakeholder analysis techniques based on project needs, ranging from simple interest/influence matrices to detailed power/impact assessments.
Engagement Strategies
Tailor communication approaches, frequency, and channels to match stakeholder preferences and project requirements.
Feedback Mechanisms
Implement appropriate feedback loops that allow for stakeholder input while maintaining project momentum and focus.
Tailoring the Team Performance Domain
The Team Performance Domain encompasses activities related to establishing, developing, and leading the project team. Tailoring this domain ensures the team structure and dynamics support project success.
Team Structure
Adapt team organization based on project size, complexity, and delivery approach. Consider hierarchical, matrix, or self-organizing structures as appropriate.
Skill Development
Tailor training and development approaches based on team capabilities, project requirements, and available resources.
Leadership Style
Adjust leadership approaches to match team composition, organizational culture, and project characteristics.
Collaboration Methods
Select appropriate collaboration tools and techniques based on team distribution, project complexity, and organizational preferences.
Tailoring the Development Approach and Life Cycle Performance Domain
This domain focuses on the approach used to develop the project deliverables and the overall project life cycle. Tailoring this domain is fundamental to creating an effective project approach.
Life Cycle Selection
Choose an appropriate life cycle based on:
  • Project complexity and uncertainty
  • Stakeholder requirements for visibility
  • Organizational constraints
  • Need for early delivery of value
Development Approach
Select and adapt development approaches:
  • Predictive (plan-driven)
  • Iterative (repeated cycles)
  • Incremental (progressive delivery)
  • Adaptive (agile methods)
  • Hybrid (combination of approaches)
Phase Definition
Define appropriate phases considering:
  • Decision points and gates
  • Deliverable validation needs
  • Resource allocation patterns
  • Stakeholder engagement points
Tailoring the Planning Performance Domain
The Planning Performance Domain involves activities related to developing and maintaining the plans that guide the project through execution and delivery. Tailoring planning approaches ensures appropriate detail and flexibility.
Planning Horizon
Adjust the planning horizon based on project uncertainty. Use shorter horizons with rolling wave planning for projects with high uncertainty, and longer horizons for more predictable projects.
Planning Detail
Tailor the level of detail in plans based on project complexity, team experience, and stakeholder requirements. Balance between too much and too little detail.
Planning Frequency
Determine appropriate planning cadence based on the development approach. Adaptive approaches require more frequent planning sessions than predictive approaches.
Plan Formats
Select appropriate planning formats and tools that match the project approach and team preferences, from detailed Gantt charts to simple backlogs or kanban boards.
Tailoring the Project Work Performance Domain
The Project Work Performance Domain focuses on establishing project processes, managing physical resources, and managing procurements. Tailoring this domain ensures efficient execution of project activities.
Tailor project work processes by selecting appropriate work management methods, defining communication protocols, establishing change management procedures, and determining resource management approaches that align with the project's needs and constraints.
Tailoring the Delivery Performance Domain
The Delivery Performance Domain encompasses activities related to delivering the project scope and quality to produce the intended business value. Tailoring this domain ensures appropriate focus on value delivery.
Quality Approach
Select appropriate quality methods based on project requirements, industry standards, and organizational expectations
Deliverable Validation
Tailor validation approaches to match deliverable complexity and stakeholder requirements
Value Demonstration
Adapt methods for demonstrating value based on stakeholder expectations and organizational metrics
Acceptance Process
Customize acceptance criteria and processes to align with project approach and stakeholder needs
Tailoring the Measurement Performance Domain
The Measurement Performance Domain involves activities related to evaluating project performance and taking appropriate actions to maintain acceptable performance. Tailoring this domain ensures meaningful metrics and effective reporting.
3-7
Key Metrics
Select a focused set of meaningful metrics rather than tracking everything possible
2
Reporting Levels
Tailor reporting detail based on audience needs and project complexity
1-4
Reporting Frequency
Adjust reporting cadence to match project pace and stakeholder requirements
5+
Visualization Methods
Choose appropriate data visualization techniques that communicate effectively
Tailoring the Uncertainty Performance Domain
The Uncertainty Performance Domain focuses on identifying and addressing risks, both threats and opportunities. Tailoring this domain ensures appropriate risk management based on project characteristics.
Tailor risk management approaches based on project complexity, uncertainty level, organizational risk appetite, and stakeholder requirements. Select appropriate risk identification methods, analysis techniques, response strategies, and monitoring approaches that provide the right level of risk management without creating unnecessary overhead.
Diagnostic Approaches for Tailoring
Diagnostic tools can help project teams identify appropriate tailoring options based on project characteristics. These approaches provide structured ways to assess project context and select suitable methods.
Complexity Assessment
Evaluate project complexity across multiple dimensions including technical, organizational, and environmental factors. Higher complexity typically requires more robust approaches to planning, risk management, and stakeholder engagement.
Uncertainty Profiling
Assess the level of uncertainty in requirements, technology, and constraints. Projects with higher uncertainty benefit from more adaptive approaches with frequent feedback loops and progressive elaboration.
Stakeholder Analysis
Analyze stakeholder characteristics, influence, and engagement needs. Projects with diverse or highly influential stakeholders may require more emphasis on communication and engagement strategies.
Organizational Context Evaluation
Examine organizational culture, governance structures, and process requirements. Tailoring must work within organizational constraints while optimizing for project success.
Common Situations and Tailoring Suggestions
Certain project situations frequently occur and benefit from specific tailoring approaches. Understanding these common scenarios can help project teams quickly identify appropriate tailoring strategies.
Models, Methods, and Artifacts Overview
Models, methods, and artifacts are tools that project teams use to accomplish project work. Understanding the range of available options helps teams select the most appropriate tools for their specific project context.
Models
Conceptual frameworks that help teams understand complex concepts or relationships. Examples include:
  • Situational leadership models
  • Communication models
  • Motivation models
  • Change models
  • Complexity models
  • Team development models
Methods
Procedures or techniques used to accomplish project work. Examples include:
  • Data gathering and analysis
  • Estimating techniques
  • Meeting and event formats
  • Prioritization approaches
  • Problem-solving techniques
  • Decision-making methods
Artifacts
Tangible items created or used during the project. Examples include:
  • Strategy documents
  • Logs and registers
  • Plans
  • Hierarchy charts
  • Baselines
  • Visual data representations
  • Reports
Commonly Used Models
Models provide conceptual frameworks that help project teams understand complex concepts or relationships. Selecting appropriate models helps teams navigate various aspects of project management.
Situational Leadership Models
Frameworks that help leaders adapt their leadership style based on team member development levels and task requirements. Examples include Hersey and Blanchard's Situational Leadership Model.
Communication Models
Frameworks that describe how information flows between parties. Examples include sender-receiver models, interactive models, and transactional models of communication.
Motivation Models
Frameworks that explain what drives human behavior and performance. Examples include Maslow's Hierarchy of Needs, Herzberg's Two-Factor Theory, and McClelland's Needs Theory.
Change Models
Frameworks that describe how change occurs and can be managed. Examples include Lewin's Change Management Model, Kotter's 8-Step Change Model, and the ADKAR Model.
More Commonly Used Models
Continuing from the previous section, these additional models help project teams understand and navigate other important aspects of project management.
Complexity Models
Frameworks that help teams understand and navigate project complexity. Examples include the Cynefin Framework, Stacey Matrix, and the Complexity Assessment Model.
Team Development Models
Frameworks that describe how teams form and evolve over time. Examples include Tuckman's Stages of Group Development (Forming, Storming, Norming, Performing) and the Drexler/Sibbet Team Performance Model.
Emotional Intelligence Models
Frameworks that describe the ability to recognize and manage emotions in oneself and others. Examples include Goleman's Emotional Intelligence Model and the EQ-i 2.0 Model.
Decision-Making Models
Frameworks that guide the process of making choices among alternatives. Examples include the Vroom-Yetton-Jago Decision Model and the Cynefin Framework for decision contexts.
Commonly Used Methods
Methods are procedures or techniques used to accomplish project work. Selecting appropriate methods helps teams efficiently complete project activities and achieve desired outcomes.
Data Gathering
Techniques for collecting information needed for project decisions. Examples include interviews, surveys, focus groups, observation, document analysis, and research.
Data Analysis
Techniques for examining and interpreting collected data. Examples include root cause analysis, SWOT analysis, cost-benefit analysis, trend analysis, and statistical methods.
Estimating
Techniques for forecasting project variables like time, cost, and resources. Examples include analogous estimating, parametric estimating, three-point estimating, and planning poker.
Meetings and Events
Structured approaches for team collaboration and communication. Examples include standups, retrospectives, planning sessions, reviews, and workshops.
Commonly Used Artifacts
Artifacts are tangible items created or used during the project. Selecting appropriate artifacts helps teams document, communicate, and track project information effectively.
Strategy Artifacts
Documents that define project direction and approach:
  • Business case
  • Project charter
  • Roadmap
  • Product vision statement
Logs and Registers
Records that track specific project information:
  • Risk register
  • Issue log
  • Decision log
  • Assumption log
  • Stakeholder register
Plans
Documents that describe how aspects of the project will be managed:
  • Project management plan
  • Schedule
  • Budget
  • Quality plan
  • Resource plan
More Commonly Used Artifacts
Continuing from the previous section, these additional artifacts help project teams document, visualize, and communicate project information effectively.
Hierarchy Charts
Visual representations of hierarchical structures:
  • Work breakdown structure (WBS)
  • Organizational breakdown structure
  • Resource breakdown structure
  • Risk breakdown structure
Baselines
Approved versions of project artifacts used for comparison:
  • Scope baseline
  • Schedule baseline
  • Cost baseline
  • Performance measurement baseline
Visual Data
Graphical representations of project information:
  • Dashboards
  • Burndown/burnup charts
  • Kanban boards
  • Information radiators
  • Flowcharts and diagrams
Applying Models, Methods, and Artifacts Across Performance Domains
Different performance domains may require different models, methods, and artifacts. Understanding which tools are most relevant to each domain helps teams select appropriate options for their specific project needs.
When selecting models, methods, and artifacts for each performance domain, consider the specific needs of the project, the characteristics of the domain, organizational requirements, and team preferences. The goal is to use "just enough" tools to effectively manage the project without creating unnecessary overhead.
Stakeholder Performance Domain
The Stakeholder Performance Domain focuses on activities and functions associated with stakeholders. This domain is critical for ensuring appropriate engagement with all parties who may impact or be impacted by the project.
Stakeholder Identification
The process of identifying individuals, groups, or organizations that may affect or be affected by project decisions, activities, or outcomes. This includes analyzing their interests, involvement, interdependencies, influence, and potential impact.
Stakeholder Engagement
The systematic approach to communicating and working with stakeholders to understand their needs, address issues, and foster appropriate involvement throughout the project lifecycle.
Stakeholder Analysis
The process of examining stakeholder characteristics, interests, and potential impact on the project to develop appropriate engagement strategies and prioritize efforts.
Communication Planning
Determining the information and communication needs of stakeholders, including methods, frequency, and level of detail required for effective engagement.
Team Performance Domain
The Team Performance Domain encompasses activities related to establishing, developing, and leading the project team. This domain focuses on creating a high-performing team environment that enables project success.

2

4

5

High-Performing Team
Collaborative, efficient, and effective
2
Team Development
Building skills, relationships, and cohesion
Leadership
Guiding, motivating, and empowering the team
4
Team Culture
Establishing norms, values, and behaviors
5
Team Structure
Organizing roles, responsibilities, and reporting
Development Approach and Life Cycle Performance Domain
This domain focuses on the approach used to develop project deliverables and the overall project life cycle. It addresses how work is organized and sequenced to deliver project outcomes effectively.
Development Approaches
Methods for creating project deliverables:
  • Predictive: Plan-driven approach with detailed upfront planning
  • Iterative: Repeated cycles of development and refinement
  • Incremental: Progressive delivery of components
  • Adaptive: Evolving requirements and solutions through collaboration
  • Hybrid: Combination of different approaches
Life Cycle Components
Elements that structure the project timeline:
  • Phases: Distinct periods with specific focus
  • Gates: Decision points between phases
  • Iterations: Time-boxed periods of work
  • Releases: Delivery of value to stakeholders
  • Handoffs: Transition points between teams
Selection Factors
Considerations for choosing an approach:
  • Project complexity and uncertainty
  • Team capabilities and distribution
  • Organizational culture and constraints
  • Stakeholder requirements
  • Regulatory environment
Planning Performance Domain
The Planning Performance Domain involves activities related to developing and maintaining the plans that guide the project through execution and delivery. Effective planning establishes a solid foundation for project success.
Define Objectives and Scope
Establish clear project goals, deliverables, and boundaries to guide planning efforts
Develop Work Breakdown
Decompose project work into manageable components for planning and execution
3
Create Schedule
Sequence activities, estimate durations, and develop timeline for project execution
Determine Budget
Estimate costs and establish financial framework for project execution
5
Plan Resources
Identify required resources and develop approach for acquisition and management
6
Integrate and Adapt
Coordinate all planning elements and adjust as needed throughout the project
Project Work Performance Domain
The Project Work Performance Domain focuses on establishing project processes, managing physical resources, and managing procurements. This domain addresses the day-to-day activities that move the project forward.
Process Management
Establishing, maintaining, and improving the processes used to accomplish project work efficiently and effectively. This includes defining workflows, establishing quality controls, and implementing continuous improvement.
Balancing Constraints
Managing the competing demands of scope, schedule, cost, quality, resources, and risk to deliver successful project outcomes. This requires ongoing assessment and adjustment as project conditions change.
Resource Management
Acquiring, allocating, and optimizing the use of physical resources needed for project execution. This includes equipment, materials, facilities, and infrastructure.
Procurement Management
Planning and executing the purchase of products, services, or results from external vendors. This includes contract management, vendor relationships, and performance monitoring.
Delivery Performance Domain
The Delivery Performance Domain encompasses activities related to delivering the project scope and quality to produce the intended business value. This domain focuses on ensuring that project outputs meet requirements and enable outcomes.
Define Value
Clearly articulate what constitutes value for the project and its stakeholders. This includes identifying key performance indicators, success criteria, and expected benefits.
Ensure Quality
Implement quality planning, assurance, and control activities to meet requirements and stakeholder expectations. This includes defining quality standards, conducting reviews, and addressing defects.
Deliver Incrementally
Where appropriate, deliver value in stages to enable early benefits realization, validate assumptions, and gather feedback for improvement. This supports adaptive approaches and risk reduction.
Validate Deliverables
Confirm that project outputs meet requirements and acceptance criteria. This includes testing, demonstrations, reviews, and formal acceptance procedures.
Measurement Performance Domain
The Measurement Performance Domain involves activities related to evaluating project performance and taking appropriate actions to maintain acceptable performance. This domain focuses on metrics, analysis, and improvement.
Effective measurement involves establishing meaningful metrics, collecting accurate data, analyzing performance trends, presenting information clearly, and taking appropriate actions based on results. The goal is to provide timely insights that support informed decision-making and continuous improvement.
Uncertainty Performance Domain
The Uncertainty Performance Domain focuses on identifying and addressing risks, both threats and opportunities. This domain helps project teams navigate ambiguity, complexity, and volatility to improve project outcomes.
Identify
Recognize potential risks that could impact project objectives
2
2
Analyze
Evaluate probability and impact to prioritize risks
Plan Responses
Develop strategies to address prioritized risks
4
4
Implement
Execute response plans when triggers occur
Monitor
Track identified risks and watch for new ones
Types of Uncertainty in Projects
Uncertainty in projects can take various forms, each requiring different approaches to identify, analyze, and address effectively. Understanding these different types helps project teams develop comprehensive uncertainty management strategies.
General Uncertainty
The lack of complete certainty about future events or outcomes. This is inherent in all projects and requires ongoing vigilance and adaptability.
Ambiguity
A state of being unclear or having multiple possible interpretations. This often occurs with requirements, objectives, or stakeholder expectations and requires clarification through communication.
Complexity
The result of many interconnected parts creating unpredictable interactions. This requires systems thinking, decomposition, and careful integration management.
Volatility
Rapid and unpredictable changes in the project environment. This requires enhanced monitoring, scenario planning, and flexible response strategies.
Risk Management in Projects
Risk management is a systematic process for identifying, analyzing, and responding to project risks. Effective risk management improves the likelihood of project success by maximizing opportunities and minimizing threats.
Risk Identification
Techniques for identifying risks:
  • Brainstorming
  • Checklists
  • Interviews
  • SWOT analysis
  • Root cause analysis
  • Assumption analysis
  • Document reviews
Risk Analysis
Methods for evaluating risks:
  • Probability and impact assessment
  • Probability-impact matrix
  • Sensitivity analysis
  • Expected monetary value
  • Decision tree analysis
  • Monte Carlo simulation
Risk Response Strategies
Approaches for addressing risks:
  • Threats: Avoid, transfer, mitigate, accept
  • Opportunities: Exploit, share, enhance, accept
  • Contingency planning
  • Fallback plans
Interactions Between Performance Domains
The eight project performance domains do not exist in isolation but interact with and influence each other. Understanding these interactions helps project teams manage projects as integrated systems rather than separate components.
1
1
Stakeholders
Influences all domains through requirements, expectations, and decision-making
2
2
Team
Enables all other domains through skills, collaboration, and execution
3
3
Development Approach
Shapes how all other domains are implemented and integrated
4
4
Planning
Provides structure and direction for all other domains
5
5
Project Work
Executes plans and produces deliverables that create value
6
6
Delivery
Realizes value from project outputs and enables outcomes
7
7
Measurement
Provides insights that inform decisions across all domains
8
8
Uncertainty
Affects all domains through risks, complexity, and ambiguity
Checking Results Across Performance Domains
Each performance domain includes methods for checking results to ensure the domain is functioning effectively. Regular assessment helps project teams identify improvement opportunities and make necessary adjustments.
Models, Methods, and Artifacts Applied Across Performance Domains
Different models, methods, and artifacts are applicable to different performance domains. Understanding which tools are most relevant to each domain helps teams select appropriate options for their specific project needs.
8
Performance Domains
Each domain requires specific tools tailored to its focus
50+
Models
Conceptual frameworks that help understand complex concepts
40+
Methods
Procedures and techniques for accomplishing project work
60+
Artifacts
Tangible items created or used during the project
The key to effective project management is selecting the right combination of models, methods, and artifacts for each performance domain based on the specific project context, rather than applying all possible tools regardless of need.
Relationship to PMIstandards+
The PMBOK® Guide is complemented by PMIstandards+, an interactive digital platform that incorporates current, emerging, and future practices, methods, artifacts, and other useful information for project management professionals.
Expanded Content
PMIstandards+ provides a richer and broader range of information and resources that can more quickly accommodate advances and changes in project management.
Practical Application
The platform explains how specific practices, methods, or artifacts apply to projects based on industry segments, project types, or other characteristics.
Continuous Evolution
Starting with the inputs, tools and techniques, and outputs from the PMBOK® Guide – Sixth Edition, PMIstandards+ continues to incorporate new resources.
Complementary Resource
Users of The Standard for Project Management and the PMBOK® Guide can find information in PMIstandards+ that supplements the information in the printed publication.
Evolution of the PMBOK® Guide
The PMBOK® Guide has evolved significantly since its inception in 1987, adapting to changes in the project management profession and incorporating new approaches and perspectives.
1
1996 Edition
Distinguished as "a guide to the body of knowledge" rather than the body of knowledge itself. Shifted to a process-based standard to show interactions among Knowledge Areas.
2
Third Edition (2004)
First edition to incorporate the "ANSI Standard" logo and formally designate The Standard for Project Management as separate from the Project Management Framework.
3
Sixth Edition (2017)
First edition with distinct separation between the ANSI standard and the guide. First time "agile" content was incorporated into the text, not just referenced in examples.
4
Seventh Edition (2021)
Shifted from a process-based to a principles-based standard. Introduced performance domains and focused on outcomes rather than deliverables.
Summary of Changes in the Seventh Edition
The Seventh Edition of the PMBOK® Guide represents a significant evolution from previous editions, with several key changes that reflect the changing nature of project management.
Principles-Based Approach
Shifted from a process-based standard to a principles-based approach that focuses on intended outcomes rather than prescriptive processes. This provides greater flexibility for different project types and approaches.
The 12 Project Management Principles provide foundational guidelines for strategy, decision making, and problem solving across all types of projects.
Systems View
Adopted a systems view of project management that emphasizes:
  • Value delivery as part of a larger system
  • Projects as enablers of outcomes that deliver value
  • Eight interconnected performance domains that work as a system
  • Focus on outcomes rather than just outputs
Digital Integration
Created PMIstandards+, an interactive digital platform that:
  • Complements the printed guide
  • Provides expanded and evolving content
  • Accommodates advances in project management
  • Offers practical application guidance