The project charter is an important document to formalize the initiation of any project conducted in a professional way. This document establishes a common understanding between the parts (stakeholders), especially the sponsors and the executors, being the basis for a formal contract that will financially enable the project development.
Beyond a high-level
estimation of duration and costs, these documents need to bring some more
information that makes the project goals and conditions of its execution clear,
in a way its feasibility becomes tangible for both parts.
Here is
important information Project Charter needs to present:
Justification
Explain the
reason for this project should be executed. What is the problem to be solved?
Objectives
What are
the benefits to business? What is going to be improved from the current
scenario?
Expected Results 🧭
What are
the main deliverables from this project? Include partial deliverable that may
be tangible.
Premises
What is the
expected situation to initiate the project execution? What is expected to be
available on the first day of the project in order to initiate its activities?
Restrictions 🚫
There are
constraints which reduce the choice of possibilities for the project or product
action plans?
Criteria for success 🗹
When the
project ends, what can be observed to infer the project was delivered and
matching the expected quality?
Milestones 🚩
Checkpoints
or markers within a project's timeline that indicate the completion of a major
phase or the achievement of a key objective. Here you don’t need to know
exactly when they are going to happen but identify what they are.
Using dotProject (www.dotproject.cloud) you may elaborate the Project Charter following the best practices guidelines.

Comments
Post a Comment