VERSION CONTROL

Version Made by reviewed by Approved by Date Reason

Project Charter
PROJECT NAME CODE

CONCEPTS ASSOCIATED WITH THE FORMAT

DEVELOP PROJECT CHARTER: THE PROCESS OF DEVELOPING A DOCUMENT THAT FORMALLY AUTHORIZES THE
EXISTENCE OF A PROJECT AND GIVES THE PROJECT MANAGER THE AUTHORITY TO ALLOCATE ORGANIZATIONAL
RESOURCES TO PROJECT ACTIVITIES. THE KEY BENEFIT OF THIS PROCESS IS A WELL-DEFINED PROJECT
INITIATION AND BOUNDARY, THE CREATION OF A FORMAL PROJECT RECORD, AND THE ESTABLISHMENT OF A
DIRECT WAY FOR TOP MANAGEMENT TO FORMALLY ACCEPT AND COMMIT TO THE PROJECT.
PROJECT CHARTER: A DOCUMENT ISSUED BY THE PROJECT INITIATOR OR SPONSOR THAT FORMALLY
AUTHORIZES THE EXISTENCE OF A PROJECT AND GIVES THE PROJECT MANAGER THE AUTHORITY TO ALLOCATE THE
ORGANIZATION'S RESOURCES TO PROJECT ACTIVITIES. IT DOCUMENTS THE BUSINESS NEEDS, ASSUMPTIONS,
CONSTRAINTS, UNDERSTANDING OF HIGH-LEVEL CUSTOMER NEEDS AND REQUIREMENTS, AND THE NEW PRODUCT,
SERVICE, OR RESULT THE PROJECT IS TO PROVIDE.

PROJECT DESCRIPTION: DESCRIBE THE PURPOSE OF THE PROJECT, WHO ARE THE PEOPLE INVOLVED, HOW
THE PROJECT OBJECTIVES WILL BE ACHIEVED, THE ESTABLISHED START AND END TIME OF THE PROJECT, AND THE
PLACE WHERE THE PROJECT WILL BE CARRIED OUT. (WHAT, WHO, HOW, WHEN AND WHERE)

DEFINITION OF THE PROJECT PRODUCT: DEFINE IN DETAIL THE PRODUCT, SERVICE OR CAPACITY TO BE
GENERATED, AS WELL AS ALL THE DELIVERABLES REQUESTED BY THE CLIENT.

DEFINITION OF PROJECT REQUIREMENTS: {REQUIREMENT: CONDITION OR CAPABILITY THAT MUST BE

PRESENT IN A PRODUCT, SERVICE OR RESULT TO SATISFY A CONTRACT OR OTHER FORMALLY IMPOSED
SPECIFICATION}. DESCRIBE THE FUNCTIONAL, NON-FUNCTIONAL, QUALITY REQUIREMENTS, ETC., OF THE
PROJECT.

PROJECT OBJECTIVES: DESCRIBE THE GOALS TOWARDS WHICH THE WORK OF THE PROJECT MUST BE
DIRECTED IN TERMS OF THE TRIPLE CONSTRAINT, DEFINING THE MEASURABLE OBJECTIVES OF THE PROJECT AND
THE ASSOCIATED SUCCESS CRITERIA.
CONCEPT OBJECTIVES SUCCESS CRITERIA
1 REACH
2. TIME
3. COST
PROJECT PURPOSE: DESCRIBE THE ULTIMATE GOAL, GENERAL PURPOSE, OR HIGHER LEVEL OBJECTIVE FOR
WHICH THE PROJECT IS EXECUTED, MENTIONING THE LINK WITH PROGRAMS, PORTFOLIOS, OR STRATEGIES OF THE
ORGANIZATION.

PROJECT JUSTIFICATION: DESCRIBE THE QUALITATIVE AND QUANTITATIVE REASONS WHY IT IS NECESSARY
TO CARRY OUT THE PROJECT, SPECIFYING THE BENEFITS TO BE ACHIEVED.
QUALITATIVE JUSTIFICATION QUANTITATIVE JUSTIFICATION
Income Stream
Expense Flow
GO
IRR
RBC

DESIGNATION OF THE PROJECT DIRECTOR: {PROJECT DIRECTOR: PERSON APPOINTED BY THE

PERFORMING ORGANIZATION TO LEAD THE TEAM THAT IS RESPONSIBLE FOR ACHIEVING THE PROJECT
OBJECTIVES}. WRITE THE NAME OF THE ASSIGNED PROJECT MANAGER, HIS/HER RESPONSIBILITY AND LEVEL OF
AUTHORITY.
NAME AUTHORITY LEVELS
REPORT TO
SUPERVISES

PROJECT MILESTONE SCHEDULE: {MILESTONE: SIGNIFICANT POINT OR EVENT WITHIN A PROJECT,

PROGRAM, OR PORTFOLIO}. MENTION ALL THE MILESTONES CHRONOLOGICALLY, PLACING THEIR SCHEDULED
START AND END DATES.
MILESTONE OR SIGNIFICANT EVENT SCHEDULED DATE

STAKEHOLDERS INVOLVED IN THE PROJECT . IN THIS SECTION, ALL THE INTEREST GROUPS OR PERSON
WITHIN THE PROJECT ARE NAMED, AS WELL AS THE ROLE THAT EACH OF THEM PLAYS.
NAME COMPANY ROLE PLAY EMAIL PHONE NUMBER

MAIN THREATS OF THE PROJECT: {THREAT: RISK THAT WOULD HAVE A NEGATIVE EFFECT ON ONE OR
MORE OBJECTIVES OF THE PROJECT}. THE NEGATIVE RISKS THAT CAN AFFECT THE OBJECTIVES OF THE PROJECT
MUST BE ENTERED. A NEGATIVE PROJECT RISK THAT HAS MATERIALIZED IS CONSIDERED A PROBLEM.

. 2
MAIN OPPORTUNITIES OF THE PROJECT: {OPPORTUNITY: RISK THAT WOULD HAVE A POSITIVE EFFECT
ON ONE OR MORE OBJECTIVES OF THE PROJECT}. POSITIVE RISKS THAT CAN GENERATE GREATER VALUE IN THE
PROJECT MUST BE ENTERED.

ASSUMPTIONS: {ASSUMPTION: FACTOR OF THE PLANNING PROCESS THAT IS CONSIDERED TRUE, REAL OR
CERTAIN, WITHOUT PROOF OR DEMONSTRATION}. DESCRIBE THE FACTORS THAT FOR PROJECT PLANNING
PURPOSES ARE CONSIDERED TRUE, REAL, OR CERTAIN.

RESTRICTIONS: {RESTRICTION: LIMITING FACTOR THAT AFFECTS THE EXECUTION OF A PROJECT, PROGRAM,
PORTFOLIO OR PROCESS}. DESCRIBE THE FACTORS THAT LIMIT THE PERFORMANCE OF THE PROJECT, THE
PERFORMANCE OF A PROJECT PROCESS, OR THE PROJECT PLANNING OPTIONS, MAY APPLY TO THE PROJECT
OBJECTIVES OR TO THE RESOURCES THAT ARE USED IN THE PROJECT.

INTERESTED LIST : {INTERESTED OR STAKEHOLDER: INDIVIDUAL, GROUP OR ORGANIZATION THAT CAN

AFFECT, BE AFFECTED OR PERCEIVE HIMSELF AS POSSIBLY AFFECTED BY A DECISION, ACTIVITY OR RESULT OF A
PROJECT}. THIS SECTION MENTIONS ALL INTERNAL AND/OR EXTERNAL STAKEHOLDERS INVOLVED IN THE
PROJECT, AS WELL AS THEIR ROLES.

PROJECT APPROVAL REQUIREMENTS: DESCRIBE WHAT CONSTITUTES PROJECT SUCCESS, WHO DECIDES
IF THE PROJECT IS SUCCESSFUL, AND WHO SIGNS THE PROJECT APPROVAL.

PRELIMINARY PROJECT BUDGET: TENTATIVELY MENTIONS ALL EXPENSE ITEMS, THEIR RESPECTIVE
COSTS, THE CUMULATIVE TOTAL OF THE BASELINE AND THE TOTAL BUDGET THAT INCLUDES CONTINGENCY AND
MANAGEMENT RESERVES.
CONCEPT AMOUNT

AUTHORIZING PROJECT SPONSOR: {SPONSOR: A PERSON OR GROUP THAT PROVIDES RESOURCES AND
SUPPORT FOR THE PROJECT, PROGRAM, OR PORTFOLIO AND IS RESPONSIBLE FOR FACILITATING ITS SUCCESS.}
THIS SECTION MENTIONS THE PROJECT SPONSOR, AS WELL AS THE ENTITY TO THE ONE TO WHICH IT BELONGS,
THE POSITION IT OCCUPIES AND THE DATE OF PREPARATION OF THE PROJECT'S CHARTER.
NAME BUSINESS POSITION DATE
. 3
. 4