Methodology Project General: Tailoring at Project and Organizational Level

PMBOK v8 Definition

The Methodology Project General refers to the organization's established project management methodology that serves as the foundation for tailoring at both the project and organizational levels. According to PMBOK v8, this general methodology is adapted through tailoring at the project level to create specific methodologies for individual projects (Project A, B, C, D, E), and through tailoring at the organizational level to create specialized methodologies for different project categories (small projects, large/sensitive projects). The methodology is influenced by Enterprise Environmental Factors and General Guides, providing a structured framework that aligns with The Standard for Project Management, which identifies principles that guide behaviors and actions of project professionals and stakeholders.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of how project management methodologies are adapted rather than applied rigidly. Questions typically present scenarios where you must determine whether tailoring occurs at the project level (individual project customization) or the organizational level (creating standardized variations for project categories). Expect scenario-based questions asking what the project manager should do when a standard methodology doesn't fit a specific project's needs.

Key Points to Remember (for the exam)

• Two Levels of Tailoring: Tailoring occurs at project level (individual methodology per project) AND organizational level (standardized methodologies for project categories like small vs. large/sensitive projects)

• General Methodology as Base: The General Project Management Methodology is the foundation from which all tailored versions derive—it is NOT applied identically to all projects

• Enterprise Environmental Factors Influence: These factors (organizational culture, industry standards, regulatory requirements) directly shape how methodologies are tailored

• Methodology for Small Projects: Organizations create simplified, streamlined methodologies specifically for small projects to avoid unnecessary overhead

• Methodology for Large/Sensitive Projects: Organizations create more rigorous, controlled methodologies for projects with high risk, high visibility, or strategic importance

• Tailoring is NOT Optional: PMBOK v8 treats tailoring as a necessary practice—applying a methodology without tailoring is a common exam trap

• Principle-Driven: The Standard for Project Management principles guide HOW tailoring is performed, ensuring consistency while allowing flexibility

Typical PMI Exam Example

A project manager joins an organization that has a standard project management methodology. The project is a small internal IT upgrade with low risk and a 3-week timeline. What should the project manager do? Answer: Tailor the organization's methodology at the project level to create a simplified approach appropriate for a small project, rather than applying the full standard methodology.

PMI Exam Traps

• Trap: Thinking "Methodology Project General" means one methodology fits all projects

• Reality: The general methodology is a BASE that requires tailoring for each project's unique characteristics

• Trap: Confusing project-level tailoring with organizational-level tailoring

• Reality: Project-level = per project customization; Organizational-level = creating standardized categories (small vs. large)

• Trap: Believing tailoring only applies to large or complex projects

• Reality: ALL projects require tailoring—small projects need simplified methodologies to avoid waste

• Trap: Assuming Enterprise Environmental Factors are optional considerations

• Reality: These factors are MANDATORY influences that directly shape how methodologies are tailored

Important PMI Connections

Quick Review Questions

1. A project manager is assigned to a high-risk, high-visibility project. Should they use the organization's small project methodology or create a tailored methodology for large/sensitive projects?

2. What is the relationship between the "General Project Management Methodology" and the "Methodology for Project A"?

3. When tailoring at the organizational level, what two specific methodology categories does PMBOK v8 identify?

4. True or False: Enterprise Environmental Factors are optional considerations when tailoring a project management methodology.

5. A project manager applies the organization's standard methodology without any modifications to a 2-week project. Is this correct according to PMBOK v8?

PMBOK v8 Reference

Section 3 - Figure 3-2: Tailoring at the Project Level and Tailoring at the Organizational Level (General Project Management Methodology, Enterprise Environmental Factors, General Guides)

Note: The PMBOK v8 content provided focuses on the concept of methodology tailoring as illustrated in Figure 3-2, showing the relationship between the general methodology, project-level tailoring, and organizational-level tailoring, with Enterprise Environmental Factors and General Guides as influencing elements.