Project Plan

Project Plan

for the

<insert name here>

Project

Version: 1.0.0April 10, 2023

Sarasota County GovernmentProject Management Office

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

The contact for this document is:

<project manager name>Phone: E-mail: Sarasota County GovernmentProject Management Office (PMO)

PMO Ver. 1.0.0ii


Preface

This Project Plan defines the activities to be performed, the products to be developed, the project 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>

PMO Ver. 1.0.0iii


Table of Contents

Approvals............................................................................................................................... III

1 INTRODUCTION..............................................................................................................61.1 Project Plan Purpose...........................................................................................................61.2 Evolution of the Project Plan.............................................................................................6

2 PROJECT OVERVIEW.....................................................................................................82.1 Project Scope....................................................................................................................... 82.2 Project Modules...................................................................................................................82.3 Project Assumptions and Constraints..............................................................................92.4 Software Life Cycle.............................................................................................................92.5 Project Issues....................................................................................................................... 92.6 Course Corrections.............................................................................................................92.7 Testing................................................................................................................................ 102.8 Training.............................................................................................................................. 10

3 PROJECT MANAGEMENT............................................................................................113.1 Project Management Objectives and Priorities.............................................................113.2 Procedures, Methods and Standards.............................................................................113.3 Quality Assurance Plan....................................................................................................12

4 SYSTEM OVERVIEW....................................................................................................134.1 Figure 1 – System Connectivity......................................................................................13

5 CRITICAL COMPUTER RESOURCES........................................................................155.1 Critical Computer Resource Assumptions.....................................................................15

6 PROJECT SCHEDULE AND LEVEL OF EFFORT ESTIMATES.............................15

7 RISK MANAGEMENT...................................................................................................17

8 EXTERNAL DEPENDENCIES......................................................................................18

APPENDIX A - MAJOR MILESTONE AND SCHEDULE SUMMARY...........................18

Appendix B – Initial Work Breakdown Structure...............................................................19

Index of Tables

Table 1 Reference Materials......................................................................................................7Table 2 Vendor Developed Modules..........................................................................................8Table 3 EIT Developed Modules.................................................................................................8Table 4 Project Roles................................................................................................................12Table 5 Project Contact List.....................................................................................................12Table 6 Summary of Critical Computer Resources for the Project.........................................15Table 7 Risk Management........................................................................................................17Table 8 Major Milestone LOE and Schedule Summary............................................................18

PMO Ver. 1.0.0iv


1 Introduction

1.1 Project Plan PurposeThe 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 project schedule, 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 and approved.

PMO Ver. 1.0.05


Table 1 Reference Materials

Document Overview Created By

Document File Location and/or Name

PMO Ver. 1.0.06


2 Project Overview

2.1 Project ScopeThis 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)

PMO Ver. 1.0.07


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 IssuesIssues 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 Web Site> every <day of week/time>.

2.6 Course Corrections Course corrections will be made throughout the project. These course corrections will be discussed in the Weekly Project Status Meetings.

PMO Ver. 1.0.08

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 One2. Component Two3. 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 functionality2. Manager Portal, GUIs, and backend functionality3. Administration Portal, GUIs and backend functionality4. Merit Increase Process Functionality 5. Performance Review Process6. Performance Review Process – Multi-Rater Feedback7. Employee Information Update Process

2.8 TrainingA training plan will be developed outlining the roles and responsibilities of the <appropriate organizations here>.

PMO Ver. 1.0.09


3 Project Management

3.1 Project Management Objectives and PrioritiesExample

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 StandardsExample

1. Project status will be reported weekly. Status reports will be available on the EIT Project Web Site every Wednesday.

2. Changes to milestone dates, risks, or resources, which have the potential to result in a Scope Change Request (SCR), will be communicated to the project stakeholders in the weekly status report.

3. Project Schedule issues will be tracked and controlled by the project manager and the project team.

4. Project Schedule actuals in regards to Milestone Actual Start and Finished dates will be reported via the Project Status Report

5. Risk Management will be performed throughout this project.

6. Weekly Status meetings will be held with select members of the project team.

PMO Ver. 1.0.010



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 responsibilitiesProject Manager Name Day-To-Day Project OversightDepartment Manager Name Manage Development ResourcesAnalysis Name, Resource 2

Gustafson, Resource 1Gather and document project requirements

Development Developer/Vendor names Develop application processes, reports, custom modules and GUIs

Database Administration

DBA Design, develop, and support the Database

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 Information Technology

861-5418 [email protected] SCTC

Barbara Thibault

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

Eleanor Zoppe Enterprise Information Technology


Resource 2 Gustafson

Enterprise Information Technology


Fred Dunayer Enterprise Information Technology


Gayle Gursky Finance and Administration 861-6176 [email protected] 1301 Cattlemen

Nancy Fisher Administrative & Financial Services

861-6715 [email protected] 2817 Cattleman

Nikki Snyder Payroll (Finance - Clerk) 861-5159 [email protected] 1660 Ringling

3.3 Quality Assurance Plan

PMO Ver. 1.0.011

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


mailto:[email protected]

mailto:[email protected]





4 System Overview

4.1 Figure 1 – System Connectivity Example Only

4.1.1 PLANNINGExample High-Level Planning Milestones

Task StatusConduct a Database Model Review with the Database Architect

Complete – 02/07/03

Initial meeting with Web developers to discuss details surrounding the GUIs

Scheduled – 02/10/03

Meet with developers and Database Architect to map GUI fields to database tables/fields

Not scheduled. No resources identified as of 02/10/03.

Developers and Core team to meet to define data constraints

Not started

Define error processing for all GUIs Not started

PMO Ver. 1.0.012


4.1.2 DATABASE CLEANUP ACTIVITIESExample High-Level Planning Milestones

Task StatusCheck 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 startedOther 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

PMO Ver. 1.0.013


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/orApplication

Source

Workstations (development, testing, training, production, user)

N/A N/A N/A

Servers (Production, Test, Development, and Training)

2 (Production) Microsoft IISMicrosoft SQL Server 2000

EIT

Direct Access Storage 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 Tools

DevelopmentTestProduction

Identitech ComponentsSQL Server 2000 SoftwareMicrosoft IIS Software

EIT

5.1 Critical Computer Resource AssumptionsExample

1. The critical computer resources requirements as outlined above will be required to complete Phase I of the HRMS project.

2. The EIT/Network Applications group created the above Critical Computer Resource requirements.

6 Project Schedule and Level of Effort Estimates

Example Level of effort (LOE) information would normally be documented in the

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

PMO Ver. 1.0.014


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.

PMO Ver. 1.0.015


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

Priority High,

Medium, Low

Risk resolution progress

1 Creeping requirements

DelayedImplementation

Increased Scope

High User interface prototype used to gather high-quality requirements.

Staged delivery approach will be employed to provide some ability to change features if 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 software has low quality

Delayed Implementation

Low Customer Satisfaction

Medium User interface prototype developed to assure users would accept software.

Internal Technical reviews will be conducted in the EIT Network Applications group for requirements, designs, and code.

Test planning assures system testing will cover all functionality.

Independent testers perform system tests.

5 Unachievable schedule

Sponsor dissatisfaction

Customer dissatisfaction

Medium Schedule is re-estimated several times over the course of the project.

Active project tracking assures that schedule slips have better chance of being recognized.

Staged delivery allows for delivery of partial functionality even if whole project takes longer than expected.

6 Friction between developers and customers

Customer dissatisfaction

Project Failure

Low User interface prototype aligns developers and customers on same vision.

Staged deliveries provide customers with evidence of steady progress.

8 External Dependencies

PMO Ver. 1.0.016


8.1.1 This project is dependent upon …

PMO Ver. 1.0.017


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 ScheduledStart Date

ActualStart Date

ScheduledEnd

ActualEnd

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) EnvironmentPromote 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

PMO Ver. 1.0.018


Appendix B – Initial Work Breakdown Structure

<Next page>

PMO Ver. 1.0.019

<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, Resource 2

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

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

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

8 Employee Update 0 days Fri 12/13/02 Fri 12/13/02 Resource 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 Review

0.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/03 16

18

19 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/03 20 Steve

22 Meet with Identitech to clarify project scope and objectives 0.2 days Tue 2/4/03 Tue 2/4/03 Steve, 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/03 24 Steve

26 Update/Changes to RS/HLA document based on feedback from Kick- 1 day Thu 2/13/03 Fri 2/14/03 25 Steve

<project name WBS> 04/10/23


off Meeting

27Baseline RS/HLA document established (the document is still a work in 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/03 Resource 2, Resource 1, 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/03 32 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/03 35Jim, Resource 2, Resource 1

37

38 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/03 41Resource 2, Resource 1

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

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/03 47Resource 2, Resource 1

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

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/03 53 Beta Users



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

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

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 functionality 0.5 days Tue 2/18/03 Tue 2/18/03 34 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 Database

1 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/03 63 Team

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

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/03 65 Team

69 Build database indexes 0.5 days Mon 2/24/03 Mon 2/24/03 68 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/03 72 Team

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

0.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/03 75 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/03 77

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

80

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

82Develop Detailed Requirements for Performance Management Process

12 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/03 79 Team



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

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


2 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/03 86 Team

88 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/03 90 Team

92 Build other required sub processes and modules? 1 day Thu 3/27/03 Fri 3/28/03 91 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/03 93 Team

95 Build Prototype of Performance Management Process 1 day Tue 4/1/03 Wed 4/2/03 94 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 HRMS Database

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

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

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

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

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

103

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

105Develop Detailed Requirements for Employee Information Update 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/03 106 Web1

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


1 day Fri 4/4/03 Fri 4/4/03 108 Web1

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

111 Define/Update flat file format for IFAS 1 day Tue 4/8/03 Tue 4/8/03 110 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/03 111 Web1

114 Build database indexes 2 days Fri 4/11/03 Mon 4/14/03 113 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/03 115 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/03 119 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/03 121 Web1

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

125

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

127 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 Web3

136 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/03 142 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/03 145 Users

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

148 Manager's Portal 4 days Tue 6/17/03 Fri 6/20/03 146 Users

149 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/03 150 Team

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

155 System Live in Production 0 days Thu 6/26/03 Thu 6/26/03 154,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/03 155 Team, PM

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

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

0.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/03 160

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/03 164

166

167Project Complete - Warranty and Project Closeout Activities Complete

0 days Thu 7/31/03 Thu 7/31/03 165



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

DateResolved

Status Resolution/Comments

1 Issue Type: ResourceDescription (revised) Need resource 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: ResourceDescription: No resource commitments from development for GUI development.Impact: The project requires an Internet 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


Project Plan

Documents

project schedule

project modules

project assumptions

project overview

project scope

project roles

project plan purpose

project management objectives