Project Charter Template

This Project Charter Template is free for you to copy and use. Please feel free to provide
comments and feedback to help us improve this template for future users. This template is to be
distributed only through the PM Documents web site (http://www.pmdocuments.com)

Project Charter
[Project Name]

Date

[Company Name]
Address
City, State Zip
Contents
1. Project Description..........................................................................................................................3
2. Project Purpose...............................................................................................................................3
3. Business Case...................................................................................................................................3
4. Business Requirements....................................................................................................................3
5. Assumptions....................................................................................................................................3
6. Constraints.......................................................................................................................................3
7. Risks.................................................................................................................................................3
8. Project Deliverables.........................................................................................................................4
9. Project Milestones...........................................................................................................................4
10. Project Manager..........................................................................................................................4
11. Project Roles and Responsibilities...............................................................................................4
12. Project Life Cycle Methodology and Tools...................................................................................5
13. Authorization...............................................................................................................................5

Note: Select all (ctrl + A) and hit the "F9" key to update all document references and the table of
contents
 Project Charter Template
http://www.pmdocuments.com

1. Project Description
Explain what the project is, and how it will be accomplished. Explain the ultimate intended outcome of
the project. This should serve as a brief introduction. Provide some background about the history of how
the project got to this point.

Comercializar cacao criollo de primera calidad de origen, promoviendo y vendiendo cacao de la

región a clientes internos que comercialicen con procesadoras internacionales.

2. Project Purpose
State the purpose of the project. Tie the purpose to the organization's strategic goals and objectives if
possible. Tell the reader why this project is being started and what need it is fulfilling. Identify if there
are any specific mandates, policies or laws that are driving this change.

Recibir la entrega del producto y almacenarlo en las bodegas en la region del Tolima.

3. Business Case
Provide information on how the project going to benefit the organization. Discuss the alternatives that
were considered, if any, and provide information on how the organization came to the selected approach.

Mejorar el funcionamiento de la cadena de suministro de los proveedores de la región,

garantizando la participación de cultivadores, reduciendo al mismo tiempo el comercio y los
riesgos del precio.

4. Business Requirements
Identify the high level business requirements that the project is going to fulfill. Remember that this is not
a detailed list of system requirements.

El cacao se va a comprar directamente al productor y a través de cooperativas asociadas en

convenio con asociaciones de productores de cacao el Huila y Tolima. La venta de cacao se va
realizar directamente al exportador o comprador internacional. Por lo que se necesita de un (1)
almacen, con capacidad de XXXX sacos de cacao, con aproximadamente un area de XXXX mts
cuadrados , el almacen debe tener piso de cemento sin grietas para que los insectos no se alojen, el
nivel del piso debe ser más alto que el suelo para evitar inundaciones y también para que el agua
fluya con mayor facilidad. Es importante mencionar que el cacao es un comodity considerado un
producto de lujo por que no es indispensable, ni es de primera necesidad en la alimentación por
consiguiente se establece participar del mercado de futuros en la bolsa nacional agropecuaria para
tener un mayor control en el cambio de precios.

3
 Project Charter Template
http://www.pmdocuments.com
5. Assumptions
Assumptions are conditions at the start of the project that must be considered. For example, when
developing the new software system that is going to take 3 years to fully complete, an assumption could
be that the project budget is approved each year for three years so that the project scope is not impacted.

Supuestos.

 Mantener las condiciones climaticas en condiciones normales.

 El remplazo de cultivos de coca por cultivos de cacao en el proceso del posconflicto
 El exceso de oferta en el mercado
 Tecnificación y tecnología de cultivos
 El marketing eficaz y sofisticado del producto terminado
 Globalización cultural
 Crecimiento de ventas totales para china
 El apoyo por incentivar la productividad por parte de Fedecacao y Corpoica
 Oportunidades nuevas de negocios con Italia, Suiza, Belgica y Francia y mejorar y
aumentar acuerdos con socios comerciales España, Holanda y Alemania

6. Constraints
Constraints are situations or events on the ground that must be considered and accounted, for which the
project has no control over. For example, a constraint can be a hard deadline or completion date. Other
constraints could be resources, tools or hardware -- so that if the project has no budget for additional
servers, then the project must find a way to develop the new system using the hardware already in place.
This could mean juggling servers to fit specific development environment needs while ensuring that the
production environment stays up.

Restricciones: En cuanto a nuestra situación de negocio, una situación que se nos puede presentar
es la de un “paro”, podríamos resultar afectados directamente por este evento.

7. Risks
State the known risks. These risks are generally at a high level since not much is known about the details
of the project yet. If a Benefit-Cost Analysis was performed, then risks identified during the Benefit Cost
Analysis should be placed here. For example, if the project is going to span 5 years and touch multiple
third party systems, then integration and technology change would be risks to consider here. For
examples on how to write a risk statement, visit http://www.pmdocuments.com/category/risk-
management/

Riesgos: Como un posible riesgo tenemos que tener un plan B, en el caso que se cierre un acuerdo y/o
tratado internacional con algunos de los países destino a exportar, donde se derivan contratos
bastante importante para la ejecución y crecimiento del producto, por ende nuestra rentabilidad.

Adicionalmente un cambio climático, donde nos pueda retrasar en la cadena de producción y puesta
en marcha de negociaciones presentes y a futuro.

4
 Project Charter Template
http://www.pmdocuments.com

8. Project Deliverables
Document what is going to be delivered at the completion of the project.

Entregable: Al finalizar nuestro proyecto, ejecutaremos entrega física bajo ducumento de estudio
de nuestro plan de negocio. Desglosando el ¿Cómo?, ¿Dónde?, ¿Cuándo?, así como los recursos
necesarios para la puesta en marcha del negocio, el cual nuestro accionista principal nos requirió
desde el comienzo de nuestro proyecto.

9. Project Milestones
Identify the project milestones.

Milestone Date Milestone Name Milestone Description

[Jan 1] System Requirements System requirements version 1.0 are approved and
Complete baselined so that the project can begin design and
development.
[June 1] Development Complet Software development is complete and ready for
integration testing
[Dec 1] Deployed to Production System passes integration and end-user acceptance
testing and is deployed to production

10. Project Manager

Identify the project manager here. It is important to clearly identify the project manager so that the
project manager has the authority to complete the project. Provide a quick professionaly biography if
available. Explain as clearly as possible, the roles and responsibilities of the project manager. Explain
the project manager's levels of authority with respect to resource allocation, schedule modifications and
purchasing authority. Review the nine knowledge areas of the Project Management Body of Knowledge
(PMBOK) and think about the role that the project manager will fill in each of the areas.

11. Project Roles and Responsibilities

Define the other key roles and responsibilities within the project team. For example, if the project team
has functional team leads, then document them here. The table below provides a quick way to identify
specific people within a role:

Name Role Responsibilities

Jane Smith Risk Management Lead the risk management team to ensure risk
Team Lead identification, analysis and mitigation.
John Smith Testing Lead  Plan and complete testing in all stages of testing.

5
 Project Charter Template
http://www.pmdocuments.com
 Maintain traceability to requirements to ensure
that all requirements are tested.
 Responsible for testing tools

12. Project Life Cycle Methodology and Tools

Identify what project management methodology the project will be using. In many instances,
organizations have their own proprietary version of a waterfall-type life cycle. They may also have their
own preferred tools for managing the project management assets (e.g., DOORS for managing
requirements; SharePoint for document management and versioning; Other risk management and testing
tools etc.).

13. Authorization
Provide the names of those business sponsors that must sign the Project Charter. Once the project Charter
is signed by the project sponsors, the project is authorized to start.

Approved by the Project Sponsor:

___________________________________________ Date:____________________
[Project Sponsor]

[Project Sponsor Title], [Project Sponsor Organization or Division]

Note: Add other signatories as needed