IT Project Plan Workbook

PROJECT PLAN WORKBOOK Sections

I. II. III. IV. V. VI. VII. Project Profile Requirements Decision Making Model Project Plan Project Plan Schedule Project Implementation Plan Project Test Plan Project Plan Recommendation Document

VIII. Project Plan Group Review IX. Post Project Summary

Page 1

10/15/2013

IT Project Plan Workbook

PROFILE
PREPARED BY: DATE:

Profiles I. User Profile

Users 5 Doctors 1 Office manager 1 Billing Manager 10 Nurses 5 Receptionists 5 X-Ray Technicians 10 Medical Assistants 4 Office Supervisors 4 Billing Clerks Growth 4 New Doctors 4 Nurses 4 Interns

II. Usage/Applications Profile

Windows 98 Novell 4.5 SCO Unix Billing Management Application

III. Geographic Profile

Roseville Sacramento Elk Grove Rancho Cordova Folsom

IV. Hardware Profile

Page 2

Revised: 10/15/2013

IT Project Plan Workbook

V. Special Requirements Profile

REQUIREMENTS DECISION MAKING MODEL

1. 2. LIST REQUIREMENTS CLASSIFY REQUIREMENTS A. MUSTS B. WANTS 3. SCORE REQUIREMENTS A. SCORE MUSTS B. SCORE WANTS 4. DETERMINE RISK EVALUATION A. WHAT COULD GO WRONG IF MUST IS NOT MET? B. WHAT COULD GO WRONG IF IT IS NOT MET? 5. DEFINITION OF TERMS REQUIREMENT: A GENERAL NEED OR CONDITION THAT MUST BE MET BY THE SYSTEM OR PRODUCT FOR IT TO BE ACCEPTABLE BY YOUR DEPARTMENT. THE REQUIREMENT IS MANDATORY FOR THE SYSTEM OR PRODUCT TO BE ACCEPTABLE. THE REQUIREMENT IS DESIRABLE BUT NOT MANDATORY FOR THE SYSTEM OR PRODUCT TO BE ACCEPTABLE. DETERMINE THE IMPACT IF THE MUST OR IT T REQUIREMENT IS NOT MET BY THE PROJECT.
Page 3 Revised: 10/15/2013

MUST :

WANT :

RISK EVALUATION

IT Project Plan Workbook

MUST REQUIREMENTS
Please write all your MUST requirements in the first column. Score each requirement on a scale of 1 to 10. With 10 having the highest priority and 1 having the lowest priority. (1) Determine the level of importance for each requirement. (2) Then evaluate each score by the priority it has for your project. If you encounter two requirements which have equal importance and priority, then perform a risk evaluation. Ascertain the level of impact if this requirement was not met by the project and assign a risk evaluation score based on the same 1-10 scale.
MUST REQUIREMENTS 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Page 4 Revised: 10/15/2013 PRIORITY SCORE RISK EVALUATION

IT Project Plan Workbook 15.

Page 5

Revised: 10/15/2013

IT Project Plan Workbook

WANT REQUIREMENTS
Please write all your WANT requirements in the first column. Score each requirement on a scale of 1 to 10. With 10 having the highest priority and 1 having the lowest priority. (1) Determine the level of importance for each requirement. (2) Then evaluate each score by the priority it has for your project. If you encounter two requirements which have equal importance and priority, then perform a risk evaluation. Ascertain the level of impact if this requirement was not met by the project and assign a risk evaluation score based on the same 1-10 scale.
WANT REQUIREMENT 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. PRIORITY SCORE RISK EVALUATION

Page 6

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN
PREPARED BY: DATE:

I.
A.

Objectives
System Objectives

B.

Infrastructure Objectives

II.

Project Scope

Page 7

Revised: 10/15/2013

IT Project Plan Workbook

III. Organization A. Staffing Plan

B.

Customer Staffing Plan

IV. Project Approach A.

Project Assumptions

B.

Project Risks

Page 8

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN
PROJECT PLAN: DATE:

VI.
A.

Budget
Estimated Resources

B.

Cost for Each Phase

C.

Estimated Cost for Project

Page 9

Revised: 10/15/2013

IT Project Plan Workbook

D.

Facility Requirements

VII. Schedule
A. Phases of Work

B.

Estimated Phase Start and End Dates

C.

Time Line Schedule

Page 10

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT CHARTER PROJECT TITLE: A. PROJECT DESCRIPTION

The purpose of this project is to investigate the reasons for the problem and propose a solution.

B.

PROJECT MANAGER ASSIGNED AND AUTHORITY LEVEL

List the person who has been given authority to lead the project. Define the level of authority granted such as: does he or she determine budget, schedule and staffing, etc.?

C. OBJECTIVES
The project is to be completed no later than ____________. The budget is limited to no more than __________. The project will reduce expenditures by at least ______%. We expect that no more than _______ complaints will occur throughout the project from customers as we interrupt their day-to-day work.

D. BUSINESS CASE
Why is the project being done? This project is being completed in order to prevent ___________________. We expect that improved customer satisfaction will increase revenue to the company in the _____ year due to a decrease in ____________. We hope that the project will generate ideas on improving customer satisfaction while fixing this problem.

E.

PRODUCT DESCRIPTION/DELIVERABLES
What are the specific deliverables wanted and what will be the end result of the project? 1. A report that outlines what can be changed, how much each change will cost and the expected decrease in time it takes to ________ resulting from each change. The report will be presented to these departments: ____________, ______________, and _____________. 2. A list of interactions with our customers necessary to complete the changes. 3. A work breakdown structure, due within _____ weeks, that outlines the plan for accomplishing the project and a list of potential risks expected completing the project.

Page 11

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT CHARTER
PREPARED BY: DATE:

Project Title:
A. PROJECT DESCRIPTION

B.

PROJECT MANAGER ASSIGNED AND AUTHORITY LEVEL

C.

PROJECT OBJECTIVES

D.

BUSINESS CASE

E.

PRODUCT DESCRIPTION/DELIVERABLES

F.

SIGNED AND APPROVED BY:

SENIOR MANAGEMENT:

Page 12

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN
SCHEDULE
Description:

Project Schedule:
Activity Start Date Completion Date Status

Page 13

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT IMPLEMENTATION PLAN

I. II.
Task #

Implementation Plan Overview/Strategy Implementation Plan Task List

Implementation Plan Task Description
Resource Required days Responsible Person Start Date mm/dd/y y End Date mm/dd/yy

Page 14

Revised: 10/15/2013

IT Project Plan Workbook

CONTINGENCY DE-INSTALLATION PLAN III. IV.

Tas k#

Contingency De-Installation Plan Overview/Strategy Contingency De-Installation Plan Task List

Contingency/De-Installation Plan Task Description
Resource Required days Responsible Person Start Date mm/dd/yy End Date mm/dd/yy

Page 15

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT TEST PLAN

UAT Type of Testing: PROJECT NAME: PROGRAM NAME: PREPARED BY: TESTED BY: Unit TEST CYCLE NO: DATE: DATE:

Test Case No

Test Conditions

Test Procedures

Expected Results

Date Tested mm/dd

Pass/ Fail P/F

Page 16

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN RECOMMENDATION DOCUMENT

PREPARED BY: DATE:

Definition Section
I. Statement of Opportunity

II.

Scope of Requirements A. High Level Requirements B. Affected/Unaffected Products, Services, or Operations Solution Criteria A. Summary of Solution Criteria B. Detailed Evaluation Recommendation

III.

VI.

Page 17

Revised: 10/15/2013

IT Project Plan Workbook

II.
A.

Requirements Scope
High Level Requirements

Reqmt No.

Requirement Statement
[Statement must be clearly defined, complete, and verifiable]

Validation Method
[Description of what must occur to demonstrate that the requirement has been met]

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Page 18

Revised: 10/15/2013

IT Project Plan Workbook

B.

Affected/Unaffected Products, Services, Operations, and Organizations A/U * Description (If Affected (A)

Category Functions/Processes:

User Departments:

Subsystems:

A/U: Enter A for Affected and U for Unaffected.

Page 19

Revised: 10/15/2013

IT Project Plan Workbook

III.

Solution Criteria

Solution:
Description:

Advantages:

Disadvantages:

Preliminary Estimate: [of cost and effort required]

Page 20

Revised: 10/15/2013

IT Project Plan Workbook

VI.

Recommendation
[Describe in detail the preferred solution for meeting the customer's requirements including a preliminary estimate for cost, resources, and schedule.]

Page 21

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN GROUP REVIEW

Project Name: Date of Review: Role Facilitator Recorder Reviewer 1 Participants Name Comments/Recommendations

Reviewer 2

Reviewer 3

Reviewer 4

Reviewer 5

Page 22

Revised: 10/15/2013

IT Project Plan Workbook

PROJECT PLAN POST PROJECT SUMMARY

PREPARED BY: DATE:

Comments/Recommendations
I.

II.

III.

IV.

V.

Page 23

Revised: 10/15/2013