PROJECT MANAGEMENT SKILLS FOR LEADERS - DRAFT A PROJECT CHARTER:

In this article, you’ll find project charter examples for a real-life project. Then, we’ll discuss how to use it in the real world. In addition, you can get a simple project charter template I developed and used throughout 17 years managing different kind of projects successfully. Let’s review how it works.

What is a project charter?

A project charter is a document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

A project charter acts as a soft agreement between a project manager and project owners not to change the project timeline, scope, and budget without proper consideration and impact analysis.

This is to allow you to conduct project planning on a stable vision at the start of the project. After that, you’ll use the project charter to keep to the project scope and objectives.

One of the most effective tools in the project manager's toolbox that every leader should use, hands down, is the project charter. It's a document that outlines key expectations, and elements of the project, and it provides a sense of focus for everybody.

The truth is that when we engage in external agreements, there's almost always some sort of clearly documented contract, agreement, statement of work, something formal that outlines terms and conditions, and other expectations.

We need to apply that same concept, even if not the same level of detail, to internal projects as well. The goal, as always, is to minimize miscommunications, and ensure everyone is operating from the same sheet of music.

So what's typically in this project charter? While official project management methodology may reference a project charter as a formal document authorizing the work, for practical purposes, for most leaders, I like to also include some elements typically found in a team charter as well.

#. Project Charter Example from Real Project:

Project Title:

Image Library Service Site Update (codename: project “redesign”)

Description:

The last update of the?Image Library Service Site?was done three years ago. It is outdated in terms of appearance, performance, and user experience.

An investigation was conducted to develop performance requirements and a new vision of the UI.

The purpose of this project is to develop a new design and implement a brand-new site.

The new site deployment is not a part of this project. Due to its complexity, it will be done as a separate project.

Any updates or improvements to the database should not be performed unless needed.

#. Project Manager and Authority Level

Business Case:

All closest competitors have up-to-date, responsive, and fast websites. Customer satisfaction with our service has dropped to a level of severe attrition.

This project is called to update the Image Library Services site.

1. The new site should have good search and filtering capabilities.
2. UI should be clutter-free and focused on finding and previewing images in the library.
3. The site should be fast, responsive, and support key accessibility features.

We expect to regain our first position as an image content provider within a year after the new site is online.

Resources Preassigned:

Patricia Smith from the design team is already assigned to the project on a full-time basis. The Project Manager will identify and request any other internal resources.

Stakeholders:

Andrew Peterson represents the design team. Ray Jackson is from the customer support team. Lora James is from marketing.

They are available to support the project as needed.

Stakeholder Requirements as Known:

There are requirements for the new site’s performance and a description of a general vision of its design as attachments to this document.

In no way the new website should reduce existing functionality for users.

Product Description/Deliverable

• Full design of the new site as a storyboard
• Work breakdown structure
• Human resources plan
• List of project-related risks
• The new version of the site that is tested on lower environments and ready for deployment

Assumptions:

• No new hardware is required.
• No changes to the database are required.
• Internal resources are capable of finishing the project.

Constraints:

The new site should be ready for deployment by October 20.

The work breakdown structure ?should be provided by July 10.

A list of risks should be provided by July 25.

The final design should be ready and approved no later than August 20.

Measurable Project Objectives:

The objective of this project is to develop a site with the speed performance level stated in the requirements.

Attrition should be reduced to 3%.

Budget limits ?and deadlines are the next priority.

Release date: Due no later than October 20, 2016.

Summary budget: $100,000

Project Approval Requirements:

The head of the Design Department should approve the final UI designs.

Sponsors should approve the work breakdown structure.

PMO Manager should review and approve the list of risks.

High-Level Project Risks:

We have little experience in improving and measuring customer satisfaction. It is possible that the new site will not meet end-users expectations. Therefore, our goals may not be reached.

Due to customer attrition, project delays may cause serious customer losses.

Project Sponsors Authorizing This Project:

______________________ John Snow, Vice President

What Project Charter Template Should I Use?

How to Create a Useful Project Charter:

Step #1:?Check who is responsible for creating the project charter. Is it mandatory?

Step #2:?Check if there is a project charter template in your organization. Ask your manager and peer colleagues. If there’s no project charter template – create one.

Step #3:?Talk to the project sponsor, client, customer, and?key stakeholders . Collect information about the business case, high-level requirements, constraints, assumptions, project success criteria, and risks.

Step #4:?Understand the project objective and how it is aligned with the business case.

Step #5:?Try to identify real expectations from the project.

Step #6:?Write a project charter draft.

Step #7:?Consult with subject matter experts, review historical data, and look for similar projects.

Step #8:?Update the draft if needed with risks and assumptions from other projects.

Step #9:?Meet with preassigned project team members and get their input.

Step #10:?Update the draft if needed.

Step #11:?Plan a meeting with project stakeholders.

Step #12:?Update the draft and finalize the project charter.

Step #13:?Get the sign-off.

• For sure, the process may differ. Some steps might not be formal or mandatory.

?