A project charter typically includes:

Question

Options

• AControl charts
• BFishbone diagram
• CBusiness case
• DStatistical tests

• A
  2% (1)
• B
  2% (1)
• C
  92% (46)
• D
  4% (2)

Explanation

A project charter is a foundational document that formally authorizes a project and provides the high-level information needed to initiate it - the business case (option C) is a core component, as it justifies why the project exists by outlining the problem, opportunity, and expected benefits.

Why the distractors are wrong:

• A. Control charts - these are quality control tools used during project monitoring/controlling to track process stability over time, not project initiation documents.
• B. Fishbone diagram - also called an Ishikawa or cause-and-effect diagram, this is a root cause analysis tool used in quality management or problem-solving, not charter creation.
• D. Statistical tests - these belong to quality analysis and data-driven decision-making phases, far removed from the charter's purpose.

Memory tip: Think of the project charter as the project's birth certificate - it needs a reason for existing (business case), a name (project title), and authority behind it (sponsor signature). If a tool sounds analytical or graphical (charts, diagrams, tests), it belongs later in the project lifecycle, not in the charter.

No community discussion yet for this question.