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

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

3. MD Digital Government Summit, June 26, 2006 3 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 Maryland’s IT Structure

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

5. MD Digital Government Summit, June 26, 2006 5 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. Tier #1 - Professional Project Management (Agency)

6. MD Digital Government Summit, June 26, 2006 6 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. Tier #2 - Portfolio Reviews (DBM / Agency)

7. MD Digital Government Summit, June 26, 2006 7 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. Tier #3 - Peer Review Committees (Multiple Agencies)

8. MD Digital Government Summit, June 26, 2006 8 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. Tier #4 – IV&Vs (Third Party)

9. MD Digital Government Summit, June 26, 2006 9 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. SDLC Purpose

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

11. MD Digital Government Summit, June 26, 2006 11 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. 1. Initiation Phase Products

12. MD Digital Government Summit, June 26, 2006 12 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.

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

14. MD Digital Government Summit, June 26, 2006 14 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.

15. MD Digital Government Summit, June 26, 2006 15 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.

16. MD Digital Government Summit, June 26, 2006 16 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.

17. MD Digital Government Summit, June 26, 2006 17 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.

18. MD Digital Government Summit, June 26, 2006 18 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.

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

20. MD Digital Government Summit, June 26, 2006 20 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.

21. MD Digital Government Summit, June 26, 2006 21 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 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 PMO Resources