13

Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Embed Size (px)

Citation preview

Page 1: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004
Page 2: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Executive Summary

Target Deployment – January 4, 2005Actual Deployment – December 22, 2004

Page 3: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Business Objectives

Ability of Governor to share his vision for the state and his principles of governance

State employees have access to information about state services

Build team spirit of state employeesIncrease number of employees using site

on a regular basis

Page 4: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Technical Objectives

Successfully deploy community of interest content

Successfully deploy private search collection capability

Make survey/feedback capability available in initial deployment

Page 5: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Quality Objectives

Web site available to intended users 98% of the time

Site is effective, consistent, and provides customer satisfaction as measured by website survey

Page 6: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Critical Success Factors

Executive Sponsorship & SupportDedicated ResourcesSingle Point of Authority for Approval

and ChangesCommunication w/Affected AgenciesApplication of Project Management

ProcessesBaseline Plan After Estimating

Page 7: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Project Management Processes

Scope ControlAcceptance Process

12 Distinct Deliverables with baseline target dates

Actual approval of deliverables ranged from 34 days ahead of schedule to 12 days behind schedule.

Average .25 days ahead of schedule

Page 8: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Project Management Processes

Change Management1 change request

Risk Management5 risksMonthly risk review and mitigation

Issue ManagementWrote escalation triggers in PMPAdhered to escalation process and triggers

Page 9: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Project Management Processes

Estimating ProcessEvery Task Estimated for effort and durationOptimistic, Pessimistic, ExpectedUsed MS Project as tool for Putnam

Formula (O + P + 4E)/6

ID Name Optimistic Pessimistic Likely Putnam Work

0 Team Georgia Connection 833 1909 1248 1289 2,144.5 hrs1 Initiation Phase 0 0 0 0 0 hrs7 Planning Phase 122 240 154 163 165 hrs8 Develop Project Charter 38 78 58 58 79 hrs9 Write Draft Project Charter 16 32 24 24 26 hrs

10 Review Project Charter w /Stakeholders 4 4 4 4 4 hrs11 Write Final Draft of Project Charter 8 16 16 14.67 14.5 hrs

Page 10: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Project Management Processes

Capture of Effort Hours and Estimate to Complete on a regular basisRequired time capture from all assigned

resources – state staff as well as contractRequired Estimate to Complete (ETC)Required Target Completion Date

Page 11: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Project Management Processes

Weekly Team MeetingsTrack and Measure Commitments

Identified commitments in all documents such as Charter, Project Management Plan

Identified 33 distinct commitments Identified 125 measurable commitment

events (i.e. weekly team meetings)80% met by due date 95% met w/in 10 days

Page 12: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Areas for Improvement

Improve EstimatesActual Effort capture helps future estimatesSome variances 500%

Identify and Schedule All Tasks and Resources

Include Configuration Advisory Board (CAB) in the Project Plan

Plan for Training PCC Help Desk Personnel

Page 13: Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004

Risks for Release 2

Operational StaffingProject StaffingScope ManagementTime Constraints Due to Legislative

Session