Formal chartering may be the step most frequently overlooked by organizations when beginning projects. Root cause analysis of project failures often identifies “poor vision” or “lack of a charter” as a key reason projects go awry or are cancelled.
Knowing this, why is developing a good project charter apparently so difficult? It is certainly not due to any complex technical reason, like not being able to find a word processor advanced enough to document the information. There are a few reasons so many projects have ineffective charters.
Business managers that sponsor projects are not experts in project management. The care and nurturing of projects are merely a fraction of their job duties. Business managers simply need results. Many times they feel their responsibilities are complete if they simply identify the problem to someone (like a project manager) that is assigned to correct it. If it is the role of the project sponsor to create the charter, they may need some training or assistance in order to develop a charter that serves as a foundation for future project work.
It is often not clear which role in an organization is responsible for developing a charter. Since the business manager has clearly identified the problem to someone assigned to help (the PM again), they will often revert back to other duties, leaving the task to the PM. The 5% rule now comes into play: If a single task is assigned to 2 people equally, each will take 5% ownership of its completion. It should be clearly documented in an organizations project methodology which role is responsible for developing the charter.
If it is clearly the responsibility of the project manager, project charters are often only developed half-heartedly, leading to unclear vision from the beginning of the effort. Many times the project manager has not been a party to the business discussions leading to the birth of the project. Once assigned, it is often seen as a sign of weakness for a PM to go back over territory already covered. What PM wants to acquire the reputation of not being able to jump in with both feet and get the project moving? Revisiting lofty ideas such as business objectives, goals, and critical success factors can come across as being excessively process-oriented and not focused on achieving results. As a result, many PM’s will move forward with the uneasy feeling that they are missing something.
As a project manager, what is your role and responsibility when it comes to chartering projects? Well, since you probably do not control the funds needed to sponsor a project, it is unlikely that you will have the gravitas (my favorite word from a previous election cycle) to charter them yourself. Basically, it comes down to this.
The business managers will often put together an unsuitable charter. However, this does not mean that you should accept this shortcoming and move forward anyway. Remember, you are ultimately responsible for the success of the project, so it is in your best interest—in fact your responsibility, especially if you are a PMP—to insure an appropriate charter is in place before investing additional effort/hours/cost.
Here are some items you should make certain are addressed through whatever chartering process your organization employs. If your company doesn’t even recognize the concept of chartering, you may need to introduce these concepts a little at a time and walk them through the process without using any official sounding terms like charter, mission statement or vision document.
Read more at ProjectConnections.