Let's first talk about the similarities between PMBOK7 and PRINCE2 (only talk about similarities, not whether to refer to them):
First, all adopt a principled management structure
PMBOK7 12 Principles:
▶ Be a diligent, respectful, and caring steward (see Section 3.1).
Be a diligent, respectful, caring steward
▶ Create a collaborative project team environment (see Section 3.2).
Create a collaborative project team environment
▶ Effectively engage with stakeholders (see Section 3.3).
Interact effectively with stakeholders
▶ Focus on value (see Section 3.4).
Focus on value
▶ Recognize, evaluate, and respond to system interactions (see Section 3.5).
Identify, evaluate, and respond to system interactions
▶ Demonstrate leadership behaviors (see Section 3.6).
Demonstrate leadership behavior
▶ Tailor based on context (see Section 3.7).
Trim based on the scenario
▶ Build quality into processes and deliverables (see Section 3.8).
Incorporate quality into processes and deliverables
▶ Navigate complexity (see Section 3.9).
Navigating complexity
▶ Optimize risk responses (see Section 3.10).
Optimize risk response
▶ Embrace adaptability and resiliency (see Section 3.11).
Embrace adaptability and resilience
▶ Enable change to achieve the envisioned future state (see Section 3.12).
Drive change to realize future visions
Prince2 Seven Principles:
▶Continued business justification
Continuous business validation
▶Learn from experience
Lessons learned
▶Defined roles and responsibilities
Clearly defined roles and responsibilities
▶Manage by stages
Manage by phase
▶Manage by exception
Exception management
▶Focus on products
Focus on products
▶Tailor to suit the project
Crop according to the project
Second, the performance domain management (strictly speaking P2 is the theme) structure is adopted
PMBOK7 Eight Performance Domains:
▶ Stakeholders,
Interested Parties
▶ Team,
team
▶ Development Approach and Life Cycle,
Development methodology and lifecycle
▶ Planning,
planning
▶ Project Work,
Project work
▶ Delivery,
delivery
▶ Measurement,
measurement
▶ Uncertainty.
uncertain
Prince2 Seven Themes:
▶ Business Case,
Business case
▶ Organization,
organization
▶ Quality,
quality
▶ Plans,
▶ Risk,
risk
▶ Change,
alter
▶ Progress,
progress
Third, the value information flow is also clearly expressed
PMBOK7 Value Stream:
PRINCE2 Value Stream:
Fourth, there are no tools for talking about it at great length
PMBOK7 describes the style of the tool:
PMBOK7's description of the tool is limited to the explanation of the terms in the following figure, without a more detailed explanation.
PRINCE2 describes the style of the tool:
The impact of the environment on the project was emphasized
PMBOK7：
The internal environment is described in 2.4.1 and the external environment is described in 2.4.2
PRINCE2：
PRINCE2 itself is dedicated to building a controlled project environment, and in Chapter 21, it describes in detail how to tailor and implant methodologies into a project to build the right environment.
Sixth, the project life cycle (process) has been raised to a higher position
In Chapter 2.3, the third of the eight performance domains describes the development methodology and life cycle in detail.
Although the life cycle of specific industries and company methodologies is not covered in P2, when using P2 for company system and process construction, it is necessary to define the life cycle, which is also elaborated in P2.
Seventh, all of them explained the cutting part in a large way
The trim part is an important part of PMBOK7, and in the third chapter, PMBOK7 spends the entire chapter explaining how to trim the project, including why cut? What to cut? How to cut? How do I trim a performance field?
The trim part is also an important part of P2, and in chapter four, P2 also spends the entire chapter explaining how to tailor, both in the project environment and in the organization environment.
Trim based on the project environment
Tailoring (implantation) based on the tissue environment
8. Other similarities
Other similarities will need to be gradually interpreted in the subsequent sneak peek series.
Summary: There is no problem with local reference between systems, and it is true that there are many commonalities in project management, and maintaining the uniqueness of the overall level of the system is competitiveness.