Skip to main content Skip to course navigation

Project Charter

Learning Objective

By the end of this lesson, the learner should be able to:

  • Explain the purpose of a Project Charter.
  • Identify the six important elements of a Project Charter.
  • Explain the purpose of the Business Case, Problem Statement and Goal Statement.
  • Explain how the Scope Statement defines project boundaries.
  • Explain the importance of the Timeline and Team Members.
  • Understand why the Project Charter is a living document.
  • Explain how a Project Charter prevents scope creep and supports stakeholder alignment.

1. Introduction

A Project Charter is a formal document used to define and establish a Six Sigma improvement project.

It provides a clear understanding of:

  • Why the project is being undertaken
  • What problem is being addressed
  • What the project is expected to achieve
  • What is included within the project
  • Who is involved
  • When the project is expected to be completed
  • What benefits are expected

A well-defined Project Charter helps prevent scope creep and ensures alignment among stakeholders.

2. Why a Project Charter Is Important

A Six Sigma project can involve several people, departments and stakeholders.

Without a clear agreement at the beginning, the project can gradually move away from its original purpose.

The Project Charter helps the team maintain focus by clearly defining:

  • Project boundaries
  • Objectives
  • Responsibilities
  • Expected benefits

It also provides a common reference for the project team and management.

3. The Six Important Elements of a Project Charter

The six important elements identified in the Black Belt programme are:

  1. Business Case
  2. Problem Statement
  3. Goal Statement
  4. Scope Statement
  5. Timeline
  6. Team Members

These elements provide the basic structure needed to define the project clearly.

4. Business Case

The Business Case explains why the project is important to the organization.

It describes the expected business value from addressing the problem.

Examples of business benefits include:

  • Increased customer satisfaction
  • Increased customer count
  • Improved quality
  • Increased profit
  • Improved savings

The Business Case connects the improvement project to meaningful organizational benefits.

Example

If a company is experiencing a high level of product defects, the Business Case may identify:

  • Increased customer complaints
  • Higher rework costs
  • Material losses
  • Reduced customer satisfaction
  • Reduced profitability

The project therefore has a clear business reason for being undertaken.

5. Problem Statement

The Problem Statement clearly describes the problem that exists.

It should establish the situation that requires improvement without prematurely presenting the solution.

A clear Problem Statement gives the project team a common understanding of the issue being addressed.

Example

Instead of:

Improve the production process.

A project should clearly identify the actual problem, such as:

The packaging line is experiencing a high level of defects, resulting in increased rework and customer complaints.

The Problem Statement establishes what needs to be investigated.

6. Goal Statement

The Goal Statement defines what the project intends to achieve.

The goal should provide a measurable direction for the project.

Example

Reduce delivery delays by 30%.

A measurable goal makes it possible to determine whether the project has achieved its intended result.

7. Scope Statement

The Scope Statement defines the boundaries of the project.

It helps the team understand what is included within the project and prevents the project from expanding unnecessarily.

The Black Belt source specifically identifies the Scope Statement as describing the physical boundaries of a project.

Example

If the project concerns packaging defects:

Scope = Packaging line

This establishes the physical area in which the project will operate.

A clearly defined scope helps prevent scope creep, where additional problems or areas are gradually added to the original project.

8. Timeline

The Timeline establishes the expected duration of the project.

It gives the team and stakeholders a clear understanding of when the project should progress and when it is expected to be completed.

Example

Timeline = 6 months

The Black Belt source uses this six-month timeline in its packaging plant case study.

9. Team Members

The Project Charter identifies the people who will participate in the project.

The team may include people with different responsibilities and knowledge of the process.

For example, the packaging plant case identifies:

  • Operators
  • Engineers
  • Quality team

Clearly identifying team members helps establish who is involved in the project.

10. Project Charter as a Living Document

A Project Charter is not simply created once and then forgotten.

The Project Charter should be reviewed throughout the project and regularly compared with the original plan.

As the project develops, the team may gain a better understanding of the problem, scope or objectives.

The Charter therefore remains an important reference throughout the project.

11. Tools Used with the Project Charter

The Black Belt programme identifies the following supporting tools:

  • Charter Template
  • SMART Goals
  • Stakeholder Analysis

Charter Template

A standard template helps ensure that important project information is not overlooked.

SMART Goals

SMART provides a structure for developing clear goals:

  • Specific
  • Measurable
  • Achievable
  • Relevant
  • Time-bound

Stakeholder Analysis

Stakeholder Analysis helps identify the people affected by the project and those who need to be involved or aligned.

These tools support clear project definition and stakeholder alignment.

12. Application Example — Logistics Company

A logistics company wants to reduce late deliveries.

The Project Charter defines:

  • Scope: Delivery process
  • Goal: Reduce delays by 30%
  • Roles: Supervisor, analyst and driver

By defining these elements, the project team has a clear understanding of what the project covers, what it intends to achieve and who is involved.

13. Case Study — Packaging Plant

A packaging plant is experiencing high defect rates.

The Project Charter establishes:

  • Scope: Packaging line
  • Goal: Reduce defects by 25%
  • Timeline: 6 months
  • Roles: Operators, engineers and quality team

The clear definition of the project helped the team remain focused.

The case study reports that the project achieved a 28% reduction in defects and generated $200K in annual savings.

The important lesson is not simply the result. It is that a clearly defined Charter gave the project a common direction.

14. Project Charter and Stakeholder Alignment

The Project Charter provides a common understanding between the project team and stakeholders.

It establishes:

  • The reason for the project
  • The problem being addressed
  • The intended result
  • The project boundaries
  • The people involved
  • The expected timeframe

This helps ensure that stakeholders understand what the project is intended to accomplish.

15. Common Problems When the Charter Is Weak

A poorly defined Charter can lead to:

  • Unclear project objectives
  • Unclear project boundaries
  • Confusion about responsibilities
  • Expansion of project scope
  • Misalignment among stakeholders
  • Difficulty measuring project success

A strong Charter provides a foundation for disciplined project execution.

16. Black Belt Perspective

For a Black Belt, the Project Charter establishes the foundation for disciplined project execution.

Before moving deeply into data collection and analysis, the Black Belt must have a clear understanding of why the project exists, what problem is being addressed, what result is expected, what the boundaries are, who is involved and when the project should be completed.

A well-defined Charter keeps the project focused while providing a common reference for the project team and stakeholders.

17. Lesson Practice

Scenario

A manufacturing company has a high defect rate on one packaging line.

Management wants the defect rate reduced, but the project team has not yet formally defined the project.

Prepare the basic elements of a Project Charter:

  • Business Case
  • Problem Statement
  • Goal Statement
  • Scope Statement
  • Timeline
  • Team Members

Then consider:

Why is it important to define the scope before the project begins?

18. Key Learning Points

After completing this lesson, the learner should understand that:

  1. A Project Charter formally establishes a Six Sigma improvement project.
  2. The six important elements are Business Case, Problem Statement, Goal Statement, Scope Statement, Timeline and Team Members.
  3. The Business Case explains why the project matters to the organization.
  4. The Problem Statement defines the current problem without prematurely prescribing a solution.
  5. The Goal Statement defines the measurable result.
  6. The Scope Statement defines the project boundaries.
  7. The Timeline establishes the expected project duration.
  8. Team Members identifies the people participating in the project.
  9. The Charter should remain a living document throughout the project.
  10. Charter Templates, SMART Goals and Stakeholder Analysis support project definition and alignment.
  11. A clear Charter helps prevent scope creep.
  12. A clear Charter supports stakeholder alignment and disciplined project execution.

Lesson Conclusion

The Project Charter establishes the foundation of a Six Sigma project. It defines the project’s purpose, problem, objective, boundaries, people and timeframe.

A well-defined Charter helps prevent scope creep, maintains stakeholder alignment and provides a common reference for the project team.

Most importantly, the Project Charter is a living document and should be reviewed throughout the project to ensure that progress remains aligned with the agreed plan.