CH5: Project Chartering

What is a project charter?

What are the key traits of a project charter?

Can a project start without a charter?

An elevator pitch of project objectives, scope, and responsibilities; an informal contract between project team and sponsor.

Entered freely, cannot be changed arbitrarily, provides value for both parties, living document that can evolve.

Yes, but it may lack clarity, direction, and stakeholder alignment.

Why is a project charter used?

What percentage of projects fail, and how does a charter help?

What are the four main purposes of a project charter?

How does a charter protect the project manager?

To set up project success by defining purpose, aligning stakeholders, and authorizing the project manager.

70% of projects fail; a charter helps prevent failure by clarifying scope, roles, and objectives.

Authorize the project manager, create common understanding, build team commitment, and screen out poor projects.

By formally authorizing and empowering them, and reducing sponsor’s ability to change agreements.

When is a project charter needed?

What is the overall role of a project charter?

At project start, to:

• Ensure sponsor’s needs are understood.

• Provide reference and planning basis.

• Empower the project manager.

• Align everyone on the same page.

To align sponsor, project manager, and team at a high level; increase success likelihood by clarifying scope, purpose, milestones, risks, and commitments.

What are the typical elements of a project charter?

• Title – project name.

• Scope Overview – boundaries, product features, prevents scope creep.

• Business Case – purpose, justification, link to strategy, cost/benefit.

• Background – extra context (optional).

• Milestone Schedule & Acceptance Criteria – timeline of major milestones; standards for completeness and correctness.

• Risks/Assumptions/Constraints – risks (positive/negative), unproven assumptions, project limits.

• Resource Estimates – preliminary budget, what PM vs. sponsor controls.

• Stakeholder List – key stakeholders and their interests.

• Team Operating Principles – rules for meetings, respect, decision-making.

• Lessons Learned – knowledge from past projects for future use.

• Signatures & Commitment – formal commitment of sponsor, PM, and team.