Jeff GruettertDirector of Operations| 3BG Supply Co.Fort Wayne, In, United States
I am having a bit of an issue here; on one hand, I would like to create a project charter for all my small projects but am having an issue justifying the time put in to developing a PC if the project is small in scope (take a small process automation improvement for example). I receive written/verbal approval for all my projects.
Anyone have words of advice? I understand the importance, but working for a small company has its challenges with balancing resources and capacity. Saving Changes...
Helen McCulleyAssociate Director Project Management| Covis PharmaZug, Switzerland
Consider selling this to your organisation in a different manner by maybe documenting the information you feel you would want to include in a charter in a presentation instead. This way the information is still communicated and agreed but potentially in a format that may better suit the organisation. Sometimes utilising words like 'Charter' can sound like bureaucracy to some stakeholders and so it may need repackaging to suit. Saving Changes...
Mark EckmanSenior Project Manager, PMP| VeoliaEmporia, Va, United States
Jeff,
I agree with all of our colleagues that having a Project Charter is a must, (even on the small projects). Lori already hit on my company's answer, we use a scaled down version for smaller projects as well.
Mikel has offered a template of what he uses and I will also be glad to share the template(s) that I use . Saving Changes...
Abdul AbbasiIT Project Manager - PMP, CSMToronto, Ontario, Canada
Always create a project of all projects you work. If the project fails or major scope change occurs, the sponsor or other stakeholders will always request to see the project charter. Saving Changes...
Saji VargheseSaji Varghese PMP| Virtusa (Formarly Polaris Consulting and services Ltd.)Thane, Maharashtra, India
Use your PMIS, Generally there will be an SOW in case of small projects, in the PMIS, create project and project code, enter the details, fill the template and attach the SOW. In short for the smaller project the client generally sin the SOW. the project created in the PMIS can be treated as PC Saving Changes...
Mikel SteadmanPMO Leader| Development Dimensions InternationalTroy, Nh, United States
Aug 17, 2017 5:35 PM
Replying to LORI WILSON
...
Hi Jeff - this is normal for the large corporation I work in as well as for smaller organizations. When this is the scenario, we use what is called a Project Charter - Lite. We also have a Business Case - Lite that we use. Much smaller documents, a better fit and the best use of our time as PM's. All the advice from my peers so far on this is great! Sounds like Mikel has a template to share!
Yes. I am willing to share. Connect with me on LinkedIN and give me a good email, and I will send along what I use. It's not spectacular, but it's lean and effective for me and my projects.
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
I agree with Tom & Mikel. Its important to have a PC approved by Management. Remember "When things are going well, no one will question" and opposite is a reality. Saving Changes...
Welcome to the onset of agile thinking. Agile processes only do as much documentation as necessary, and smaller projects need substantially less documentation than larger ones. Saving Changes...
Jeff:
Many great comments here; the beauty of a project charter is that it clearly identifies the scope of your work and can be documented along with your email approval.. I'd use a one page project charter including schedule/comm plan, issue and risk log. Keep it simple; document what is necessary and required. Saving Changes...
Braden KelleyHuman-Centered Design, Innovation, Change and Transformation Leader| Best Selling Author and Keynote SpeakerIssaquah, Wa, United States
Get your pens and sticky notes ready...
Anyone and everyone can get a free Visual Project Charterâ„¢ here:
Think of the project charter as the contract. It doesn't have to be complicated or long. It just sets the agreement between the client and the provider.
In fact, you want to make your project charter as generic and general as possible. Leave the details for other artefacts that can be more easily changed. Saving Changes...