Post

Principles 1 to 3: holistic view, value, and quality

PMBOK 8 cut twelve principles down to six. The first three are adopt a holistic view, focus on value, and embed quality into processes and deliverables. None of them will be asked as a definition, and all of them decide which answer is best.

Principles 1 to 3: holistic view, value, and quality

Zara has a drawing now. Graph paper, two colours, the platform marked out square by square against the fork in the oak, and she is pleased enough with it that she carries it next door to be admired.

Mr Oyelaran admires it. Then he puts it on the bench and looks at it for longer than she wants him to.

“How do you get up?”

She turns the paper over, as though the ladder might be on the back. It is not on the back. It is not anywhere, because she had been drawing the part she could picture, which was the floor and the walls and the window she intends to lean out of.

“What are you going to do up there?”

Live in it, she says, which is not true, and she can hear that it is not true while she is saying it. He waits. She tries again, and the real answer turns out to be reading without her brother finding her, and watching the road for her mum’s car.

“And when you’ve cut a board, when do you check it’s square?”

At the end, she says, when they are all cut, because that way she only has to stop once.

He does not tell her she is wrong. He asks what happens to the other nineteen boards if the first one was out by half a centimetre and she finds out on Sunday.

Explain it like I’m 10

Three questions, and not one of them is about how to build a treehouse.

The first is about everything the drawing left out. A treehouse is not only the bit you can picture. It is the ladder, and the tree that is still growing, and the neighbour who will see it from her kitchen, and the dad who has to say yes. Zara drew the part she was excited about and called it the plan. Most people do.

The second sounds like being asked to justify yourself, which is why she resents it. What is it for? Not what is it, which is a treehouse. What will she actually do up there? Her real answer changes the drawing. Reading needs light, so the window matters more than she thought. Watching the road means the window faces the house, not the field.

The third is about when you check. Checking at the end feels efficient, because you stop once instead of twenty times. It is only efficient if everything was fine. If the first cut was wrong, checking at the end means finding out after you have made the same mistake nineteen more times, and the cheapest moment to catch it was the moment after you made it.

None of the three tell her how to build anything. They are about how to think while she builds, which is a different kind of help, and the kind she will still be using on the build after this one.

The grown-up version

Twelve became six

PMBOK 8 opens its Standard for Project Management with a chapter called Project Management Principles, and the 7th edition’s twelve principles are now six. PMI did not delete half of them. It refined them, which in practice means it collapsed overlapping ideas into fewer statements, and the Guide carries an appendix on that refinement for anyone who wants the reasoning.

The six are: adopt a holistic view, focus on value, embed quality into processes and deliverables, be an accountable leader, integrate sustainability within all project areas, and build an empowered culture. This post covers the first three. The next covers the rest.

What tells you how PMI wants these used is the shape of each section. Every principle gets exactly three subsections: project impact, principle in action, and connected performance domains. Not a definition, an etymology, and a history. Impact, action, and what it touches. The chapter also opens with a section on the project management mindset before it reaches the first principle, which is PMI saying, before you ask, that this chapter is about disposition rather than procedure.

Adopt a holistic view

The principle asks you to see the project as part of a system rather than as a box with a boundary. The organisation around it, the environment outside that, the other projects competing for the same people, the operations that will inherit what you build. Post 3 laid out that chain. This principle is the instruction to keep looking at it while you work.

In practice it is the instruction to widen the frame before you act. A delay in your schedule is a schedule problem until you notice it releases a specialist two weeks early into a programme that needed her. A change request is a scope question until you notice what it does to the handover you already agreed with operations.

On the exam this shows up as a preference. Given four defensible options, the one that accounts for an effect outside the project boundary tends to be the one PMI wants, and the one that optimises your own numbers at the system’s expense tends to be the distractor.

Focus on value

Output is what you produced. Value is what it was for. A project can deliver its full scope, on time and inside budget, and produce nothing anybody wanted, and the 7th edition’s language about outcomes exists precisely because that keeps happening.

Two behaviours follow, and they pull in opposite directions, which is why this is harder than it reads.

The first is subtraction. Work that produces no value is waste even when it is in the plan, and gold plating is the version of this the exam likes best: a team adding polish nobody asked for, usually with good intentions, always at someone’s cost. The second is resistance. When a schedule is under pressure, the things cut first are often the things carrying the value, because they are the least visible. Testing. Training. The handover.

The practical question is the one Mr Oyelaran asked. What is it for, answered specifically enough to change a decision. “A customer portal” is not an answer. “So the forty people in the call centre stop retyping orders by hand” is, and it tells you which feature survives the cut.

Embed quality into processes and deliverables

Read the full title, because the first half is the part people skip. Processes and deliverables. Quality in what you produce, and quality in how you produce it.

The idea underneath is prevention over inspection. Inspection finds defects after they exist, when fixing them costs more than preventing them would have, and the cost of that gap grows the longer the defect survives. Half a centimetre caught on the first board is one recut. Caught on Sunday it is twenty.

This is also the principle most often misread as its opposite. A team finding defects late does not have an inspection shortage. It has a process that lets defects through, and adding a final gate makes the finding later, not earlier. Build the check into the step: a definition of done, a peer review at the point of work, a test that runs when the code is written instead of in a phase named after testing.

Why none of this is asked as a definition

There is no task on the Examination Content Outline called “apply the holistic view principle”, and no question will ask you to name the six. The outline has 26 tasks describing what project managers do, and principles are not among them.

They decide which answer is best. A scenario gives you four options that are all legal, all plausible, and all something a competent person might do. What separates them is which one a project manager holding these principles would choose, and the exam is written on the assumption that you hold them rather than that you can list them.

Which is why reciting the six is close to worthless and internalising three of them is worth a lot. If you want a study habit for this chapter, read a principle and then go back to the practice questions you got wrong, and check whether the right answer was the one that took the wider view, protected the value, or fixed the process instead of adding a gate. It usually was.

Exam trap

Tempting: the team keeps finding defects just before release, so you add a formal quality gate at the end of the cycle to catch them before they reach the customer.

Why PMI rejects it: the principle is embed quality into processes and deliverables, and a gate at the end is inspection, not embedding. It catches the same defects later in their life, when they cost more, and it leaves the process that produced them untouched. The answer PMI is looking for changes where quality is built in, which means the definition of done, the review at the point of work, or the test that runs as the work is made. A gate can be a reasonable addition on top of that. It is never the fix on its own.

Key points

  • PMBOK 8 refines the 7th edition’s twelve principles into six. The first three are adopt a holistic view, focus on value, and embed quality into processes and deliverables.
  • Every principle in the Standard gets the same three subsections: project impact, principle in action, and connected performance domains. The chapter is about disposition, and it opens with a section on the project management mindset.
  • The holistic view means widening the frame before acting. On the exam, the option accounting for an effect outside the project boundary usually beats the one optimising your own numbers.
  • Focus on value means subtracting work that produces nothing, and defending the work that carries the value, which gets cut first under pressure because it is the least visible.
  • Gold plating is the exam’s favourite value failure: polish nobody asked for, added with good intentions, paid for by someone else.
  • Quality covers processes as well as deliverables. Prevention beats inspection, and a defect costs more the longer it survives.
  • A team finding defects late has a process problem. Adding a final gate finds them later, not earlier.
  • No ECO task asks you to name a principle. They are tested as the reason one option beats three others.

Student notes

A printable study sheet for this episode, with the six principles on one side and the three exam behaviours they produce on the other, is being put together. Email [email protected] and I will send it across when it is ready, along with the sheets for the other episodes as they are written.

Practice questions

1. Your project will finish two weeks early. The same two weeks free a specialist who is the only person qualified to start the integration work on another project in your programme, though nobody has raised this with you. What is the best action?

  • A. Confirm your early finish and release the specialist through the normal resourcing process once your project closes.
  • B. Hold the specialist until formal closure, since she is assigned to your project and your project is still open.
  • C. Raise the early finish and the specialist’s availability at programme level now, so the dependent work can be rescheduled.
  • D. Approach the other project manager directly and offer the specialist informally.
Answer **C.** Adopting a holistic view means acting on an effect that falls outside your own boundary, and the value of finishing early is realised by the programme rather than by your project. A is correct procedure and too slow, since the information is useful now and the routine release is what everyone already expects. B optimises your own position at the system's expense. D moves a programme-level resourcing decision into a private arrangement, which is the same error Post 3's dependency question tested.

2. A development team has spare capacity in the final iteration and adds a configurable dashboard to the delivered product. It works, it was not requested, and it did not delay anything. How should this be assessed?

  • A. Acceptable, since the team used otherwise idle capacity and the schedule held.
  • B. Acceptable, since additional capability increases the value delivered.
  • C. A value failure, because effort produced an unrequested feature that now has to be supported and maintained.
  • D. A governance failure, because the team did not raise a change request.
Answer **C.** This is gold plating. Focusing on value means work that produces no value is waste regardless of whether it was free to build, and the dashboard is not free: it carries documentation, support, and maintenance for as long as the product lives. B mistakes capability for value. A treats spare capacity as justification. D is tempting and names a real procedural issue, but the question asks how to assess the outcome, and the substantive problem is the unrequested scope rather than the paperwork.

3. A quality review finds that most defects originate in requirements that were ambiguous when the work started. The sponsor proposes adding a second round of user acceptance testing before each release. What is the better response?

  • A. Accept the proposal, since more testing will catch more defects before the customer sees them.
  • B. Propose addressing requirement clarity at the point the work is defined, with acceptance criteria agreed before an item is started.
  • C. Accept the proposal and add a root cause analysis after the next release.
  • D. Reject the proposal, since the defects are a requirements problem and testing cannot help.
Answer **B.** Embedding quality into the process means acting where the defects are created, and the review has already told you that is the point where requirements are agreed. A adds inspection downstream of the cause and makes the feedback loop longer. C defers the diagnosis you already have. D is wrong at the other extreme, since testing is still useful and the principle does not ask you to remove it, only to stop relying on it to compensate for an upstream problem.

Next episode

The first three principles are about what you look at, what you are for, and how you work. The last three are about how you behave, and they are the ones PMI changed most in tone. Next in the series: be an accountable leader, integrate sustainability within all project areas, and build an empowered culture, including why sustainability now has a principle of its own when it has no task on the outline.


PMP, PMBOK, and PMI are registered marks of the Project Management Institute, Inc. This blog is independent and is not affiliated with, endorsed by, or sponsored by PMI. Content is for study support only and does not count toward the 35 contact hours required for PMP eligibility. Always refer to PMI’s official Examination Content Outline and PMP Handbook.

This post is licensed under CC BY 4.0 by the author.