What is your most favorite project management document?
If you had to choose just one document to manage an entire project with (i.e. project charter, issues log, project schedule, etc.), which document would you choose and why? Saving Changes...
Kimberly FehringChief Quality Officer| Paycor Inc.Cincinnati, Oh, United States
Project Charter. Mini projects all the way to giant projects need to have one in place. Avoid issues down the road by defining the business problem/background, project statement, early identifiable risks, goals and objectives, stakeholders, team members and resources needed up front. Saving Changes...
Wai Mun KooPMO Director| Intergraph PP&MSingapore, Singapore
Agree with Kimberly. Project Charter, provides the basic info needed in most areas in the project. Saving Changes...
Yee-Kuan PangHead of PMO| An international company in the chemical industrySingapore, Singapore
From business' perspective - the business case; but from Project Management perspective - definitely the Project Charter Saving Changes...
Only project charter cant be used for managing the Project rather i will go with well crafted, updated and resourse loaded schedule as the only one document i may ask from the planner. Saving Changes...
Linda HillProgram Manager| MicrosoftRenton, Wa, United States
Project Charter, if written comprehensively is a great document. Another document to consider is a Project Plan that includes the charter, scope (in and out of), change management, issues, risks, etc. Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
I will agree with the previos posters. The Project Charter is indispensible.
As documents vary, I am assuming that the Project Charter provides the high-level scope as well as ROM budget and delivery date (though the last two are optional). Even with all of the other project documents, the Project Charter is a go to document when evaluating change requests, risk mitigation, project cost, and project schedule. It can also be the determing document when deciding whether to continue or terminate a project. Lastly, smaller efforts are often done with only the equivalent of the Project Charter - though usually disguised with a different term because the effort "isn't really a project."
A concise 1-2 page description of the project is crucial to the management of a project. Us mere mortals really can't understand anything much larger. A good Project Charter is the basis for a good project.
Saving Changes...
Linda HillProgram Manager| MicrosoftRenton, Wa, United States
As a gantthead member, I am aware that there are Project Charter templates available from this site. However I am wondering if anyone has an example that works especially well for them that they are willing to share? Saving Changes...
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
I clicked this discussion because I thought it was about my most favourite project management document. It's not the one I would choose to manage my project with, but my favourite document is the project closure report - always full of useful stuff for the future and normally evidence that the project has achieved what it set out to. Saving Changes...
Philip HindPM II| P R Hind Consulting LtdRayleigh, Essex, United Kingdom
Hmmm. As I am embarking on my first Agile project I would have to say Backlog! This should be all I need to know for the project yes? Saving Changes...
Vicki JamesFounder | Small Biz Advocate| Beyond Aligned Books | Thrive HiveValencia, Spain
