A principle is a statement of what a decision should serve, written so that it holds whether the work is a bridge or a mobile application. The eighth edition carries six of them, and they form the standard for project management rather than the guide to it. That distinction matters on the exam, because a scenario question rarely has a rule that settles it and almost always has a principle that does.
The six replaced the twelve that the seventh edition introduced. The consolidation removed overlap rather than content, which is why a candidate who learned the twelve will recognise most of what follows under new headings.
The six, and what each one asks of you
| Principle | What it asks | What it looks like when it is missing |
|---|---|---|
| Adopt a holistic view | See the project inside the system that funds it, staffs it and receives its output, including the parts you do not control | A project delivered exactly as specified into an organisation that has moved on, or a dependency nobody owned because it sat between two teams |
| Focus on value | Judge the work by the benefit it produces rather than the deliverables it completes | A green status report on a project whose business case expired two quarters ago |
| Embed quality | Build quality into the process and the deliverable from the start rather than inspecting it in afterwards | A test phase discovering design faults, at the point in the schedule where fixing them costs the most |
| Lead accountably | Own the outcome, make the ownership visible, and hold others to the same standard without hiding behind process | An escalation log that records who was told rather than who decided |
| Integrate sustainability | Weigh environmental, social and economic effects over the life of what you are building, not the length of your involvement | A solution that meets every acceptance criterion and costs more to operate than it saves |
| Build empowered teams | Give the people doing the work the authority and the context to make decisions about it | A team that raises everything, because raising everything is the only safe behaviour when nothing has been delegated |
Two of the six are new emphases rather than restatements. Integrating sustainability arrived as a principle in its own right, and building empowered teams promotes what earlier editions treated as a leadership style into a standing expectation.
Why twelve became six
The twelve had genuine overlap. Stewardship, systems thinking and navigating complexity all asked the reader to look beyond the boundary of the project, and they now sit together under a holistic view. Quality and value appeared in several places and were consolidated into one each.
Tailoring is the interesting case. It was a principle in the seventh edition and is not one of the six, which reads at first like a demotion. What happened is that it moved from being one instruction among twelve to being the way all of them are applied, since a principle that holds for every project can only be followed by adapting it to the one in front of you.
A principle sets direction, a rule settles a case
The reason principles feel slippery in study is that they do not resolve situations on their own. Two project managers can apply focus on value to the same scenario and act differently, because one has a sponsor who will cancel a project and the other does not.
What a principle does is tell you which considerations belong in the decision. Faced with a change request that adds scope and delay, focus on value asks whether the change moves the benefit, embed quality asks what the compression will do to defect rates, and lead accountably asks who is entitled to make the call and whether that person has what they need to make it. The answer still depends on the project. The shortlist does not.
Reading an exam scenario through them
Scenario questions are usually built so that several options are defensible activities and one is the right next move. Principles are how the distinction is drawn.
An option that gathers information before acting usually beats one that acts immediately, because a holistic view asks what else is affected. An option that takes the decision to the team that owns the work usually beats one that decides for them, because empowered teams is a standing expectation rather than a style choice. An option that protects the benefit usually beats one that protects the schedule, because value is the thing being managed and the schedule is a constraint on producing it.
Where two options both look principled, the tie is broken by accountability. Escalating without a recommendation, or informing somebody instead of deciding, fails the fourth principle even when it looks diligent.
What the principles do not do
They do not authorise ignoring a governance requirement. A principle sits above the method and below the organisation's obligations, so a regulated approval that has to happen still has to happen, and the principle shapes how it is prepared rather than whether it is met.
They also carry no order of precedence. The six are not ranked, and a question that sets two of them against each other is testing whether you can find the option that serves both, which usually exists and is usually the one that involves talking to somebody before deciding.