Project Plan Revised

7/27/2019 Project Plan Revised

1/23

IT Project Plan Workbook

Page 1 10/15/2013

PROJECT

PLAN WORKBOOK

Sections

I. Project Profile

II. Requirements Decision Making Model

III. Project Plan

IV. Project Plan Schedule

V. Project Implementation Plan

VI. Project Test Plan

VII. Project Plan Recommendation Document

VIII. Project Plan Group Review

IX. Post Project Summary


2/23


Page 2 Revised: 10/15/2013

PROFILE

PREPARED BY: DATE:

ProfilesI. User ProfileUsers Growth

5 Doctors 4 New Doctors

1 Office manager 4 Nurses

1 Billing Manager 4 Interns

10 Nurses

5 Receptionists

5 X-Ray Technicians

10 Medical Assistants

4 Office Supervisors4 Billing Clerks

II. Usage/Applications ProfileWindows 98Novell 4.5

SCO Unix

Billing Management Application

III. Geographic ProfileRosevilleSacramento

Elk Grove

Rancho CordovaFolsom

IV. Hardware Profile


3/23



V. Special Requirements Profile

REQUIREMENTS

DECISION MAKING MODEL

1. LIST REQUIREMENTS

2. 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.

MUST : THE REQUIREMENT IS MANDATORY FOR THE

SYSTEM OR PRODUCT TO BE ACCEPTABLE.

WANT : THE REQUIREMENT IS DESIRABLE BUT NOT

MANDATORY FOR THE SYSTEM OR PRODUCT

TO BE ACCEPTABLE.

RISK DETERMINE THE IMPACT IF THE MUST OR IT T

EVALUATION REQUIREMENT IS NOT MET BY THE PROJECT.


4/23



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 PRIORITY

SCORE

RISK

EVALUATION

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.


5/23



15.


6/23



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 PRIORITY

SCORE

RISK

EVALUATION

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.


7/23



PROJECT PLAN

PREPARED

BY:

DATE:

I. ObjectivesA. System Objectives

B. Infrastructure Objectives

II. Project Scope


8/23



III. Organization

A. Staffing Plan

B. Customer Staffing Plan

IV. Project Approach

A. Project Assumptions

B. Project Risks


9/23



PROJECT PLAN

PROJECT

PLAN:

DATE:

VI. BudgetA. Estimated Resources

B. Cost for Each Phase

C. Estimated Cost for Project


10/23



D. Facility Requirements

VII. Schedule

A. Phases of Work

B. Estimated Phase Start and End Dates

C. Time Line Schedule


11/23



PROJECT CHARTER

PROJECT TITLE:

A. PROJECT DESCRIPTIONThe purpose of this project is to investigate the reasons for the problem and propose asolution.

B. PROJECT MANAGER ASSIGNED AND AUTHORITY LEVELList the person who has been given authority to lead the project. Define the level ofauthority granted such as: does he or she determine budget, schedule and staffing, etc.?

C. OBJECTIVESThe 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 CASEWhy is the project being done? This project is being completed in order to prevent

___________________. We expect that improved customer satisfaction will increaserevenue 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/DELIVERABLESWhat 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.


12/23



PROJECT CHARTERPREPARED BY: DATE:

Project Title:A. PROJECT DESCRIPTION

B. PROJECT MANAGER ASSIGNED AND AUTHORITY LEVEL

C. PROJECT OBJECTIVES

D. BUSINESS CASE

E. PRODUCT DESCRIPTION/DEL IVERABLES

F. SIGNED AND APPROVED BY:

SENIOR MANAGEMENT:


13/23



PROJECT PLANSCHEDULE

Description:

Project Schedule:

Activity Start Date Completion Date Status


14/23



PROJECT

IMPLEMENTATION

PLAN

I. Implementation Plan Overview/Strategy

II. Implementation Plan Task List

Task

#Implementation Plan

Task Description

Resource

Required

days

Responsible

PersonStart

Date

mm/dd/y

y

End

Date

mm/dd/yy


15/23



CONTINGENCY

DE-INSTALLATION

PLAN

III. Contingency De-Installation Plan Overview/Strategy

IV. Contingency De-Installation Plan Task List

Tas

k #Contingency/De-Installation Plan

Task Description

Resource

Required

days

Responsible

PersonStart

Date

mm/dd/yy

End

Date

mm/dd/yy


16/23



PROJECT

TEST PLANUAT Unit

Type of Testing:

PROJECT NAME: TEST CYCLE NO:

PROGRAM NAME:

PREPARED BY: DATE:

TESTED BY: DATE:

Test

Case NoTest Conditions Test Procedures Expected Results Date

Tested

mm/dd

Pass/

Fail

P/F


17/23



PROJECT PLAN

RECOMMENDATION DOCUMENT

PREPARED BY: DATE:

Definition SectionI. Statement of Opportunity

II. Scope of Requirements

A. High Level RequirementsB. Affected/Unaffected Products, Services, or Operations

III. Solution CriteriaA. Summary of Solution CriteriaB. Detailed Evaluation

VI. Recommendation


18/23



II. Requirements Scope

A. High Level Requirements

ReqmtNo.

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

1920


19/23



B. Affected/Unaffected Products, Services, Operations, and Organizations

Category A/U * Description (If Affected (A)

Functions/Processes:

User Departments:

Subsystems:

* A/U: EnterAfor Affected andUfor Unaffected.


20/23



III. Solution Criteria

Solution:

Description:

Advantages:

Disadvantages:

Preliminary Estimate: [of cost and effort required]


21/23



VI. Recommendation

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


22/23



PROJECT PLAN

GROUP REVIEW

Project Name:

Date of Review:

Role Participants Name Comments/Recommendations

Facilitator

Recorder

Reviewer 1

Reviewer 2

Reviewer 3

Reviewer 4

Reviewer 5


23/23


PROJECT PLAN

POST PROJECT SUMMARY

PREPARED BY: DATE:

Comments/Recommendations

I.

II.

III.

IV.

V.

Documents

Project Plan Revised