KVCC IT -- Project Management Document

IT Project Manager:
Department/Requestor:

1. Introduction
A high-level narrative description of the project, providing background information, areas
covered, and approach taken.

2. Goals and Objectives

An explanation of the projects goals and supporting objectives. These goals and objectives, as
well as the measures of success for each (e.g. automation, cost savings, efficiencies, etc.), will
derive primarily from the requesting department. However, listing some of the major ones will
help focus the ITs efforts. Example:

Goal Objectives

The system will
improve job
satisfaction levels
within the Institution
It will allow users to work more efficiently and
effectively, thus freeing time for those activities which
add greater value
Staff will have greater accessibility to the information
they need to do their job
The system will provide greater transparency for
decision makers at all levels

3. Scope and Schedule

Page 1 of 3 KVCC IT -- Project Management Document

A broad explanation of the work required, broken down into phases and tasks as appropriate.
The schedule may include milestones, duration, start and end dates, and dependencies where
these are known.

Phase/Task: Schedule information

5. Out of Scope
If any related areas or tasks are defined as beyond the scope of this project, highlighting these
areas may reduce confusion and help align stakeholder expectations.

6. Risks, Constraints, Assumptions and Implications

This section is critical in outlining issues, events and conditions which may impact the project,
as well as how the project might itself impact other areas.

List major project risks, as well as early warning signs and any relevant mitigation strategies.
Also summarize known constraints that may affect the scope or schedule of the project. A list
of assumptions upon which the project plan is based will further help to clarify conditions
under which this plan might change. Implications of this project underscore potential effects
that the project or its product(s) may have on other systems or processes.

7. Roles & Responsibilities

Direct human resource requirements for the project should be listed here. The roles and
responsibilities will tie back to 3. Scope and Schedule.

Page 2 of 3 KVCC IT -- Project Management Document

Name: Role/Responsibilities

8. Stakeholder Information and Communication

Appropriate two-way communication with stakeholders is crucial to project success, both
during and after the project.

Stakeholder(s) Information Shared Frequency Media/Method

Page 3 of 3 KVCC IT -- Project Management Document