Principle 7: Tailor Based on Context
PMBOK 7 Statement: "Tailor the project approach, development approach, and project management processes, governance, and methods based on the context of the project, its environment, and the team to achieve the desired outcomes."
Tailoring is one of the most significant conceptual shifts from PMBOK 6 to PMBOK 7. In PMBOK 6, tailoring was described as a single process within Process Group 1 (Initiating). In PMBOK 7, tailoring is elevated to a guiding principle — recognition that no two projects are identical and that applying a standard methodology without adaptation is a recipe for failure. This principle is the foundation of PMBOK 7's entire philosophy: context matters, and the project manager's judgment in adapting approaches is more important than rote compliance with any framework.
One-Size-Fits-None: Why Tailoring Matters
The central insight behind Principle 7 is that there is no universal project management methodology that works for every project. A multi-year infrastructure project with regulatory compliance requirements has fundamentally different needs from a six-week software prototype. A team of five co-located people operates differently from a distributed team of fifty across three continents. A government contract with fixed-price terms follows different governance than an internal innovation initiative with a flexible budget.
When project management processes are applied without tailoring, the result is waste. Waste takes many forms: excessive documentation that nobody reads, meetings that consume time without generating value, approval chains that delay decisions, artifacts that duplicate information, and governance that constrains rather than enables. PMBOK 7's emphasis on value (Principle 4) and quality (Principle 8) reinforces that tailoring is not optional — it is a direct contributor to project success.
Tailoring is not the same as deviating from standards. Tailoring is a deliberate, documented decision to adapt processes to fit the project context. Deviation is departing from agreed-upon standards without justification. A tailored approach is still governed — the tailoring decisions themselves should be reviewed, approved where appropriate, and revisited as the project evolves. PMI does not advocate for abandoning standards; it advocates for applying them with judgment.
The Tailoring Dimensions
PMBOK 7 identifies four primary dimensions along which tailoring should be considered. Each dimension represents a set of choices that the project manager makes, ideally in consultation with the team and stakeholders, to shape the project's approach.
1. Lifecycle and Development Approach
The first and most consequential tailoring decision is choosing the development approach: predictive (waterfall), adaptive (agile), or hybrid. This decision is driven by project characteristics such as:
- Degree of uncertainty — High uncertainty favors adaptive approaches that can incorporate learning; low uncertainty favors predictive approaches that optimize for efficiency.
- Complexity — High complexity may benefit from iterative cycles that reduce risk through incremental delivery.
- Stakeholder preferences — Some organizations or clients require fixed-scope contracts that demand predictive approaches.
- Regulatory requirements — Compliance-heavy industries (healthcare, aerospace, finance) may require documented phase gates and formal sign-offs.
- Team capability and experience — Teams new to agile may struggle with pure adaptive approaches without coaching and guardrails.
PMBOK 7 does not prescribe any single development approach. Instead, it provides a framework for making this decision contextually. The PMP exam tests your ability to recognize which approach fits a given scenario.
2. Processes
Once the development approach is chosen, the project manager tailors the specific processes used to plan, execute, monitor, control, and close the project. This includes decisions about:
- Planning cadence — Detailed upfront planning for predictive projects; just-in-time planning for agile projects; rolling-wave planning for hybrid projects.
- Change management — Formal change control boards for predictive projects; team-level backlog refinement for agile projects.
- Risk management — Periodic risk reviews with formal registers for predictive projects; continuous risk identification in daily standups for agile projects.
- Quality management — Separate quality audits for predictive projects; built-in quality practices (TDD, pair programming, peer reviews) for agile projects.
- Reporting and communication — Formal status reports and monthly steering committees for predictive projects; information radiators and daily standups for agile projects.
3. Methods and Tools
Methods are the specific techniques used to execute processes (e.g., earned value management, user story mapping, critical path analysis, rolling wave planning). Tools include software, templates, and physical artifacts. Tailoring at this level involves selecting the methods and tools that add value for the specific project. A small project does not need enterprise project management software. A simple project does not need earned value management. A co-located team does not need a complex virtual collaboration platform. The guiding question is always: Does this method or tool contribute to delivering value, or is it overhead?
4. Artifacts
Artifacts are the documents, deliverables, and outputs produced by project processes. PMBOK 7 takes a pragmatic view: produce only those artifacts that are necessary for the project's success. A project charter, stakeholder register, and risk register are nearly always valuable. A detailed lessons learned document at the end of a two-week sprint may be overkill — a brief retrospective discussion may be more appropriate. The tailoring principle asks: Which artifacts serve a real purpose for this project, at this stage, for this team and these stakeholders?
| Dimension | Predictive | Agile | Hybrid |
|---|---|---|---|
| Lifecycle | Sequential phases (Initiate, Plan, Execute, Close) | Iterative sprints or iterations (2–4 weeks) | Predictive for stable portions, agile for uncertain portions |
| Planning | Detailed upfront plan; formal baseline management | Just-in-time planning; backlog refinement | Rolling-wave planning; progressive elaboration |
| Change Control | Formal CCB; change requests and approval workflows | Product owner prioritizes backlog; no formal CCB | Formal for predictive components; flexible for agile components |
| Risk | Periodic risk reviews; formal risk register | Continuous risk identification; risks managed in backlog | Mixed: formal register for major risks, continuous for operational |
| Documentation | Comprehensive; formal sign-offs at each phase | Lightweight; working software over comprehensive docs | Appropriate to each component's governance needs |
Factors That Influence Tailoring Decisions
PMBOK 7 provides a structured set of factors that project managers should consider when making tailoring decisions. These factors fall into several categories:
Project-Specific Factors
- Size and complexity — Larger, more complex projects need more structured governance; smaller projects can be lighter.
- Criticality — Life-critical or mission-critical projects (medical devices, safety systems) require more rigorous processes.
- Duration — Longer projects need more attention to change management and stakeholder evolution; shorter projects can streamline.
- Stability of requirements — Stable requirements favor predictive; evolving requirements favor adaptive.
Organizational Factors
- Organizational culture — Hierarchical cultures may resist flat agile structures; collaborative cultures may chafe under rigid governance.
- Organizational structure — Functional, matrix, and projectized structures each impose different authority and communication patterns.
- Maturity of project management practices — Organizations with low PM maturity need simpler processes; mature organizations can handle sophistication.
- Resource availability — Constraints on budget, tools, or skilled personnel require pragmatic trade-offs.
External Factors
- Regulatory and legal requirements — Compliance is non-negotiable and may impose specific processes regardless of other considerations.
- Market conditions — Fast-moving markets may favor speed over documentation; stable markets may tolerate thoroughness.
- Geographic distribution — Distributed teams need more structured communication and collaboration processes.
The PMP exam tests tailoring through situational questions where you must determine the appropriate approach for a given context. For example: "You are managing a project in a highly regulated industry with a distributed team and stable requirements. What development approach should you use?" The correct answer would recognize that the regulatory environment and stable requirements favor a predictive approach, but the distributed team requires additional tailoring in communication and collaboration processes. Look for answer choices that adapt all four tailoring dimensions — lifecycle, processes, methods, and artifacts — to the specific context.
The Tailoring Process
PMBOK 7 does not treat tailoring as a one-time decision made during project initiation. It is an ongoing process throughout the project lifecycle:
- Select the initial approach — During project initiation, evaluate the factors above and choose the development approach and initial process set.
- Tailor processes and artifacts — Adapt the selected processes, methods, and artifacts to the specific project context. Document tailoring decisions and their rationale.
- Implement and monitor — Execute the tailored approach and continuously assess whether the tailoring is working. Are the processes generating value? Are artifacts being used? Is the team productive?
- Adapt as the project evolves — Project context changes. A new regulation may require more formal governance. A team maturity increase may allow lighter processes. A scope change may shift the development approach. Regularly revisit tailoring decisions.
- Capture lessons — Document what tailoring decisions worked and what didn't, so future projects in the same organization can benefit from the learning.
Tailoring in Agile, Predictive, and Hybrid Contexts
Tailoring is often misunderstood as something that only happens in agile environments. In reality, every project tailors — even predictive projects. The difference is whether the tailoring is intentional and documented or accidental and ad-hoc.
In predictive environments, tailoring involves decisions like: which phase gates to include, how much detail in the work breakdown structure, what level of earned value management to apply, and how many formal reviews to schedule. Many predictive organizations have a project management methodology that is itself a tailored baseline — and the project manager tailors further for each specific project.
In agile environments, tailoring is built into the framework through inspect-and-adapt cycles. Scrum teams tailor their definition of done, sprint length, meeting cadence, and artifact format. Kanban teams tailor their WIP limits, class of service policies, and board design. The agile principle of "inspect and adapt" is essentially a continuous tailoring process.
In hybrid environments, tailoring becomes even more important. The project manager must decide which parts of the project benefit from predictive rigor and which benefit from agile flexibility — and must manage the interfaces between them. This requires deep understanding of both approaches and the judgment to apply them contextually.
Tailoring connects strongly to Principle 4: Focus on Value (tailoring eliminates non-value-adding processes), Principle 5: Systems Thinking (tailoring requires understanding the system context), Principle 8: Quality (tailoring ensures quality by fitting processes to context), and Principle 11: Adaptability and Resiliency (tailoring is how adaptability is operationalized).
← Previous: Principle 6 — Leadership | Back to PMBOK 7 Principles | Next: Principle 8 — Quality →