Why create a charter it seems just like busy work? I mean the boss wants this done NOW why waste the time on creating a charter? Good questions, but I can guarantee you a charter is NOT a waste of your time, nor the bosses time either. Do you remember the school yard game where you would line up and tell the person next to you something and have them pass it on. What was said at the end of the line? Was it ever the same thing? I’d say NO. Why is that? Because as much as we think we state things clearly the receiver never gets it exactly like what we said. I see this all the time in training and working in teams. We are such a diverse group of people that our individual picture of what is said gets mixed with what we know and that changes the thought.
So we write a charter to capture the “true” reason we are doing the project. It is the best way to capture and pass on what you are doing. With out it your team may get lost very quickly as the direct at the beginning is slightly different in everyone’s mind.
The charter is more than a simple statement of the project objective. It hold a lot of information so everyone gets the same “picture” of what we are doing. Some things in a charter may seem redundant but they are not. They are stating the approach to the issue in a slightly different way so other will get the complete picture of what is happening. You will find that you will come back to the charter time and again to bring the team back on task for what they were brought together to accomplish. So lets look at what should be in your charter.
The Header Block
- Project Name or Title
- Who will be the project Lead and their phone number
- Who will be the project Sponsor and their phone number
Note: A sponsor is ALWAYS needed. The Sponsor will be the manager that the project will impact and help the most . The Sponsor will also help remove road blocks as the team encounters them. Last the Sponsor will be the main conduit to top management that will need to support this project as well.
- The Project Start and Target End Date. Management will not support a project that we do not have some time frame to complete.
The Problem Statement – Here we need to describe the problem as briefly as we can but with enough detail that everyone understands it. Plus here we need to include a business case statement. This statement is what ties this problem to the company goals and objective and defines why we need to do it NOW. In other words it is the “burning platform or need” to do it now.
A Vision Statement – Many call this the objective but I like to call this a vision of the future state of the process. Many times this makes it easier for others to “picture” what it will look like when the project is complete.
The Metrics – This may seem hard to define right now but believe me when I say management when they saw this problem it was not a touchy feely thing it had hard number associated to it. Numbers they want to see changes in. It could be dollars, volume, time, or number of customers but there are numbers that are the metrics YOU need to improve. Sometimes even management does not quite know what they are but it is your job to ask why they think they see this as an issue and find the metric!
The Benefits – Now we take the metrics and align them to stakeholder benefits. Stakeholders are Customers, Stockholders, and Employees. So here we take the metrics and show how they impact our stakeholders.
Deliverables – Here is one a lot of folks miss but don’t you be one of them. This will define when you know the project is done. These will be the results of the project. They can be minimum changes in the metrics with stretch goals included. But everyone needs to know not only the date the project will be complete but also what will result from it. Yes, it is hard to know the exact solution at the start of a project but you can set some reasonable goals to accomplish. It does seem scary but in the end you will find that you had been very conservative with these.
Scope of the Project – The best way I can describe this is when looking at the process you are trying to improve. What steps of that process will be looked at in this project. This will help you keep the project focus and not have what I call scope creep due to not know what areas of the company this project will cover. It also should be noted that you need to make sure the scope is not to big ( you can not solve world hungry, you may be able to only solve hungry in your neighborhood).
Project Team – list here the member of the project team, what roles they will play and how you can contact them (phone).
DMAIC Est. Completion Times – I know you have the project Start and estimated completion dates above, but you will need an estimated completion time for each of the five step of DMAIC. These will be milestones to you and management on how well the project is moving. It is better to make adjustment as you go then to find you are way behind and over budget near the end of the project.
Well there you have the basic components of a six sigma project charter. At least from my prospective. If you have questions or comments please feel free to leave them below or you can contact me on my website.
Bersbach Consulting
Peter Bersbach
Six Sigma Master Black Belt
http://sixsigmatrainingconsulting.com
peter@bersbach.com
1.520.829.0090
