V 2.0 Project Charter Project Name Project Number Project Manager Prioritization Owner(s) Start Date: Scheduled Completion Date: Mission/ Purpose What is your project going to accomplish? How does this project relate to overall goals and objectives of the company? It is part of a program or larger project? SOW What will this project create? What is the product of the project? At a high level, how do you plan on doing the work of the project? What are the high-level deliverables for this project? Objectives What objectives, if any, of the company is this project designed to meet? Business NeedWhy should we do this project? What will be gained, changed, or modified? Is there a financial or business reason to do this project? This area should contain any feasibility studies, NPV, PI, PB, or PBD used to advance the project. Project Manager and Stakeholders Who will lead this project? Who are the major stakeholders? Milestones What are the key milestone dates associated with the project? Budget What is the order-of-magnitude budget for this project? User Acceptance Criteria/Quality What are the minimum success criteria as defined by the key stakeholders? High-Level Project Assumptions What are the assumptions on which the project is based? High-Level Project ConstraintsWhat are the major limiting factors that affect the project? Exclusions and Boundaries What are the boundaries of the project? What is to be included and what is to be excluded from the project? Major Risks What are the major risks affecting the project? KEY STAKEHOLDERS Project Manager Authority Level Project Core Team Subject Matter Experts (SMEs) (include company and channel designations if applicable) APPROVALSType NameSignatureDate Project Manager Approval: Customer/Sponsor Approval: V 2.0 Project Scope Statement Project Name Project Number Project Manager Prioritization Owner(s) Statement of Work—Project Description and Project Product This section is typically a detailed amplification of the project SOW and mission from the Project Charter. This also includes how you intent to accomplish the project. “We intend to do this. . . and here are the steps we intend to use to accomplish the project.” This section is typically a detailed amplification of the SOW product description from the Project Charter. What will the product of the project look like or what should it be able to do when completed? Project DeliverablesWhat are the tangible outputs or services of this project? What big-picture items will have to be created or performed in order to accomplish the statement of work? These are the deliverables to be found in the WBS. Project Objectives What are the cost, schedule, and quality objectives of this project? Project Assumptions What are the assumptions on which the project is based? Project ConstraintsWhat are the major limiting factors that affect the pro ...

1. V 2.0
Project Charter
Project Name
Project Number
Project Manager
Prioritization
Owner(s)
Start Date:
Scheduled Completion Date:
Mission/ Purpose

2. What is your project going to accomplish? How does this
project relate to overall goals and objectives of the company? It
is part of a program or larger project?
SOW
What will this project create? What is the product of the
project? At a high level, how do you plan on doing the work of
the project? What are the high-level deliverables for this
project?
Objectives
What objectives, if any, of the company is this project designed
to meet?
Business NeedWhy should we do this project? What will be
gained, changed, or modified? Is there a financial or business
reason to do this project? This area should contain any
feasibility studies, NPV, PI, PB, or PBD used to advance the
project.
Project Manager and Stakeholders
Who will lead this project? Who are the major stakeholders?
Milestones
What are the key milestone dates associated with the project?
Budget
What is the order-of-magnitude budget for this project?

3. User Acceptance Criteria/Quality
What are the minimum success criteria as defined by the key
stakeholders?
High-Level Project Assumptions
What are the assumptions on which the project is based?
High-Level Project ConstraintsWhat are the major limiting
factors that affect the project?
Exclusions and Boundaries
What are the boundaries of the project? What is to be included
and what is to be excluded from the project?
Major Risks
What are the major risks affecting the project?
KEY STAKEHOLDERS
Project Manager Authority Level
Project Core Team

4. Subject Matter Experts (SMEs) (include company and channel
designations if applicable)
APPROVALSType NameSignatureDate
Project Manager Approval:
Customer/Sponsor Approval:

5. V 2.0
Project Scope Statement
Project Name
Project Number
Project Manager
Prioritization
Owner(s)
Statement of Work—Project Description and
Project Product
This section is typically a detailed amplification of the project
SOW and mission from the Project Charter. This also includes
how you intent to accomplish the project. “We intend to do this.
. . and here are the steps we intend to use to accomplish the
project.”
This section is typically a detailed amplification of the SOW
product description from the Project Charter. What will the
product of the project look like or what should it be able to do
when completed?
Project DeliverablesWhat are the tangible outputs or services of
this project? What big-picture items will have to be created or
performed in order to accomplish the statement of work? These
are the deliverables to be found in the WBS.
Project Objectives
What are the cost, schedule, and quality objectives of this

6. project?
Project Assumptions
What are the assumptions on which the project is based?
Project ConstraintsWhat are the major limiting factors that
affect the project?
Exclusions
What are the boundaries of the project? What is to be included
and what is to be excluded from the project?
Acceptance Criteria What must the product be able to do when
completed to be acceptable to the customer? What standards or
regulations must the product meet? What performance
specifications must the product meet to be acceptable to the
customer?
Technical RequirementsHow should the product work? What
features should it have? What functionality must it have?
APPROVALSType NameSignatureDate
Project Manager Approval:
Customer/Sponsor Approval:

7. Project Charter
Provide a project charter of your selected project in accordance
with the charter template attached. Be certain to include the
following.
Project Objectives
Project Statement of Work
Milestones
All other sections as required in the project charter
Please put this in proper business writing format. Consider me
to be your boss.
Deliverables:
Project charter (in MS Word)
Scope Statement
Prepare a scope statement using the attached template.
Remember to be tangible, measurable, and specific. Be sure to
include all sections required in the Practitioner section below.
On the practical side of project management, a scope statement
is often created a little different than in the above explanation.
When starting to create a scope statement, one must remember
that it is arguably the most important single document created
on a project. Without a complete, thorough scope statement,
chances of success on the project are not very good. Each
section of a practitioner-based scope statement is described
below.
Project Scope and Product Scope description. In this section of
the scope statement, we specifically elaborate on what the
project will create. One should also discuss here how the project
team plans to accomplish this project. This section should be
quite detailed, because it creates the basis for the entire project.
This section should be based on information found in the

8. project's charter.
Deliverables. As stated earlier, deliverables are tangible items
or services created for this project. These are generally big
picture items. For example, if the project was to build a
shopping mall, the foundation, walls, roof, and parking lot
might be examples of deliverables.
Project Acceptance Criteria. Project acceptance criteria are the
criteria the customer will use to judge whether the project was
successful or not. What must this project create in order for the
sponsor or customer to be satisfied with the results?
Inclusions and Exclusions. What is included in the project and
what is not included in it? Returning to our example of a
shopping mall, is the layout of each individual store part of the
project, or is that the responsibility of the soon-to-be tenant?
These inclusions and exclusions set the boundaries for the
project manager to operate within.
Project Assumptions. Project assumptions are those things we
believe to be true without proof for planning purposes. For our
mall, we could assume that all the materials we need to build it
will be available when we need them. We have no way to know
this for sure during project planning, thus it is an assumption.
Project Constraints. Project constraints are limitations placed
upon the project. Many of them are placed by individuals
outside of the project. Let’s say we are only given a budget of
$5 million dollars to build our mall. That $5 million dollars is a
constraint to the project, because we have no more money than
that to complete the project.
Notice that milestones are not included in this list. From a
practitioner point of view, milestones are found in the charter,
not in the scope. If these milestones were modified from those
in the charter, the new milestones may appear in the scope
statement; however, if they were not modified, they are not
normally found in the scope statement.

9. Deliverables:
Project scope statement (in MS Word)