UH | CoT | ILT

Project Team [Team Name/Number]

[Semester] | CIS4375.[Section]
Project Charter

Saved: 5-Jul-16
Printed: 20-Aug-13

[Project Charters provide decision makers with enough information to authorize work on a project.
The Charter imparts authority to the designated project manager to develop a project management
plan and funding request. At the start of a Charter, it would be helpful to summarize the projects
purpose.]

GOALS AND OBJECTIVES

[For decision makers to make an informed decision, they must understand the overall goals and
objectives of the project.
Goals should state a desired future state, like This project will produce a software product that
Instructors will use to manage their class & assignment rubrics.
Objectives are specific, measureable, attainable, relevant, time-bound, and should directly support
their goal(s), e.g. By Week 5, the Project Team will produce a project management plan by which
the Rubric project will be managed.
For our purposes, a bulleted list in the following format will suffice.]

Goal 1
o Objective 1
o

Goal 2
o Objective 1
o

BUSINESS BACKGROUND
[For management to make an informed decision, the project team must provide background about
the organization for which the project is undertaken. This may be a corporation, a department or a
work unit. The Business Background focuses on the context of the project.]

PROBLEM STATEMENT
[The problem statement should state the business problem clearly & succinctly, but should provide
decision makers with enough information to understand how the Proposed Solution will address the
problem.]

PROPOSED SOLUTION
[The proposed solution should describe the solution and the way in which it solves the stated
problem.]

344205815

Mark Stinnett tmstinnett2@uh.edu

Page 1 of 4

UH | CoT | ILT
Project Team [Team Name/Number]
[Semester] | CIS4375.[Section]
Project Charter

Saved: 5-Jul-16
Printed: 20-Aug-13

HIGH-LEVEL REQUIREMENTS
[To be successful a product must meet the clients needs. While detailed requirements are
developed during the Analysis Phase, the Project Team should include a list of high-level
requirements (high-level functions & features)]
#

Requirement Description

Source

Priori
ty
(HML
)

ASSUMPTIONS & CONSTRAINTS

[Project Team should identify known assumptions & constraints, so they, the sponsor and any other
decision maker understands the parameters under which the project team will operate.]

SUMMARY OF MILESTONES & DELIVERABLES

[The Charter should include a high-level list of known milestones & deliverables, along with
expected completion dates. For our purposes, most milestones & deliverables have been specified
by the instructor, but the project team and the client may have additional requirements which
should be listed.]
#

Milestone/Deliverable

Expected
Completion Date

Charter

17 Sep 2015

2
3
4

INITIAL STAKEHOLDER REGISTER & AGREEMENT TO PROCEED

344205815

Mark Stinnett tmstinnett2@uh.edu

Page 2 of 4

UH | CoT | ILT
Project Team [Team Name/Number]
[Semester] | CIS4375.[Section]
Project Charter

Saved: 5-Jul-16
Printed: 20-Aug-13

All parties agree that the Charter reasonably reflects their understanding of
the current situation, the defined problem & proposed solution, assumptions
& constraints under which the team will operate, and the expected due dates
for key deliverables;

All parties understand that the project is a class exercise for a UH, College of
Technology, Computer Information Systems undergraduate course which is
intended, primarily, as a vehicle for teaching UH students about software
development; and,

Project Team members understand that they have an obligation to work with
the client to deliver a best effort web application which satisfies both:
o Client requirements (which will be defined in the Requirements
Traceability Matrix),
o Class requirements (as defined in the Project Requirements document);

Client Sponsor authorizes the Project Team to begin working on a Project

Management Plan, which will provide an overall structure for managing the
software development effort.
Stakeholder Register & Agreement to Proceed
Role

Name

Signature & Date

Client
Sponsor:
Project
Manager:
Coordinator:
Analyst:
Designer:
Developer:
Tester:

[General Template Recommendations: This template has been provided as a way both to reduce
the effort required to complete the CIS2334 project and to standardize deliverables for easier
instructor review and grading. You are strongly encouraged to use the format and styles, as
defined.
344205815

Mark Stinnett tmstinnett2@uh.edu

Page 3 of 4

UH | CoT | ILT
Project Team [Team Name/Number]
Saved: 5-Jul-16
[Semester] | CIS4375.[Section]
Project Charter
Printed: 20-Aug-13
[Only certain styles & properties have been standardized. The Calibri font was chosen because
some campus printers have had issues printing other fonts. Any defined style that does not use
the Calibri font has not been modified as part of this standard. The Body Text style was created as
the standard body of text style and should be used unless circumstances require a different look &
feel. The Heading styles provide 5 levels of distinct headers. The Normal style has no before/after
spacing and is good for tightly spaced bullets.
[All Instruction text should be removed prior to publication or submission. The Client should never
see a document that includes these instruction comments.
Finally, the templates are intended as guides. Do not allow yourself to be straight-jacketed by
them. I would encourage you to talk with the instructor prior to any major modifications, but if the
templates are hindering your ability to complete the assignment, do not hesitate to change them.]

344205815

Mark Stinnett tmstinnett2@uh.edu

Page 4 of 4