Project Charter, Scope Statement, Deliverables, and Objectives

This project charter assignment provides a comprehensive overview of project management principles. It includes a project scope statement detailing the project's goals, deliverables, and execution plan. The assignment emphasizes the creation of a Work Breakdown Structure (WBS) with two levels, task descriptions, project deliverables, and objectives. It also addresses project assumptions, constraints, and exclusions, offering a checklist for acceptance criteria and technical requirements. The document covers essential elements of project planning, including defining scope, developing schedules, and outlining budgets, while also focusing on the practical application of project management tools and techniques.

Project Scope Statement
Project Name Project
Number
Project Manager Prioritization
Owner(s)
NOTE: Remove this note and all instructions in the template for a business professional
document.

Statement of
Work—Project
Description and
Project Product
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 and prepares you for development of
your upcoming WBS. Here you should (A) list about 25+ high-level tasks
and (B) describe how each task will be executed for the project. This
section should be based on information found in the project's charter. For
example, a software development project would have an overall description
(two to three paragraphs explaining the project product).
(A) WBS CONSISTING OF TWO LEVELS. EXAMPLE:
1. Initiation Phase
a. Form team
b. Develop project charter
c. Obtain project approval
2. Planning Phase
a. Define scope
b. Develop schedule
c. Develop budget
d. Develop responsibility matrix
e. Obtain approval
3. Execution Phase
a. …
b. …
c. Etc..
4. Close-out Phase
a. …
b. …
c. Etc
5. Controlling Phase
a. …
b. …
6. Etc.
(B) TASK DETAIL – For each task, use a table to provide the following:.
1. Task Description
2. Who was/will be involved
3. When will the task be done (general estimate)
4. How will the task be done
Project Deliverables What 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 a list of items that
will be the result of the execution of the project work packages in
the WBS. For example, if your task is to develop software
program for application A, one of your deliverables will be
software application developed. The project examples in this
class normally have 8 to 12 deliverables.

LIST INTERNAL DELIVERABLES (EX. STATUS REPORT)
AND EXTERNAL DELIVERABLE (EX.THE EVENT …)
Project Objectives What are the cost, schedule, and quality objectives of this
project? Your objective statement is likely to be the same or
similar as in your project charter, based on any new knowledge.
Here you might add goals for the project. Objectives can and
often do look past the end for the project, such as an example of
cutting costs in operations by 15%. It is highly possible that your
project objective will have some subobjectives or goals. For
example, the project objective for the software project might be
as follows.
The objective of this project is to develop a new programming
application for the payroll department that will interface with the
existing Kronos system by 10/12/2014 at a budgeted cost of
$50,000. The goals of the project include the following.
 Create a newly developed program that will be installed
and tested by users.
 Install and load server hardware required for the
application and database environment.
EXPAND ON THE OBJECTIVES IN THE PROJECT CHARTER
Project Assumptions What are the assumptions on which the project is based?
Project assumptions are those things we believe to be true
without proof for planning purposes. For our software
development, we might assume that users will be available to
test when needed. We have no way to know this for sure during
project planning; thus, it is an assumption for our project. You
should have at least 10 assumptions. USE BULLETS.
EXPAND ON THE ASSUMPTIONS IN THE PROJECT
CHARTER.
Project Constraints What are the major limiting factors that affect the project?
Project constraints are limitations placed upon the project. Many
of them are placed by individuals outside of the project. These
limitations could be laws, regulations, rules, policies,
procedures, or customer or sponsor requirements. Let’s say we
are limited to access for 10 users to test the new application.
This would be a constraint of resources available to test the
project. You should have at least 5 constraints. USE BULLETS.
EXPAND ON THE CONSTRAINTS IN THE PROJECT
CHARTER. .
Exclusions What are the boundaries of the project? What is not going to be
included in the project? This helps the project manager to set
boundaries on the project scope. For example, on our software

development project, we might exclude some specific
functionality on the program. Let’s say Internet access for credit
card payments will not be included in the programming for this
project. You should have at least 5 exclusions. USE BULLETS.
EXPAND ON PROJECT CHARTER. 5+ EXCLUSIONS.
Acceptance Criteria Develop a checklist that will be used by the customer to
measure your performance for the project. This includes the
following: 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? For example, the new application developed must be
installed in accordance with the standard equipment and
specifications; functionality tested by the user and accepted
prior to implementation.
EXPAND ON PROJECT CHARTER.
Technical
Requirements
What is needed to make this project functional in terms of equipment,
computers, cash registers, and so forth? What functionality must it have? In
our example, there would be specific types of hardware required, such as 2
HP Proliant DL580 G7 high performance servers are needed for the
application software program execution and database storage. This section
should contain a list of at least 12 items, with brief description of each.
LIST TECHNICAL KNOWLEDGE AND TECHNOLOGY NEEDED TO DO THE
PROJECT
EX. OF TECHNICAL KNOWLEDGE NEDED:
 KNOWLEDGE EVENT PLANNING AND ORGANIZATION;
 KNOWLEDGE OF PROJECT MANAGEMENT;
 KNOWLEDGE OF HOW TO BUILD A LAN;
 KNOWLEDGE OF HOW TO SET UP SERVERS;
EX. OF TECHNOLOGY NEEDED:
 MS PROJECT;
 MS EXCEL;
 OUTLOOK;
 COMPUTERS;
 PHONES;
APPROVALS
Type Name Signature Date
Project Manager Approval
Customer or Sponsor Approval