comprehensive delivery process sdm lite v2.03 construction phase training facilitator name: enter...

Comprehensive Delivery Process

SDM Lite v2.03Construction Phase Training

Facilitator Name: enter name

State of Connecticut Department of Information Technology (DOIT)

( Construction Phase TrainingSDM Lite v 2.0

State of Connecticut

Department of Information Technology (DOIT)

Agenda

Overview of SDM Lite v2.0

Governance

Purpose of Construction Phase

Construction Phase Deliverables and Their Owners

Team Members

Construction Phase Activities




Business Issue

•Phase Kickoff Meeting •Project Management Plan•Project Profile •Detailed Schedule for Next-Phase •Phase-End Decision-Point Meeting

Business Requirements

•Bus. and Tech. Rqmts Document•Solution Alternatives Document•Deployment Strategy & Plan•Detailed Schedule for Next-Phase •Phase-End Decision Point Meeting

Design

•System Design Document•System Security Profile•System Design Signoff - TRB•System Design Signoff - PSC•Test Strategy & Plan•Detailed Schedule for Next-Phase

Construction

•Code & Unit Testing•Code Review•Development/Test Environments•Environment Migration Checklist•Software “Golden Build”•System Bill of Materials•System and User Documents•Test Scenarios/Cases•Test Data•Detailed Schedule for Next-Phase

Testing

•Environment Migration Checklist•Integration Testing•System Testing•User Acceptance Testing•Software “Golden Build”•System Bill of Materials•Test Summary Report•Prod. Support & Admin Document•Detailed Schedule for Next-Phase •Phase-End Decision Point Meeting

Post-Implementation

•Project Summary•Project Shutdown

Implementation

•Technology Solution Deployment•Approved Production Turnover•Phase-End Decision Point Meeting

Project Management Plan, Cost Benefit Analysis

Deliverables Updated in Multiple Phases:

SDM Lite v2.03 Deliverables/Events by Phase




Governance – The Project Steering Committee (PSC)Who are the typical PSC members? Agency Commissioners or Designee

Executive Director or Designee

Divisional Directors

What does the PSC do? Sets business strategies within the targeted area;

Sets priorities and allocates resources (people and budgets); and

Makes Go, No-Go, or Redirect decisions for any project in the business area throughout the entire project life cycle.




SDM Standard vs. SDM LiteWhat projects can I use SDM Lite for? For projects with an estimated budget of less than or equal to $400,000 in total project costs,

including acquisition and labor costs; and

For projects that are estimated to take less than six (6) months of duration (calendar time);

For projects that only impact one agency (not including DOIT-hosting);

For technical activities that are EWTA compliant or where an exception has been or will be granted;

Finally, exceptions are permitted, but require the prior approval of the CIO.

What if I need more structure? SDM Lite has only those deliverables and activities that are considered mandatory, regardless

of the project’s goals;

Agency-heads, Executive Sponsors or Technical Managers can include any deliverable available in SDM Standard into an SDM Lite Project as necessary to help manage risk.




Construction Phase PurposeThe Purpose of the Construction Phase is to:

Translate the Business and Technical Requirements and the detailed design as documented in the System Design Document into functioning software modules and supporting test and training artifacts;

Validate the required system software and hardware to support the solution construction, testing, and implementation;

Update or create a set of test cases to ensure that the business process flows are tested from end to end;

Update or create any relevant System and/or User Documentation necessary to support the users of the solution;

Document support structure, technical support skills, production turnover criteria, and any Service Level Agreement (SLA) if necessary; and

Develop a detailed plan that commits to the completion of the Construction Phase; verify targets for the completion of the Testing, Implementation, and Post-Implementation Phases.




Construction Phase Work Breakdown Structure (WBS)4.0 Construction

Phase

4.01EstablishInfrastructure

4.02 Perform Code&Unit

Testing

4.03 Update/Create Test Cases

4.04 Update/Create System & User Documentation

Validate/Confirm Infrastructure

Install/Refresh the Test Environment

Install/Refresh the Development Environment

Prepare the Development

Team(s)

Code & Unit Test Custom Software& Package Extns

Prepare/Configure Test Management

Tool

Update/Create System/User Documentation

4.06 Conduct Phase-End Decision Point Meeting

Create the Phase-End Decision Point Meeting

Presentation

Code & Unit TestApplication

Interface Software

Update/Create IntegrationTest Cases

Execute the Communication Plan

Conduct the Phase-End Decision Point Meeting

Plan Remaining Phases

Establish“Golden Build” for Integration Testing

Update/Create User AcceptanceTest Cases

Identify Test Cases for Regression Testing

Update/Create PerformanceTest Cases

Update/Create SystemTest Cases

Install/Refresh the Infrastructure Components

Conduct Code Reviews

4.05 Plan Production Support

Create Solution Overview

DocumentApplication Support

Service Levels

Document SupportRoles &

Responsibilities

Document Network SupportService Levels

Create ProductionSupport Turnover

Checklist

Create/Update the Environment Migration

Checklist

Create Test Data& Load into Development &

Test Databases

Update/Create Test Scenarios

Prepare/ConfigureDefect Management

Tool

Conduct Test Case

Review

DocumentSystem Availability

Service Levels

Catalog All Solution

Components




Key Deliverables in the Construction Phase

Key Deliverables – Documentation

Update or Create Test Cases (See Below),

System Bill of Materials,

Environment Migration Checklist (DOIT-hosted Applications only),

PSC Decision Point Presentation,

User Documentation & Training Materials, and.

Update the Project Management Plan

Key Deliverables - Test Cases

Integration Cases,

Performance Test Cases,

System Test Cases,

Unit Test Cases, and

User Acceptance Test Cases.

Key Deliverables – Software, Hardware, and Data

Build or Refresh Development & Testing Environments,

Software Code Verified & Assembled for Testing, and

Test Data Validated and Loaded.




Construction Phase Deliverable Snapshot

PHASE ACTIVITY NUMBERS

Team Lead Deliverables Mandatory Owner 01 02 03 04 05 06

Environment Migration Checklist Mandatory1 Infrastructure Lead N I

Development & Testing Environments Mandatory Infrastructure Lead S

“Golden Build” of Software for Testing Mandatory Development Lead C

System Bill of Materials Mandatory Development Lead N

Test Cases Mandatory Test Lead S

Test Data Mandatory Test Lead C

Test Strategy & Plan Mandatory Test Lead I

System and User Documentation Mandatory Deployment Lead C

Phase-End Decision Point Presentation Mandatory Technology Manager S

Update Project Management Plan Mandatory Technology Manager R

1. Mandatory for DOIT-hosted applications only, strongly recommended for all others.




Project Steering Committee (PSC)Name / AgencyName / Agency

TECHNOLOGY PARTNERS

BUSINESS PARTNERS

* <Name Required>Business Manager

* Name RequiredBusiness Requirements

Lead

<Name Required>Technology Manager

Name RequiredDevelopment Lead

Name RequiredSecurity Lead

* Name(s) RequiredBusiness SMEs

* Name RequiredBusiness Process

Lead

Name RequiredTest Lead

* Staffed from the Business

Name RequiredInfrastructure Lead

* Name RequiredUAT Lead

Name Required Executive Sponsor

Support/Consulting Roles:Financial Advisor: Enterprise Architect: Name RequiredBusiness Division Director: Name Required

* Name RequiredDeployment Lead

Name RequiredVendor Lead

Instructional Note:•Remove this note before presenting this slide•Remove roles that are not applicable to your project (even is it has “name required”)•If the role IS applicable to your project, then you must specify a name if the role has “name required”•If other standard SDM roles are needed, you may add them to the wheel.•Do not Update or Create any new role names; All role names are standardized within the SDM framework

Construction Phase Team Wheel




Business Division Director (Technology Role) Point of leadership escalation for technology risks and issue for the Project Team. Ensures that all technology projects being run within their assigned Agencies are aligned with SDM. Monitors the execution of all technology projects within their assigned Agencies.

Business Manager (Business Role) Responsible for coordination and delivery of all Business activities and deliverables; Provides business consultation to the technology team; Contributes to Disaster Recover planning; Provides project plan updates for all Business activities and deliverables; Attends/Participates in all Phase-End Decision Point Meetings

Business Requirements Lead (Business Role) Maintains the Functional Requirements Workbook; Maintains the Non-Functional Requirements Workbook; Provides general business requirements consultation to the project team;

Deployment Lead (Business Role) Maintains the Deployment Strategy & Plan document; Responsible for coordinating all implementation activities at the deployment site(s); Responsible for creating the Training Plan; Responsible for creating all User Documentation and Training Materials;

Construction Phase Roles and Responsibilities




Development Lead (Technology Role) Maintains the System Design Document; Responsible for mapping design components to the Requirements Traceability Matrix; Maintains the Release Strategy & Plan (if required); Update or Creates and maintains the Backout/Recovery Plan; Responsible for coordination of all software code & unit testing; Responsible for loading the migrating new software builds across environments; Responsible for coordination of all software defect remediation; Responsible for identifying defects, and entering them into the defect management tool; Contributes Performance test metrics to the Test Summary Report; Responsible for conducting code reviews; Responsible for creation of test data; Maintains the Technical Requirements Workbook; Maintains the Requirements Traceability Matrix; Update or Creates and maintains the System Bill of Materials;

Enterprise Architect - (Technology Role) Responsible for ensuring that EWTA requirements are addressed with the solution; Provides on-going architecture consultation to the project team;





Executive Sponsor (Business Role) Responsible for providing the project funding source; Attends/Participates in Phase-End Decision Point Meeting; Primary leadership escalation point for significant project risks and issues;

Infrastructure Lead (Technology Role) Single point of contact for the project team for all infrastructure needs (e.g., hardware, software, database, network); Responsible for the planning and coordination of all infrastructure activities; Relies on resources from the various infrastructure

areas to deliver the actual infrastructure work; Update or Creates and maintains the Environment Migration Checklist; Responsible for establishing the development and testing environments; Assists the Development lead in loading test data across into the various environments; Assists the Development lead in loading software builds into the various environments;

Project Steering Committee (Business & Technology Leadership Roles) Provides governance and decision making to the project team; Removes barriers for the project team; Reviews the Phase-End Decision Point presentation material prior to the Phase-End Decision Point Meeting; Renders a Phase-End decision of “Go”, “No-Go” or “Redirect” as it relates to the project team proceeding to the next phase.





Security Lead (Technology Role) Participates in code reviews; Provides security consultation to the project team as needed;

Technology Manager (Technology Role) Responsible for creation and maintenance of the overall project plan (including Business and Technology activities); Responsible for the overall coordination and delivery of all Technology deliverables; Responsible for creating the Disaster Recovery Plan; Update or Creates all Phase-Kickoff Meeting presentations; Facilitates all Phase Kickoff Meetings; Maintains the Configuration Management Plan; Updates the Project Team Wheel; Updates the Project Management Plan; Responsible for creating the PSC Phase-End Decision Point Meeting Presentations; Hosts and facilitates the PSC Phase-End Decision Point Meetings; Responsible for providing project status reporting at monthly project reviews; Responsible for creating the final Project Summary and formal shutdown of the project.

Test Lead (Technology Role) Responsible for the planning and execution of Integration and System testing; Update or Creates and maintains all Integration and System test cases and scenarios; Responsible for mapping Integration & System test cases to business requirements in the Requirements Traceability Matrix;





UAT Lead (Business Role) Responsible for the planning and execution of User Acceptance testing; Update or Creates and maintains all User Acceptance test cases and scenarios;





Activity 4.01: Establish InfrastructurePurpose:

The purpose of this activity is to acquire and install the required system software and hardware to support the solution Construction, Testing, and Implementation.

This Activity Produces the Following:

Verify available Infrastructure Budget and procure needed Infrastructure Components for all environments;

Execute Environment Migration Checklist (for DOIT-hosted Application);

Install Technology and Infrastructure Components;

Prepare Development Environments; and

Prepare Test Environments.




Activity 4.02: Perform Code & Unit TestingPurpose:

The purpose of this activity is to install, build, and unit test all of the software components based on the approved Detail Design.


Prepare the Development Team;

Update or Create Test Data and load into Test Databases;

Code and Unit Test custom software and package extensions;

Code and Unit Test legacy interface software;

Code and Unit Test software for operating and supporting the solution;

Code and Unit Test data conversion routines;

Execute Code Merges;

Conduct Code Reviews;

Catalog all Solution Components; and

Assemble the Solution Components for Integration Testing.




Activity 4.03: Update or Update or Create Test CasesPurpose:

The purpose of this activity is to update or create a set of Test Cases to ensure that the business process flows are tested from end to end.


Update or Create Test Scenarios;

Update or Create Integration Test Cases;

Update or Create System Test Cases;

Update or Create Performance Test Cases;

Identify Test Cases for Regression Testing

Update or Create User Acceptance Test Cases;

Conduct the Test Case Review; and

Update the Requirements Traceability Matrix with Test Scenarios and Test Cases.




Activity 4.04: Update or Create System and User DocumentationPurpose:

The purpose of this activity is to complete the user documentation and training materials necessary to train and support the users of the solution.


• Update or Create any relevant System and/or User Documentation.

• User Documentation may also include any online application help or web-based materials.




Activity 4.05: Plan Production SupportPurpose:

The purpose of this activity is to document the support structure required to support the new application once it is deployed to production. The support structure will describe the available support services, the responsible support organizations, and the support processes and procedures that will be used.


Update or Create a Solution Overview for the Production Support Team;

Document the Application Support Service Levels;

Document the Network Support Service Levels;

Document System Availability Service Levels;

Document the Support Roles and Responsibilities;

Document the Problem Ticket Workflow and Escalation Path; and

Update or Create the Production Support Turnover Checklist.




Activity 4.06: Conduct Phase Decision Point MeetingPurpose:

The purpose of this activity is to obtain a “Go”, “No-Go”, or “Redirect” decision from the Project Steering Committee.

Minimum Suggested Attendees for the Phase Decision Point Meeting:

Project Manager,

Project Sponsor,

PSC,

Technology Manager, and

Business Manager


Distribute the Construction Phase Decision Point Presentation to the PSC;

Conduct the Phase-end Decision Point Meeting; and

Execute the communication plan.




On-going SDM Support

SDM Resources:

Newly designed SDM website: www.ct.gov/doit/sdm

SDM Overview & Training

SDM Sample Deliverables

SDM Email Box:

[email protected]

Inbox is reviewed on a scheduled basis (e.g., weekly, bi-weekly, etc.)

Will add input for ‘FAQ’ section of website

PMO Team will respond to feedbackSDM Continuing Education:

SDM open communication forums

SDM Brown Bags

Specific discussion on ‘hot’ SDM topics

Scheduled assistance as requested




PMO Team MembersPlease contact the PMO Team with any questions that you have. The PMO Team will be reviewing the SDM Feedback Mailbox on a regular basis.

PMOPMO

PMO Team Members:

Lois Bryant 860-622-2981 [email protected]

Tricia Johnson, PMO Director 860-622-2549 [email protected]

Dawn Keiper 860-622-2232 [email protected]

Jim Rutushni 860-622-2271 [email protected]

Lori Violette 860-622-2365 [email protected]

Larry Williford 860-622-2465 [email protected]

The PMO Team also has a group telephone # 860-622-2085. If you receive the voicemail, please leave a message as the voicemail will be

checked on a regular basis.

PMO Web site: www.ct.gov/doit/pmo




Thank you for attending!

Any questions, comments or suggestions??

comprehensive delivery process sdm lite v2.03 construction phase training facilitator name: enter...

Documents

phase slide

total project costs

project steering committee

entire project life

business area

business strategies

typical psc members

projects goals agen