Basic Project Charter

Home  >  Deliverables  > 

Basic Project Charter

( Example )

become a premium member to DOWNLOAD THIS NOW
gantthead premium membership the power of gantthead's extensive content library at your fingertips
Already a premium member? Login here learn about membership options 






Format:

This Project Charter walkthrough covers fundamentals, such as:

  • scope
  • general and specific objectives
  • defining constraints and assumptions
  • project organization
  • sponsor
  • project manager(s)
  • user representatives
  • technical lead
  • as well as approaches to staffing, budget, communications, planning, tracking, change control, system and document access, project plans and support requirements.

What will I get out of this?
This example will give you a basic, solid, structure for building a Project Charter. The sample text will give you a jump start on how to articulate each point in a clear and concise way.

Users who downloaded this template also downloaded . . .
Project Plan/Project Definition  ( Plan - Template)
Methodology Implementation Project Charter  ( Plan - Example)
Communication Plan  ( Plan - Example)

Alexander Finger
Menthonnex-en-Bornes, France
Posted: Jun 3, 2009 7:15 AM

"The Charter example is too vague and features too many items: The list of objectives gives examples of things, but not objectives. "Reporting" is a thing to do, but no objective, for example. My expectation towards a project charter is to tell me in a one-pager who will do what when, how and at which price, whereas the what can be rough - the charter is not there to judge the project but to give direction and facilitate portfolio management."



sponsored announcements and special offers
You can do this!
Earn your master's degree in project management without putting your life on hold at GoUWP.com!
Apply today at GoUWP.com for 100% online courses, 45 PDUs each. No entrance exam. University of Wisconsin- Platteville’s MS in Project Management is globally accredited by PMI. Combine academics and real-world scenarios for a 360-degree education.
If you have a distributed team, what are you trying to achieve with Agile approaches? Isn't Agile more for co-located teams? There are eight key benefits to working in a distributed Agile environment. A new report from ProjectsAtWork looks at each of those benefits – and how you can achieve them.
Most business and IT executives agree that any company able to rapidly deliver software of high and predictable quality with minimum budgets enjoys a significant advantage. However, practical experience shows that the challenges associated with software quality remain largely unsolved. Download the white paper Uplift Quality with Requirements Driven Testing to learn fundamental principles of Requirements Driven Testing.



"Creative minds have always been known to survive any kind of bad training."
- Anna Freud