Project Plan Template - Ver 1.0 - SCG

8/7/2019 Project Plan Template - Ver 1.0 - SCG

http://slidepdf.com/reader/full/project-plan-template-ver-10-scg 1/27

Project Plan

for the

<insert name here>



<insert name here>

Sarasota County Government

<project name> Project Plan

Document Control

Document Approval

Approvals Signature Date

Document History

Revision Author/Reviser Comments Date

Document Storage

This document is created in Microsoft Word 2000 and is maintained in the <insert web

address or network drive/folder here>

Project Contact





Preface

This Project Plan defines the activities to be performed, the products to be developed, theproject schedule, and the resources required to develop the <project name here>. This

Project Plan will be used as a tool to track and manage the project.

Table 1 Initial Distribution List

Name Project Role Delivery

Information

Name Sponsor, Tester,etc

E-mail, Web, etc.

After Initial Distribution the lastest version of the project plan will be located on the EIT

Project Page located at <insert web address or network drive/folder here>







1 Introduction

1.1 Project Plan Purpose

The purpose of this document is to provide a mechanism to communicate the

project scope, assumptions, constraints, project issues, risks, and Project

Management objectives as well as other pertinent project information. Project

details relating to work at the task level is in the Work Breakdown Structure

(Appendix B).

This project plan will be used to manage tasks, milestones, the projectschedule, project issues, risks, and resource assignments for the <project

name> project.

The Project Major Milestone and Schedule Summary can be found in Appendix

A. The Work Breakdown Structure, Schedule, and link to the Microsoft Project

Plan are contained in Appendix B. Appendix C contains the latest version of the

Project Issues Log.

1.2 Evolution of the Project Plan

This Project Plan will be reviewed and updated if necessary at the end of each

life cycle phase to ensure that it accurately reflects the status of the project.

The Project Plan will also be reviewed in the Weekly Project Status meeting and

modifications will be made if required.

If changes to the Project Plan’s Schedule Baseline are required, they will be

made once an approved Scope Change Request has been completed andapproved.





Table 1 Reference Materials

Document Overview Created

By

Document File Location and/or Name





2 Project Overview

2.1 Project Scope

This project will allow for planning, design, development, testing, and

implementation of a <project name/short description>

2.2 Project Modules

Table 2 Vendor Developed Modules

Vendor Module(s)

Table 3 Internally Developed Modules

Group Module(s)





2.3 Project Assumptions and Constraints

2.3.1 Assumptions

2.3.2 Constraints

2.4 Software Life Cycle (If applicable, remove if not)

Example: The software life cycle chosen for this project is Rapid Application

Development (RAD). This life cycle was chosen because this project is on a

fast track and as such must be developed in the shortest amount of time.

2.5 Project Issues

Issues and problems will be tracked in the Project Issues Log as they arise.

(Appendix C). The issues log will be uploaded to the <Applicable Project WebSite> every <day of week/time>.

2.6 Course CorrectionsCourse corrections will be made throughout the project. These course

corrections will be discussed in the Weekly Project Status Meetings.

http://intranet/project_support/hrms.asp








2.7 Testing

2.7.1 Testing

<organization name(s) here> will be responsible for testing the following

components:

1. Component One

2. Component Two

3. etc.

2.7.2 User Acceptance Testing

Example: Business Center and PMO personnel will be responsible for the

development and implementation of the user acceptance test. The User

Acceptance Test (UAT) will ensure the primary sponsor and stakeholders are

satisfied that the requirements have been me. A signoff of the UAT by the

project sponsor is required prior to implementation.

Example: The User Acceptance Test will test at a minimum the following:

1. All GUIs and backend functionality

2. Manager Portal, GUIs, and backend functionality

3. Administration Portal, GUIs and backend functionality

4. Merit Increase Process Functionality

5. Performance Review Process

6. Performance Review Process – Multi-Rater Feedback

7. Employee Information Update Process

2.8 Training

A training plan will be developed outlining the roles and responsibilities of





3 Project Management

3.1 Project Management Objectives and Priorities

Example

1. Ensure the project completes on the targeted implementation

date.

2. Assist in obtaining needed development and support tools to

support EIT development.

3. Assist (as needed) the development manager in identifying

and distributing responsibilities to development resources by

components.

4. Coordinate external issues through the appropriate

departments.

5. Conduct and lead weekly Project Management status meetings

to gather and report accurate status.

6. Report project progress through the creation of weekly status

reporting.

3.2 Procedures, Methods and Standards

Example

1. Project status will be reported weekly. Status reports will be

available on the EIT Project Web Site every Wednesday.







Table 4 Project Roles

Example- Delete and add applicable project information

Project Role Name Responsibilities

XXX General Manager Name Oversee EIT and External Development Efforts

Development Manager Name Development responsibilities

Project Manager Name Day-To-Day Project Oversight

Department Manager Name Manage Development Resources

Analysis Name, Resource 2Gustafson, Resource 1

Gather and document project requirements

Development Developer/Vendor names Develop application processes,

reports, custom modules and GUIs

Database Administration

DBA Design, develop, and support theDatabase

Quality Team

Members

Names Quality Team

Table 5 Project Contact List

Example

Name Department Phone # E-mail Address Location

Diana Allen Human Resources/Payroll 316-1206 [email protected] 6700 Clark

Rd.

Brian Darley Enterprise InformationTechnology

861-5418 [email protected] SCTC

Barbara

Thibault

Human Resources/Personnel 861-5326 [email protected] 1600 Ringling

http://intranet/ephone/[email protected]










4 System Overview

4.1 Figure 1 – System Connectivity

Example Only

4.1.1 PLANNING

SCG LAN

SC G

W AN

HRMS

Database

Server

ABRA Administrator

ABRA

Database

Server

HRMS

Database

(Partial Update

Capability)

ABRA

Full Access

Business Center

HR Reps

Note: Exporting Data from HRMS to

ABRA will not be attempted. There

will be no fall back plan to use the

ABRA Database once HRMS has

been tested and implemented.

HRMS

Database

Full Access

E-mailed HRMS Updates From Business

Center Rep to ABRA Administrator





4.1.2 DATABASE CLEANUP ACTIVITIES

Example High-Level Planning Milestones

Task Status

Check for dates and numbers outside of normal

ranges

Not started

Payroll/HR comparison (pay, classification,position from standard download)

Not started

Classification and Transaction updates Not started

Other Maintenance reports Not startedEntry of employee change transactions through

last full pay period prior to implementation.

Not started

Example High-Level Estimate (optional)

Staff: Tom – Entry of Corrections; Entry of change transactions.Resource 1 – Run Exception Reports and Comparisons; update code tables

Time: 40 hours





5 Critical Computer Resources

The following table summarizes the list of the critical computer resources

required for this project for all impacted systems:

Table 6 Summary of Critical Computer Resources for the Project

Example

Resource New/Additional Type and/or

Application

Source

Workstations

(development,

testing, training,

production, user)

N/A N/A N/A

Servers (Production,

Test, Development,

and Training)

2 (Production) Microsoft IIS

Microsoft SQL

Server 2000

EIT

Direct AccessStorage Device

(DASD)

N/A N/A

Communications

requirements

Connectivity

from all SCG

County Offices to

the Suncoast

Technology

Center

Connectivity to SCG

iNet

EIT

System Software,

Utilities Software

Development

Test

Identitech

Components

EIT





• Level of effort (LOE) information would normally be documented

in the Milestone and Schedule Summary in the table of Appendix B.

Since this project follows a RAD approach, LOE information by Milestone

will not be supplied.

• Schedule estimates would normally be derived by estimating the

project at a task level, using task decomposition techniques, and by

interviewing the resources on the development team. Since this project

will utilize a RAD approach, the schedule has been built using the project

completion date and backing into a schedule from there.

•

Estimates and timeframes noted in the Microsoft Project Plan(MPP) contain our best guesses as to when certain tasks will be

complete. The MPP will evolve over time and be adjusted as needed.

Milestone information is documented in Appendix B at a summary level

and the schedule is documented in detail in the Work Breakdown

Structure referenced in Appendix C.





7 Risk Management

Example

1. Risks will be identified throughout the project and reviewed in weekly project

status meetings.

2. Risks that are discovered externally will be evaluated by the project

lead/development team and considered for inclusion, then prioritized and addressed if necessary in the Risk Statement Table (below).

3. All action items resulting from the Risk assessments will be noted in the

Project Issues log and reviewed in the Weekly Project Status meeting.

Table 7 Risk Management (Example)

# Risk RiskConsequence

PriorityHigh,

Medium, Low

Risk resolution progress

1 Creeping

requirements

Delayed

Implementation

Increased Scope

High • User interface prototype used to gather

high-quality requirements.

• Staged delivery approach will be employed

to provide some ability to change featuresif needed.

2 Requirements or developer gold- plating

Delayed ImplementationIncreased Scope

High • Project Status Meetings will check for suspected “gold-plating” concerns or evidence.

3 Unstable tools

delay schedule

Delayed

Implementation

High • New tools are used on this project.

NOTE: No resolution known

4 Released softwarehas low quality

Delayed Implementation

Low Customer

Medium • User interface prototype developed toassure users would accept software.

• Internal Technical reviews will be

conducted in the EIT Network Applications





8 External Dependencies

8.1.1 This project is dependent upon …





Appendix A - Major Milestone and Schedule

Summary

Example: The following high-level milestones will be tracked for this project. The

detailed schedule and resources can be found in the Work Breakdown Structure

referenced in Appendix C.

Table 8 Major Milestone LOE and Schedule Summary

Phase 1 Scheduled

Start Date

Actual

Start Date

Scheduled

End

Actual

End Complete Draft RS/HLA 01/21/03 01/21/03 02/04/03

Complete Draft Project Plan 01/24/03 01/23/03 02/07/03

Coding and Testing 02/18/03 02/18/03 05/24/02

Establish User Acceptance Test

(UAT) Environment

Promote Code/Tables to

Production

05/26/03 05/28/03

Execute UAT 05/28/03 06/21/03

Production Implementation 06/25/03 06/26/03

Warranty 06/26/03 07/26/03

Project Close-out 07/28/03 07/30/03





Appendix B – Initial Work Breakdown Structure

<Next page>



<Project Name> Sarasota County Government

Example Only – Delete

ID Task Name Duration Start Date Finish Date Pred. Resource Names

1 HRMS Phase I WBS and Schedule 164 days? Fri 12/13/02 Thu 7/31/03

2 Analysis 57 days? Fri 12/13/02 Tue 3/4/03

3 Finalize Module Process Flows 27 days Fri 12/13/02 Tue 1/21/03

4 Merit Increase 0 days Fri 12/13/02 Fri 12/13/02 Resource 1, Resource2

5 Performance Review 0 days Fri 12/13/02 Fri 12/13/02Resource 1, Resource

2

6 Review Process Flow with EIT 0 days Fri 12/13/02 Fri 12/13/02Resource 1, Resource

2

7 Performance Review (Multi-Rater Feedback Sub-Process) 0 days Fri 12/13/02 Fri 12/13/02Resource 1, Resource

2

8 Employee Update 0 days Fri 12/13/02 Fri 12/13/02Resource 1, Resource

2

9 Process Flows Complete 0 days Tue 1/21/03 Tue 1/21/03

10

11 Initial GUI Design 11.1 days Tue 1/21/03 Wed 2/5/03

12 Design HR Admin Screens 10 days Tue 1/21/03 Mon 2/3/03 Resource 1

13Send out HR Admin Screens and Business Center Data Cleanup

Screens for Review0.1 days Wed 2/5/03 Wed 2/5/03 Steve

14 Design HR/Business Center Data Cleanup Screens for review 0.1 days Wed 2/5/03 Wed 2/5/03 Resource 1

15 Design Portal Screens 10 days Tue 1/21/03 Mon 2/3/03 Resource 2

16 Send Portal Screens out for review 0.1 days Wed 2/5/03 Wed 2/5/03 Resource 2

17 Portal Design Complete 0 days Wed 2/5/03 Wed 2/5/0316

1819 Initial Requirements Definition 18.2 days Tue 1/21/03 Fri 2/14/03

20 Develop HRMS RS/HLA Document - First Cut 11 days Tue 1/21/03 Tue 2/4/03 Steve

21 Send out RS/HLA (ver.0.6) document for review 0.1 days Tue 2/4/03 Tue 2/4/0320 Steve

22 Meet with Identitech to clarify project scope and objectives 0.2 days Tue 2/4/03 Tue 2/4/03Steve, Resource 1,

Resource 2

23 Send out meeting minutes from Identitech meeting 0.2 days Tue 2/4/03 Tue 2/4/03 Steve

24 Setup Kick-off Meeting 0.1 days Tue 2/4/03 Tue 2/4/03 Steve

25 Conduct Kick-off Meeting 0.2 days Thu 2/13/03 Thu 2/13/0324 Steve

<project name WBS> 01/23/11




26Update/Changes to RS/HLA document based on feedback from Kick-off Meeting

1 day Thu 2/13/03 Fri 2/14/03 25 Steve

27Baseline RS/HLA document established (the document is still a workin progress)

0 days Fri 2/14/03 Fri 2/14/03 26 Steve

28

29 HRMS Database 30 days? Tue 1/21/03 Tue 3/4/03

30 Initial meeting to discuss HRMS Database requirements 0.2 days Thu 1/23/03 Thu 1/23/03Resource 2, Resource1, Steve, Jim

31 Create Initial Design of Database Model 3 days Thu 1/23/03 Tue 1/28/03 30 Jim

32 Review Database Model with Analysis Team 0.2 days Tue 1/28/03 Tue 1/28/03 31 Resource 1, Jim

33 Create HRMS Database 13 days Tue 1/28/03 Fri 2/14/0332 Jim

34 Populate new database with a few test records 1 day? Fri 2/14/03 Tue 2/18/03 33 Jim

35 Import ABRA data into HRMS Database 0 days Tue 1/21/03 Tue 1/21/03 34 Jim

36 HRMS Test Database Ready 30 days Tue 1/21/03 Tue 3/4/0335Jim, Resource 2,

Resource 1

3738 Coding 94 days? Tue 1/21/03 Mon 6/2/03

39 HR Standalone Database Admin GUIs 50 days? Tue 1/21/03 Tue 4/1/03

40 HR Business Center Cleanup GUIs 48 days? Tue 1/21/03 Fri 3/28/03

41 Build Screens 18 days Mon 3/3/03 Wed 3/26/03 MethodFactory

42 Test Screens 2 days Thu 3/27/03 Fri 3/28/0341Resource 2, Resource1

43 Screens Ready to Deploy 0 days Fri 3/28/03 Fri 3/28/0342

44

45 Test Screens 1 day? Tue 1/21/03 Tue 1/21/03

46 HR Administration GUIs 22 days Mon 3/3/03 Tue 4/1/03

47 Build Screens 18 days Mon 3/3/03 Wed 3/26/03 MethodFactory

48 Test Screens 4 days Thu 3/27/03 Tue 4/1/0347Resource 2, Resource

1

49 Screens Ready to Deploy 0 days Tue 4/1/03 Tue 4/1/0348

50

51 LDAP Functionality 28.2 days Tue 4/15/03 Fri 5/23/03

52 Receive LDAP Module From Identitech 0.2 days Tue 4/15/03 Tue 4/15/03 Team

53 LDAP Testing with E-directory 10 days Tue 4/15/03 Tue 4/29/03 52 Team





54 Beta Testing with select users 8 days Tue 4/29/03 Fri 5/9/0353 Beta Users

55 Testing with Large Test Group (100 plus users) 10 days Fri 5/9/03 Fri 5/23/0354 Release Users

56 LDAP Module Ready 0 days Fri 5/23/03 Fri 5/23/0355

57

58 NetFYI Modules 55.2 days? Tue 1/21/03 Wed 4/9/03

59 Merit Increase Process 32.2 days? Tue 1/21/03 Fri 3/7/03

60 Develop Detailed Requirements for Merit Increase Process 22.9 days? Tue 1/21/03 Fri 2/21/03

61 Clarify and nail down exact process steps and included functionali ty 0.5 days Tue 2/18/03 Tue 2/18/0334 Team

62 Identify Data Types used in process steps 1 day Tue 2/18/03 Wed 2/19/03 61 Team

63Identify data elements to be read from/written to the HRMS

Database1 day Wed 2/19/03 Thu 2/20/03 62 Team

64 Document operations on specific fields 1 day Wed 2/19/03 Fri 2/21/0363 Team

65 Define IFAS data requirements 0.5 days Fri 2/21/03 Fri 2/21/0364Resource 1, Resource2

66 Define flat file format for IFAS 1 day? Tue 1/21/03 Tue 1/21/03 Data Management

67 Coding 2.75 days Fri 2/21/03 Wed 2/26/03

68 Build Search Classes 0.5 days Fri 2/21/03 Mon 2/24/0365 Team

69 Build database indexes 0.5 days Mon 2/24/03 Mon 2/24/0368 Team

70 Build Work Flow 0.5 days Tue 2/25/03 Tue 2/25/03 69 Team

71 Build other required sub processes and modules? 0.5 days Mon 2/24/03 Wed 2/26/03 70 Team

72 Build Prototype of Merit Increase Process 0.5 days Wed 2/26/03 Wed 2/26/03 71 Team

73 Test 32.2 days? Tue 1/21/03 Fri 3/7/03

74 Test Prototype Process Flow utilizing test users in Roles database 0.5 days Wed 2/26/03 Thu 2/27/0372 Team

75Unit test of Merit Increase Process utilizing live Data in HRMS

Database0.5 days Thu 2/27/03 Thu 2/27/03 74 Team

76 Test Prototype in Development Environment 0.5 days Thu 2/27/03 Fri 2/28/0375 Team

77 Review Prototype and Functionality with Red Team 0.2 days Mon 3/3/03 Mon 3/3/03 76

78 Rework Prototype into final Process/Workflow 4 days Mon 3/3/03 Fri 3/7/0377

79 Workflow ready for Testing 0 days Fri 3/7/03 Fri 3/7/0378

80

81 Performance Management Process 23 days Fri 3/7/03 Wed 4/9/03

82Develop Detailed Requirements for Performance

Management Process12 days Fri 3/7/03 Tue 3/25/03





83 Clarify and nail down exact process steps and included functionality 2 days Fri 3/7/03 Tue 3/11/0379 Team

84 Identify Data Types used in process steps 2 days Tue 3/11/03 Thu 3/13/0383 Team

85 Document operations on specific fields 2 days Thu 3/13/03 Mon 3/17/0384 Team


Database2 days Mon 3/17/03 Wed 3/19/03 85 Team

87 Define IFAS data requirements 2 days Wed 3/19/03 Fri 3/21/0386 Team88 Define/Update flat file format for IFAS 2 days Fri 3/21/03 Tue 3/25/03 87 Team

89 Code 6 days Tue 3/25/03 Wed 4/2/03

90 Build Search Classes 1 day Tue 3/25/03 Wed 3/26/03 88 Team

91 Build database indexes 1 day Wed 3/26/03 Thu 3/27/0390 Team

92 Build other required sub processes and modules? 1 day Thu 3/27/03 Fri 3/28/0391 Team

93 Cleanup Efforts and final 1 day Fri 3/28/03 Mon 3/31/03 92 Team

94 Build Work Flow 1 day Mon 3/31/03 Tue 4/1/0393 Team

95 Build Prototype of Performance Management Process 1 day Tue 4/1/03 Wed 4/2/0394 Team

96 Test 5 days Wed 4/2/03 Wed 4/9/03

97 Test Prototype Process Flow utilizing test users in Roles database 1 day Wed 4/2/03 Thu 4/3/03 95 Team

98Unit test of Merit Increase Process utilizing live Data in HRMSDatabase

1 day Thu 4/3/03 Fri 4/4/0397 Team

99 Test Prototype in Development Environment 1 day Fri 4/4/03 Mon 4/7/0398 Team

100 Review Prototype and Functionality with Management 1 day Mon 4/7/03 Tue 4/8/0399 Team

101 Rework Prototype into final Process/Workflow 1 day Tue 4/8/03 Wed 4/9/03100 Team

102 Workflow ready for System Testing 0 days Wed 4/9/03 Wed 4/9/03101 Team

103

104 Employee Information Update Process 45 days Tue 4/1/03 Mon 6/2/03

105 Develop Detailed Requirements for Employee InformationUpdate Process

6 days Tue 4/1/03 Tue 4/8/03

106 Clarify and nail down included functionality 1 day Tue 4/1/03 Tue 4/1/03 Web1

107 Identify Data Types 1 day Wed 4/2/03 Wed 4/2/03106 Web1

108 Document operations on specific fields 1 day Thu 4/3/03 Thu 4/3/03107 Web1


Database1 day Fri 4/4/03 Fri 4/4/03108 Web1

110 Define IFAS data requirements 1 day Mon 4/7/03 Mon 4/7/03109 Web1

111 Define/Update flat file format for IFAS 1 day Tue 4/8/03 Tue 4/8/03110 Web1





112 Code 34 days Wed 4/9/03 Mon 5/26/03

113 Build Search Classes 2 days Wed 4/9/03 Thu 4/10/03111 Web1

114 Build database indexes 2 days Fri 4/11/03 Mon 4/14/03113 Web1

115 Build other required sub processes and modules? 2 days Tue 4/15/03 Wed 4/16/03 114 Web1

116 Cleanup Efforts and final 2 days Thu 4/17/03 Fri 4/18/03115 Web1

117 Employee Portal 26 days Mon 4/21/03 Mon 5/26/03

118 Develop Prototype Screen(s) 3 days Mon 4/21/03 Wed 4/23/03 116 Web1

119 Route to HR Subject Matter Experts for Feedback/Approval 1 day Thu 4/24/03 Thu 4/24/03 118 Web1

120 Build Screens 10 days Fri 4/25/03 Thu 5/8/03119 Web1

121 Integrate into Identitech Processes and HRMS Structure 12 days Fri 5/9/03 Mon 5/26/03 120 Web1

122 Test 5 days Tue 5/27/03 Mon 6/2/03

123 Test of GUI and Employee Read/Update Processes 5 days Tue 5/27/03 Mon 6/2/03121 Web1

124 Process ready for Testing 0 days Mon 6/2/03 Mon 6/2/03123

125

126 Portal Development 30.5 days Tue 4/1/03 Tue 5/13/03127 Manager Portal 30.5 days Tue 4/1/03 Tue 5/13/03

128 Develop Prototype Screen(s) 5 days Tue 4/1/03 Mon 4/7/03 Web2

129 Route to HR Subject Matter Experts for Feedback/Approval 0.5 days Tue 4/8/03 Tue 4/8/03 128 Web2

130 Build Screens 10 days Tue 4/8/03 Tue 4/22/03 129 Web2

131 Integrate into Identitech Processes 15 days Tue 4/22/03 Tue 5/13/03 130 Web2

132 Ready for Testing 0 days Tue 5/13/03 Tue 5/13/03 131

133

134 HR Administration Portal 30.5 days Tue 4/1/03 Tue 5/13/03

135 Develop Prototype Screen(s) 5 days Tue 4/1/03 Mon 4/7/03 Web3136 Route to HR Subject Matter Experts for Feedback/Approval 0.5 days Tue 4/8/03 Tue 4/8/03 135 Web3

137 Build Screens 10 days Tue 4/8/03 Tue 4/22/03 136 Web3

138 Integrate into Identitech Processes 15 days Tue 4/22/03 Tue 5/13/03 137 Web3

139 Ready for Testing 0 days Tue 5/13/03 Tue 5/13/03 138

140

141 User Acceptance Testing (UAT)/System Test 22 days Mon 5/26/03 Tue 6/24/03

142 Obtain/Create System test data 2 days Mon 5/26/03 Tue 5/27/03 Team

143 Performance Review 5 days Wed 5/28/03 Tue 6/3/03142 Users





144 Performance Review (Multi-Rater Feedback Sub-Process) 4 days Wed 6/4/03 Mon 6/9/03 143 Users

145 Merit Increase 2 days Tue 6/10/03 Wed 6/11/03 144 Users

146 Employee Information Update Process 3 days Thu 6/12/03 Mon 6/16/03145 Users

147 HR Administrators Portal 15 days Mon 5/26/03 Fri 6/13/03Resource 2, Resource

1

148 Manager's Portal 4 days Tue 6/17/03 Fri 6/20/03146 Users149 Employee's Portal 2 days Mon 6/23/03 Tue 6/24/03 148 Users

150 User Acceptance Testing Complete 0 days Tue 6/24/03 Tue 6/24/03 149

151

152 Implementation 2 days Wed 6/25/03 Thu 6/26/03

153 Load Code in Production Environment 2 days Wed 6/25/03 Thu 6/26/03150 Team

154 Load Production Data into Production Database 2 days Wed 6/25/03 Thu 6/26/03150 Team

155 System Live in Production 0 days Thu 6/26/03 Thu 6/26/03154,153 Team

156

157 Project Closeout Activities 2 days Fri 6/27/03 Mon 6/30/03

158 Archive all Project Documentation 2 days Fri 6/27/03 Mon 6/30/03155 Team, PM

159 Place all code in Source Safe 1 day Fri 6/27/03 Fri 6/27/03155 Team

160Conduct Lesson's Learned and Project Close-out Meeting with

Stakeholders0.5 days Mon 6/30/03 Mon 6/30/03 159 PM

161 Close-Out Activities Complete 0 days Mon 6/30/03 Mon 6/30/03160

162

163 Warranty 24 days? Mon 6/30/03 Thu 7/31/03

164 Warranty Period for Phase I 23 days Mon 6/30/03 Wed 7/30/03 Team

165 Warranty Period Complete 1 day? Thu 7/31/03 Thu 7/31/03164

166

167Project Complete - Warranty and Project Closeout Activities

Complete0 days Thu 7/31/03 Thu 7/31/03165





APPENDIX C – PROJECT ISSUES LOG

<next page>





Project Issues Log - Examples – Delete

Issue # Issue Type, Description and

Impact to Project

Priority

(M/H/L

)

Date

Reported

Reported

By

Assigned

To

Date

Resolved

Status Resolution/Comments

1 Issue Type: Resource

Description (revised) Needresource commitments to fully staff

the “Red”, “Blue”, and “Quality”

teams

Impact: If the resources that have

been identified aren’t assigned to this

project, quality will suffer.

M 02/25/03 Jack Bill Open 02/25 – Will forward the list of

requested resources to EIT management by COB on 02/28.

03/03 – Have resource commitments

for Red Team, part of Blue Team,

and we are working on the rest of

the list. Resources that are needed

that can’t be obtained will be

escalated to EIT management.

2 Issue Type: Resource

Description: No resourcecommitments from development for

GUI development.

Impact: The project requires anInternet Presence resource now to

review GUI requirements and

estimate resources and Level of Effort

(LOE).

H 02/26/02 Jack PMO

Manager

Open 02/25 – Will forward this issue to the

PMO Manager for action


Documents

Project Plan Template - Ver 1.0 - SCG