Direct answer

Use project processes and practices as tailorable decision support, connecting actions, outputs, governance, feedback, and outcomes.

What to know

  • A process transforms inputs through actions into useful outputs.
  • Practices should support decisions, coordination, control, or learning.
  • The Eighth Edition’s process guidance is non-prescriptive.
  • Effectiveness matters more than producing artifacts for their own sake.

How to apply it

Define the decision or control need first, then choose the lightest reliable practice and clarify ownership, timing, and evidence.

Worked example

A high-risk supplier may need formal acceptance criteria and change records; a low-risk internal prototype may need a shared backlog and short review cadence.

Common mistakes

  • Equating artifact completion with outcome achievement.
  • Copying every process into every project.
  • Removing controls without assessing legal or contractual obligations.

Exam and practice connection

Understand why a process exists and how it changes by approach; this supports scenario reasoning better than rote sequencing.