Develop Project Charter

Sensei Short Scroll 1 Initiating Process Group

Develop Project Charter

Introduction: Why This Matters

The project charter is the single most important document created during project initiation. It officially authorizes the project, names the project manager, and establishes the high level boundaries, objectives, and stakeholders.

On the PMP exam, many situational questions hinge on whether a charter exists. If there is no charter, the project manager lacks authority. In practice, a strong charter prevents scope confusion, empowers the project manager, and gives the team a clear sense of purpose before detailed planning begins (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: Formally authorize the project or phase and grant the project manager authority to use organizational resources.

Key Objectives:

  • Provide formal authorization to proceed.
  • Define measurable high level objectives.
  • Identify initial scope, constraints, and risks.
  • Name the sponsor and the project manager.
  • Establish authority of the project manager to apply organizational resources.
  • Align project goals with business strategy.

Overview

Develop Project Charter is the initiating process that formally starts the project and links it to the organization’s strategic objectives.

  • Inputs: Business case, agreements, enterprise environmental factors, and organizational process assets.
  • Tools and Techniques: Expert judgment, data gathering, interpersonal and team skills, and meetings.
  • Outputs: The project charter itself and the initial assumption log.

Characteristics

  • Project purpose and justification: Explains why this project exists and how it supports the business case.
  • Measurable objectives: Defines success criteria that can be quantified and verified.
  • High level requirements: Describes broad deliverable features or characteristics.
  • High level risks: Captures early threats and opportunities.
  • Summary milestones: Identifies critical dates or timeframes.
  • Budget summary: States initial funding estimates or limits.
  • Project manager authorization: Formally grants decision making authority to the project manager.
  • Key stakeholders: Lists sponsor, customers, key departments, and external partners.

Practical Example

Context: A retail company wants to roll out a new point of sale (POS) system to all stores.

Activities:

  • Activity 1: Define purpose and objectives, such as improving checkout speed, reducing system downtime, and enhancing customer satisfaction.
  • Activity 2: Capture scope, budget, risks, sponsor, and project manager authority, for example rollout to 500 stores in North America with a 10 million dollar budget and explicit cross functional resource access.

Outcome: The project is authorized to move into detailed planning, with leadership alignment, funding secured, and the project manager formally empowered to lead the work.

Common Pitfalls

Pitfall Category One: Vague objectives

  • Pitfall: Objectives are not measurable, which leads to unclear success criteria.
  • Prevention: Use specific, measurable, time bound objectives that follow a SMART style approach.

Pitfall Category Two: No named project manager

  • Pitfall: Leadership gaps occur because no one is clearly accountable.
  • Prevention: Ensure the charter explicitly names the project manager and states their authority.

Pitfall Category Three: Skipping the charter

  • Pitfall: Teams rush into planning and execution without formal authorization.
  • Prevention: Require sponsor sign off on the charter before significant work begins.

Pitfall Category Four: Treating the charter as a detailed plan

  • Pitfall: The charter becomes overloaded with detail and loses its strategic focus.
  • Prevention: Keep the charter high level and use the Planning processes to build detailed baselines.

Sensei Tip : Any time you feel lost about why a project exists or what success looks like, return to the charter. It is your compass for every major decision.

Exam Alert : If the scenario describes work starting without formal authorization, the best answer is usually to work with the sponsor to create or confirm the project charter before continuing.

Exam Lens

Patterns on the PMP Exam:

  • If the project has no authorization yet, the correct first step is almost always developing or securing the charter.
  • If a conflict arises about objectives, the project manager should refer back to the charter.
  • If the question asks where the project manager’s authority comes from, the charter is the formal source.

Sample Question

Question: A project manager is assigned to lead a new initiative. Stakeholders are excited and already want to begin detailed scheduling. The sponsor has not yet approved a formal document. What should the project manager do next?

  1. Begin developing the schedule since stakeholders are ready.
  2. Work with the sponsor to create and approve the project charter.
  3. Proceed with risk identification workshops.
  4. Start acquiring resources to avoid delays.

Correct Answer: B. The project must be formally authorized with a charter before detailed planning or resource allocation.

Quick Recap Table

Element Why it matters Exam watch point
Charter authorization Gives the project legal existence. Always secure authorization before planning.
Measurable objectives Defines clear success criteria. Avoid vague or subjective goals.
Named project manager Clarifies authority and leadership. Must be explicitly stated in the charter.
High level scope and risks Provides boundaries for planning and early risk awareness. Helps prevent confusion and scope creep.
Alignment to business case Ensures strategic fit and value. Always link back to organizational benefit.

Key Takeaways

  • The project charter is the foundation of any project.
  • It formally authorizes the project and names the project manager.
  • It provides high level objectives, scope, risks, and constraints.
  • It aligns the project with business strategy and stakeholder expectations.
  • On the PMP exam, if the charter is missing, securing it is usually the first correct action.

Next Step

We now move to the second process in the Initiating Process Group, Identify Stakeholders. This process ensures you know who is impacted by or can influence the project, laying the groundwork for effective engagement and communication strategies.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (Project Management Body of Knowledge Guide) (7th ed.). Project Management Institute.

Scroll to Top