Uqba Khan Niazi Assignment 01 1767134
Project Charter
Project Title and Description: Project Title is a name of the Project. A proper project title
describes the whole assignment in one or few sentences. It helps the project team to refer the Project
with the assigned Name. Project title makes an understanding about the main goal of the Project work
and its deliverables.
Project Manager Assigned and Authority Level : This section defines who will be the
responsible project manager assigned to the project. It also helps to make an understanding about what
are the authorities given to the PM and to what level the PM will be held accountable.
Business Case: It defines the reason of doing a project. It also define the needs of the project. The
business case is the key section of the project charter. It is both the justification for the activities and a
benchmark by which the project benefits will be measured. The purpose of the business case is to
document the justification for the undertaking of a project usually based on the estimated cost of
development and implementation against the risks and the anticipated business benefits and savings to
be gained.
Resource Pre-assigned: All the primary resources that will work in the project or in the phases
of the project are described in this section of the project charter. It also defines the number of people
working in the project. Also, the persons taking care their specific domain of the project are defined in it.
Stakeholders and stakeholder Requirement: A stakeholder is a person who has a few
to high level influence in the project. The person that can be directly or indirectly affected by the
project. Stakeholder analysis is done in this section and the list of stakeholder is prepared along with
their level of influence in the project. A key stakeholder can be a project sponsor, senior management or
any consultant.
Product Description / Deliverables: The product or project description gives a clear and
correct understanding of the project in minds of the people and organizations involved in the planning
and development process. The project team uses this to get a general idea of what amount of work and
under what requirements is planned for completion. The senior management team regards the project
description as the key source of preliminary information necessary for strategic planning and
development.
Assumptions: Assumptions are what is believed to be true. In this sections cover the anticipated
events or circumstances that are expected during your project’s life cycle. The assumptions based on the
basis of experience or the information available on hand. Assumptions may not end up being true.
Sometimes, they can be false and it may affect the project. This adds risk to the project.
Uqba Khan Niazi Assignment 01 1767134
Constraints: These are the factors that limit the project team’s options. It defines the boundaries
and limitation in which the project will be performed. Constraints that may occur during the course of
project are document in this section. They mainly revolve around the scope, schedule and cost of the
project.
Measurable Project Objectives: Project objectives are goals that a team or an organization
wants to achieve. Identify what benefit an organization can get from the project. These are the business
objectives that you want the project to accomplish. Within project management, it is of utmost
importance that a project's objectives are stated clearly as these will impact every decision in the project
lifecycle. Project objectives must be measurable and contain key performance indicators that will be
used to assess a project's success. These indicators will often encompass areas such as budget, quality,
and time to completion.
Project Approval Requirements: Most projects require approval from external authorities
and from internal authorities as well. Those approvals which will have a major impact on the project can
be explicitly stated within the project charter. For example, in the mine building project, the
government approval for mine construction is so integral to the project that it could be mentioned in
the project charter. However, the project charter is not the place for a comprehensive list of approval
requirement.
High Level Risks: Most projects have one or two major risks that define the project. For example
a structural failure for a bridge overpass project, or website payment software that contains security
glitches. These are the risks that are fundamental to the project’s success and are generally thought
about before the project becomes a project. Therefore, they should be included within the project
charter, but they should not take the place of a project risk analysis within the project management
plan.
Project Sponsor: The project sponsor is one level above the project manager, often an
organization contact for the project. They should be named and their responsibilities in regard to the
project made clear.