Project charter Study Guide

📖 Core Concepts Project Charter – A short, high‑level document that states a project’s purpose, objectives, key deliverables, assumptions, constraints, risks, milestones, budget, stakeholders, and the authority granted to the project manager. Authority – Formal permission (usually signed by the sponsor) that lets the project manager use organizational resources and make decisions on behalf of the project. Stakeholders – Anyone who can affect or be affected by the project (sponsor, customers, team members, etc.). Initiating Process Group – The first phase of a project where the charter is created and stakeholders are identified. Scope (related concept) – The detailed work that must be performed; the charter provides the high‑level basis for defining scope later. 📌 Must Remember The charter formally authorizes the project and the project manager’s use of resources. It is created at the start of a phase or project by the project manager (often with sponsor input). Core elements that must appear: purpose/justification, high‑level objectives, success criteria, key deliverables, assumptions, constraints, high‑level risks, milestone schedule, budget, key stakeholders, PM authority. The charter is short and concise – it is not a detailed project plan. Serves as a baseline for scope management, change control, and governance throughout the project lifecycle. 🔄 Key Processes Initiate – Enter the Initiating Process Group. Identify Stakeholders – List all parties with interest or influence. Draft Charter – Fill in the core elements (purpose, objectives, etc.). Review & Refine – Get input from sponsor and key stakeholders. Obtain Signature – Sponsor signs, granting formal authority. Distribute – Share the signed charter with the project team and stakeholders; use it as the reference baseline. 🔍 Key Comparisons Project Charter vs. Project Scope Charter: High‑level, authorizing document; outlines purpose, objectives, authority, and top‑level constraints. Scope: Detailed description of what will be delivered and how; developed after the charter, using it as a foundation. ⚠️ Common Misunderstandings “The charter is a detailed plan.” – It only provides high‑level guidance; detailed planning occurs later. “Authority is automatic once the charter is written.” – Authority is granted only after the sponsor signs the charter. “All risks are fully listed in the charter.” – Only high‑level risks are captured; detailed risk management follows in the planning phase. 🧠 Mental Models / Intuition “Project Birth Certificate” – Think of the charter as the document that registers the project’s existence, gives it a name, and provides the newborn (project manager) with legal authority to act. 🚩 Exceptions & Edge Cases Matrix Organizations – The charter’s authority statement is especially critical when the PM must negotiate resource use across functional lines. Very Small Projects – Some organizations may combine the charter with a brief project plan, but the core elements must still be present. 📍 When to Use Which Use a Project Charter when you are starting a new project or a new phase and need formal approval and authority. Use a Detailed Scope Document or Project Management Plan after the charter, during the Planning Process Group, to flesh out how the objectives will be achieved. 👀 Patterns to Recognize Bullet‑point checklist in exam questions: purpose, objectives, deliverables, assumptions, constraints, risks, milestones, budget, stakeholders, authority → likely describing a charter. Language of “authorizes” or “grants authority” → signals the charter’s role rather than a planning artifact. 🗂️ Exam Traps Distractor: “The charter includes a detailed work breakdown structure.” – Wrong; the WBS belongs in the project plan. Distractor: “A charter is optional if the sponsor is supportive.” – Wrong; formal authorization is required by PMI standards. Distractor: “All project risks must be listed in the charter.” – Wrong; only high‑level risks are captured. Distractor: “The charter replaces the need for a stakeholder register.” – Wrong; the charter lists key stakeholders, but a full register is still created later.