Develop Project Charter: Things to Consider

Ratings are encouraged and provide useful feedback to the author.

The following are things to consider when initiating a new project for your organization.

The Shortened Version is:

EXECUTIVE SUMMARY: Paint a clear picture of the project using 1-2 paragraphs, including a Problem and Solution (Answer) Statement.

PRODUCT OBJECTIVES: Think of the project broken into its largest pieces.  Then, define what is to be delivered in 3-5 statements. Ensure these statements are “SMART”: Specific, Measurable, Attainable, Relevant, Time-bound (http://en.wikipedia.org/wiki/SMART_objective)

MEASURES OF SUCCESS: When will the project team ‘know’ when the project is complete?  Is there a specific “Measuring Stick”, or “Litmus Test” you would suggest for this project?  Convey details about deliverables that must happen in order to say they’re complete.

PROJECT RESOURCES: At minimum, list the Key Stakeholders, Budgets, and Timeframe, as well as, any other expectations regarding resources.

RISKS AND ASSUMPTIONS: At minimum, list the project priorities, as well as, anything that may impact/limit the project’s success.

For a more thorough walk-through of the Charter, consider the following: 

EXECUTIVE SUMMARY:

Paint a clear picture of the project using 1-2 paragraphs, including a Problem and Solution (Answer) Statement.

• Mission Statement (optional):
• Problem Statement:
  • Describe the “REAL” or “ACTUAL” Problem (in very specific terms), include Diagnostic Findings, and outputs of any Analysis.  “I need a new car”, is not a good problem statement.  But, “Currently, I lack adequate transportation to and from work each week” is a very helpful problem statement.
• Answer Statement:
  • Describe the Remedy (in the most general terms possible), include any Must-Haves in the Solution, the Value Proposition, and any Special Requirements.  “Buy a new car”, is not a good solution statement.  However, “Explore transportation options to identify and implement a solution that best serves me in terms of (1) the lowest-cost, (2) the least impact to my schedule, and (3) abating the stress of to/from work commute”, is an outstanding, enabling solution statement.

PRODUCT OBJECTIVES:

Think of the project broken into its largest pieces.  Then, define what is to be delivered in 3-5 statements. Ensure these statements are “SMART”: Specific, Measurable, Attainable, Relevant, Time-bound (http://en.wikipedia.org/wiki/SMART_objective)

• What is the FINAL OUTPUT?  (e.g., a Product, a Process, a Service)
• List the things it MUST be able to do in order to solve the problem stated above.

MEASURES OF SUCCESS:

When will the project team ‘know’ when the project is complete?  Is there a specific “Measuring Stick”, or “Litmus Test” you would suggest for this project?  Convey details about deliverables that must happen in order to say they’re complete.

• What would you say the “Measuring Stick”, or “Litmus Test” would be for this project?
• Are there any Contracts to be used as Inputs?
• How many do we need?
• What completion date should be targeted?
• How much money are we willing to spend to achieve the desired results? 
• What are the HIGH-LEVEL CHARACTERISTICS OF THE FINAL OUTPUT?
  • Requirements
  • Dimensions
  • Packaging, Branding
  • Functionality
  • Monetary Constraints
  • Time Constraints
• What deliverables are “related to” the FINAL OUTPUT?
  • Validating the output conforms to requirements
  • Writing Processes and Supporting Documentation
  • Establishing on-going Support and Maintenance
  • Establishing Long-term Ownership and Turning over the Final Deliverable
  • Measuring Results
  • Obtaining Final Approvals

PROJECT RESOURCES:

At minimum, list the Key Stakeholders, Budgets, and Timeframe, as well as, any other expectations regarding resources.

• Who are the KEY STAKEHOLDERS?
• Who is the CUSTOMER? Who is paying the bill? Who makes final decisions? Who provides me my authority and power to lead the project?
• What approvals will be needed to begin, execute, and complete the project and its phases?
• Who will be approving deliverables, and, which deliverables need to be approved?
• Who will be approving project changes?
• Who will be the escalation points throughout the project?
• How much time and money can be spent?
• What Special People, Tools, Skills, etc. will be Required?

RISKS AND ASSUMPTIONS:

At minimum, list the project priorities, as well as, anything that may impact/limit the project’s success.

• What are the Top 3 Risks?
• Are there any changes anticipated that could impact the project (workforce reductions, customer contracts, global holiday schedule, global communications, and global cultures)?
• Are there any environmental, political, ethical, or regulatory concerns?
• Are there any Key Stakeholders ‘against’ the successful completion of this project?
• Identify all related projects (Project Dependencies – should be prioritized)
• What projects will compete with this project?
• Which dependent projects can fail and not impact this project, or have a positive impact (more resources, sooner)? Which dependent projects will impact my project if they fail?
• Within the program/portfolio, what is the priority of this particular project?
• Prioritize the Constraints (Scope, Schedule, Budget, Quality, Risks, HR, etc.)

 

Down and Dirty Version:

EXEC SUMMARY:  Paint a clear picture of the project using 1-2 paragraphs, including a Problem and Answer statement.

PRODUCT OBJECTIVES:  Think of the project broken into its largest pieces.  Then, define what is to be delivered in 3-5 statements. Think SMART!

MEASURES OF SUCCESS:  When will the project team ‘know’ when the project is complete?  Is there a specific “Measuring Stick”, or “Litmus Test” you would suggest for this project?  Convey details about deliverables that must happen in order to say they’re complete.

PROJECT RESOURCES:  At minimum, list the Key Stakeholders, Budgets, and Timeframe, as well as, any other expectations regarding resources.

RISKS AND ASSUMPTIONS:  At minimum, list the project priorities, as well as, anything that may impact/limit the project’s success.

Advertisement