Maryland Project Management Oversight System Development Life

Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government Summit June 26, 2006 MD Digital Government Summit, June 26, 2006 1

Agenda • • Maryland’s IT Structure The Four Tiers of Oversight SDLC Purpose & Ten Phases DBM’s PMO Resources MD Digital Government Summit, June 26, 2006 2

Maryland’s IT Structure • 63 Executive Branch Agencies – 63 respective autonomous organizations – 50 Major IT Development Projects(MITDPs) on average across 20 agencies annually • DBM’s Centralized Oversight – Approves State’s IT Master Plans and IT Project Requests – Coordinates the IT Advisory Council (ITAC) • Monthly CIO meeting – Ensures success of all MITDPs • Four tiers of oversight MD Digital Government Summit, June 26, 2006 3

The Four Tiers of PM Oversight 1. 2. 3. 4. Professional Project Management Portfolio Reviews Peer Review Committees Independent Verification & Validations (IV&Vs) MD Digital Government Summit, June 26, 2006 4

Tier #1 - Professional Project Management (Agency) • Dedicated project manager for each project. • Follow PMI’s project management principles. • Follow the State’s System Development Life Cycle (SDLC) methodology. • Provide updates to the DBM / PMO. • DBM procurement under way for an automated, statewide project tracking system. MD Digital Government Summit, June 26, 2006 5

Tier #2 - Portfolio Reviews (DBM / Agency) • One-on-one review of Agency MITDP status. • Purpose is to discuss project risks and responses. • Goal is to identify corrective action tasks and time frames to promote project success. MD Digital Government Summit, June 26, 2006 6

Tier #3 - Peer Review Committees (Multiple Agencies) • Periodic meetings among CIO’s and PM’s from multiple Agencies focusing on one project. • Purpose is to discuss best practices and share experiences applicable to the target project. • Goal is to bolster oversight by leveraging the ITAC membership’s body of knowledge. MD Digital Government Summit, June 26, 2006 7

Tier #4 – IV&Vs (Third Party) • A DBM or Agency partnership with external industry resources. • Purpose is to assess project health via independent analysis. • Goal is to identify corrective action tasks and time frames to promote project success. MD Digital Government Summit, June 26, 2006 8

SDLC Purpose • The methodology provides IT Project Managers with a consistent approach to successful implementation of systems. • The process provides the visibility of design, development, and implementation status needed to ensure delivery on-time and within budget. • The documentation provides for management sign-offs before beginning next SDLC phase. MD Digital Government Summit, June 26, 2006 9

The SDLC Phases 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Initiation System Concept Development Planning Requirements Analysis Design Development Integration and Test Implementation Operations & Maintenance Disposition MD Digital Government Summit, June 26, 2006 10

1. Initiation Phase Products Concept Proposal – Identifies a business need or opportunity, alternative solutions, and constraints and assumptions. Project Management Charter – Identifies the Executive Sponsor and the Project Manager; Authorizes their roles and responsibilities. MD Digital Government Summit, June 26, 2006 11

2. System Concept Development Phase Products System Boundary Document – Identifies the capabilities of a system; Describes IT alternatives and cost/benefits; Identifies high level requirements, risks, and performance measures. Risk Management Plan – Identifies project risks and response strategies; Iterative. Information Technology Project Request – Expands on the Concept Proposal with information from the above products; Accompanies the project budget request. MD Digital Government Summit, June 26, 2006 12

3. Planning Phase Product Project Management Plan – A collection of management plans for scope, schedule, budget, communications, risk, resources, and integrated change control; Iterative MD Digital Government Summit, June 26, 2006 13

4. Requirements Analysis Phase Products Requirements Document – Captures all stakeholder functional and data requirements; Employs a traceability matrix; Ties to the Test and Evaluation Plan. Test and Evaluation Master Plan – A management plan for system testing; Correlates to the Requirements Document; Includes acceptance test plan. MD Digital Government Summit, June 26, 2006 14

5. Design Phase Products System Design Document – Describes final system details / requirements, the O/S, architecture, inputs, outputs, file layouts, interfaces, and processing logic. Implementation Plan – Describes how the system will be deployed; Describes the use of personnel, facilities, materials, and training toward implementation. Contingency Plan – Describes emergency procedures, back-up systems, roles and responsibilities, and recovery processes. MD Digital Government Summit, June 26, 2006 15

6. Development Phase Products Software Development Document – Explains the functionality of each system unit or module. System Software / Test Files / Data – The actual code / COTS modifications, inputs and outputs. Integration Document – Explains how S/W and H/W are combined; how S/W and H/W will interact. Conversion Plan – Describes how data will be migrated to the new H/W and S/W environment. MD Digital Government Summit, June 26, 2006 16

7. Integration & Test Phase Products Test Analysis Approval Determination – Summarizes the perceived readiness for migration of software and data. Test Problem Reports – Documents problems found in testing; Forms the basis for further unit and integration tests. IT Systems Security Certification & Accreditation – The set of plans, procedures, and written assessments on system security; Iterative. MD Digital Government Summit, June 26, 2006 17

8. Implementation Phase Products Delivered System – Production version delivered to the customer for O&M. Change Implementation Notice – Documents requests and approvals for changes made during implementation. Post-implementation Review Report – Reports whether system functions and benefits are as expected. MD Digital Government Summit, June 26, 2006 18

9. O&M Phase Products User Satisfaction Reviews – Used to assess whether system improvements are warranted; An input to In-Process Reviews – Measuring system performance against baseline performance metrics. MD Digital Government Summit, June 26, 2006 19

10. Disposition Phase Product Disposition Plan – Created via recommendation from an In. Process Review; Describes the orderly retirement of a system and disposition of software, hardware, data and documentation. MD Digital Government Summit, June 26, 2006 20

PMO Workshops § Introduction to the SDLC Process Mar – May + TBD § Writing good Statements of Work July 26 § Project Management Best Practices Aug 16 & Sep 13 PMO Resources Oversight Methodology @ www. dbm. maryland. gov, key word: Oversight SDLC @ www. dbm. maryland. gov, key word: SDLC Email DBM / OIT / PMO: oit. pmo@dbm. state. md. us Bob Krauss, PMP: 410. 260. 6135, rkrauss@dbm. state. md. us MD Digital Government Summit, June 26, 2006 21