ConceptReviewed
Project Charter
Name variants
- English
- Project Charter
- Katakana
- プロジェクト
- Kanji
- 憲章
Quality / Updated / COI
- Quality
- Reviewed
- Updated
- Source
- Citations & Trust
- COI
- none
TL;DR
A project charter formally authorizes a project and defines purpose and authority.
Definition
A project charter documents purpose, success criteria, authority, and key stakeholders to formally authorize work.It links objectives, scope, resources, and time, serving as a baseline for alignment and change control.It supports decisions to protect quality and schedule.
Decision impact
- Clear scope and objectives align priorities and reduce rework in decisions.
- Visible dependencies make schedule adjustments and resource trade-offs faster.
- Change and risk impacts can be assessed early, improving alignment.
Key takeaways
- Define deliverables and acceptance criteria to prevent scope drift.
- Record assumptions, constraints, and exclusions for shared expectations.
- Link dependencies to owners and dates to ease coordination.
- Review progress against the baseline, not just activity.
- Log changes with reasons and impacts to maintain transparency.
Misconceptions
- Plans are not immutable; controlled changes are expected.
- More detail is not always better if it raises maintenance cost.
- Documentation alone does not deliver results without execution.
Worked example
Example: Record business value, budget limits, and decision rights before project kickoff.When change requests arise, assess impact and renegotiate priorities with stakeholders.Review progress weekly and agree on mitigation if delays appear.Document major changes and approvals for traceability.
Citations & Trust
- Project Management (Open Textbook Library)