This project charter outlines the goals, deliverables, scope, milestones, assumptions, and organizational structure for a new project. The project aims to address an identified business need or opportunity. Key deliverables that must be completed are listed at a high level. The scope section defines what work will and will not be included. Important milestones and assumptions that could impact the project are also documented. The project team members and their roles are identified. Finally, senior management authorization of the charter is required.
This project charter outlines the goals, deliverables, scope, milestones, assumptions, and organizational structure for a new project. The project aims to address an identified business need or opportunity. Key deliverables that must be completed are listed at a high level. The scope section defines what work will and will not be included. Important milestones and assumptions that could impact the project are also documented. The project team members and their roles are identified. Finally, senior management authorization of the charter is required.
This project charter outlines the goals, deliverables, scope, milestones, assumptions, and organizational structure for a new project. The project aims to address an identified business need or opportunity. Key deliverables that must be completed are listed at a high level. The scope section defines what work will and will not be included. Important milestones and assumptions that could impact the project are also documented. The project team members and their roles are identified. Finally, senior management authorization of the charter is required.
This project charter outlines the goals, deliverables, scope, milestones, assumptions, and organizational structure for a new project. The project aims to address an identified business need or opportunity. Key deliverables that must be completed are listed at a high level. The scope section defines what work will and will not be included. Important milestones and assumptions that could impact the project are also documented. The project team members and their roles are identified. Finally, senior management authorization of the charter is required.
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt
You are on page 1of 3
PROJECT CHARTER
Project Name: Project Number:
Date: Revision Number: 1. PROJECT GOALS Describe the business need, opportunity or problem that the project was undertaken to address i.e., the project justification. 2. DELIVERABLES Provide a high level list of what needs to be done in order to reach the goals of the project. ach deliverable should be sufficiently detailed so that the Project !eam will understand what needs to be accomplished. Describe the deliverable using action words "verbs# such as deliver, provide, create, research, etc. Deliverables should be measurable, so the Project $ponsor and !eam can determine whether the deliverable has been successfully completed at the project%s conclusion. 3. SCOPE DEFINITION Document the scope of work to be delivered. !o assist you in defining scope, use documentation such as &'P%, sales proposals, business re(uirements, functional specifications, etc. to set and limit the scope. )n $cope is what the project will include to meet the re(uirements of the Project goals. *ut of $cope e+cludes responsibilities, activities, deliverables or other areas that are not part of the Project. !he project will include, !he project will not include: For Internal Use Only Page 1 4. PROJECT MILESTONES )dentify the significant project milestones, including invoicing dates to the client. 5. ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES )dentify the assumptions that were made to form the basis of defining scope. -lso identify any assumptions that will be made for the purposes of planning the project. !he objective here is to set the boundaries and address how the triple project management constraint "scope, time and cost# are potentially impacted.managed. /ist any constraints "potential factors that will impact the delivery or make it difficult to manage the project# on the project or dependencies on resources or funding to the project. 0onsider time, cost, dates and regulatory issues as constraints or dependencies to the project. 6. RELATED DOCUMENTS &eference any related documents that were used to define scope and assumptions e.g., &'1, &'P, $ales Proposal, etc. Important to attach the following as a minimum ; 1. project plan indicating the tasks and who will do what by when. 2. Change management forms. 7. PROJECT ORGANIZATIONAL STRUCTURE )dentify the key stakeholders and team members by function, name and role. Function Name Role and responsibilities . PROJECT AUT!ORIZATION Approved by: Business Manager Date Approved by: Project Manager Date For Internal Use Only Page 2 ANNEXURES: PROJECT PLAN TEMPLATE For Internal Use Only Page 3