Attachment_13_Solution_Delivery_Framework_SOP_v5.pptx

Attachment 13 – Solution Delivery Framework (SDF)

Standard Operating Procedures (SOP) Solution Lifecycle The lifecycle of a solution begins with a project request and ends with retirement or replacement..

The following slides will outline how the Project Sponsor, Project Manager, and Operations Manager will plan, build, deploy, manage, and retire applications within the overall OCIO application paradigm.

The “Procedure Legend” below defines the diagram notation used in the following slides:

PROCEDURE LEGEND

Phase/Activity Start Middle Phase/Activity End of Lifecycle

Resource Milestone

Phase/Activity Input

Phase/Activity Output

Control Gate

Recurring Activity

Termination Point

Standard Operating Procedures (SOP) Solution Delivery Framework (SDF) Delivery (SDF) Maintenance (O&M) Disposition

Development of solutions within the Peace Corps are managed according to a strict framework. The lifecycle of an solution begins with a Request, or Concept Proposal. This concept proposal is presented to the Technology Advisory Board (TAB) and if approved, moves into the Solution Delivery Framework (SDF). Once approved, the idea is transformed into an active project, and an actionable Project Management Plan is developed which dictates how requirements are identified, and how the application will be developed, tested and deployed. This Delivery Phase is explained in the approved Peace Corps’ SDF.

The output of the SDF is the solution and attendant Operations & Maintenance Plan, which dictates the system’s architecture, configurations, roles, ownership, and procedures for upgrades, patches, and change requests. This document outlines the activities and management structure of the application during the Maintenance Phase.

The final phase of any application’s lifecycle is the Disposition Phase. The disposition phase manages the formal retirement of the system. The disposition shall be managed similar to a regular project (according to the SDF), with or without a replacement system, with the Disposition Plan acting as the project’s charter. Once the system is identified as a candidate for retirement, the Disposition Plan drafted by the O&M Manager will outline the required activities in order to successfully retire/replace the application.

Retirement

Project Manager Assigned Project Manager Assigned

Request Termination SDF: Request

IPT

Approval

Initiation N

Termination

Initiation Planning & Requirements Design Development Integration & Test Deployment Closeout

BAM/Requestor develops Concept Proposal elaborating upon PRF

Concept Proposal CIO IPT provides input and vets Concept Proposal including budget BAM/Requestor presents Concept Proposal to TAB

Concept Review (TAB) BAM/Requestor presents PRF to CIO IPT

TAB

Approval PM updates Project SharePoint site with status and Artifacts

PRF Review (IPT)

OCIO PM Assigned PM updates Project SharePoint site with Status and Artifacts Project placed in Approved Backlog Y Approved, Pending N Approved, Active Requestor develops Project Request Form (PRF)

Project Request Form

BAM/Requestor presents PRF to TAB

PRF Review (TAB)

TAB

Approval Y

PM prepares the Project Charter SDF: Initiation PM updates Project SharePoint site with status and artifacts

Requirements & Planning

Request Initiation Planning & Requirements Design Development Integration & Test Deployment

PM identifies Project Team members

Concept Proposal

Project Team establishes scope and defines high-level requirements PM presents Project Charter to CIO IPT

Initiation Review (IPT) PM conducts project kick-off meeting with Project Team

Project Charter PMO Manager reviews Project Charter

SDF: Planning & Requirements PM updates Project SharePoint site with Status and Artifacts

Development Type?

Design Waterfall Development Agile Development Go to Slide 7

Design, Develop, Test Go to Slide 11

Request Initiation Planning & Requirements Design Development Integration & Test Deployment

PM prepares PMP and Tailoring Guide

Project Charter

PMP, Tailoring Guide

PM assigns development of requirements to business analysts and technical SMEs Business analysts conducts requirements elaboration sessions Technical SMEs develop non-functional requirements PM presents Requirements Document and schedule to IPT

Requirements Review (IPT)

IPT

Approval Y N Project team documents detailed requirements PM develops schedule

Schedule PM initiates procurement activities

Requirements Document

Waterfall Development

SDF: Design (Waterfall) PM manages development of system design to meet requirements

Requirements Document

PM schedules Design Review for next CIO IPT PM briefs SDD to CIO IPT

Design Review Requirements and Design Documentation baselined and development scope set PM updates Project SharePoint site with Status and Artifacts

Development Developers document design in the System Design Document (SDD)

SDD

Initiation Planning & Requirements Design Development Integration & Test Deployment

SDF: Development (Waterfall) PM manages development against baselined Requirements and SDD

Requirements and SDD PM manages updates to project documentation PM provides Status Reports during weekly recurring IPTs

Updated Req. and SDD Tester builds Test Cases & Scripts based on the finalized requirements PM completes Test Readiness Review (TRR) Checklist PM schedules a TRR for the next CIO IPT PM briefs TRR to IPT

TRR (IPT)

Test Cases PM updates Project SharePoint site with Status and Artifacts

Integration & Test

Test Readiness Checklist

Initiation Planning & Requirements Design Development Integration & Test

SDF: Integration & Test (Waterfall) System and Security Testing begins

Tester updates Test Cases for User Acceptance Testing (UAT)

Pass Fail

Bug/Defect Fixes by Development Team

Test Results PM schedules UAT

Updated Test Cases Bug/Defect Fixes by Development Team PM manages UAT

UAT

Acceptance N PM completes Deployment Readiness Review (DRR) Checklist Y PM schedules DRR with IPT

Deployment Go to Slide 12

Request Initiation Planning & Requirements Design Development Integration & Test Deployment Closeout

Pass Fail PM briefs DRR to IPT

Deployment Review (IPT)

DRR Checklist

Agile Development

SDF: Design, Develop, Test (Agile)

Pass Fail Project Team continuously engages stakeholders to refine and capture required functionality Sprint Demo & Incremental Release Project Team conducts Sprint 0 – creating skeleton design of the solution Business Analyst decomposes requirements into User Stories and establishes Product Backlog Developers work against items in Sprint backlog

Tester prepares Test Cases/Scripts for each User Story Conduct Component and Security Testing Project Team conducts final UAT or demo

Test Results PM completes Deployment Readiness Review (DRR) Checklist

Additional Reqts P F

Request Initiation Planning & Requirements Design Development Integration & Test Deployment Closeout

Product Owner determines scope of upcoming Sprint

Y

DRR Checklist

PM briefs DRR to IPT

Deployment Review (IPT)

Updated Req. and SDD

SDF: Deployment PM/Requestor finalizes Operations & Maintenance Plan and Training Plan PM schedules Deployment

CCB

Approval PM presents O&M Plan and Training Documents to CIO IPT PM conducts planning and coordinates installation

Y

O&M and Training Plan Project deployed to production and handed off to O&M

O&M

Go-Live Review (IPT)

Initiation Planning & Requirements Design Development Integration & Test Deployment

PM submits Change Request (CR), Deployment Plan, Testing Results to Change Control Board (CCB)

SDF: Closeout PM/Requestor conducts Lessons Learned meeting with project team PM prepares Project Closeout Form PM presents Project Closeout Form to IPT PM updates and finalizes Project SharePoint site with Status and Artifacts

Project Closeout Form Project results presented to TAB

SDF Phase Complete PM formally releases OCIO resources back to respective directorates

Post Implementation Review

Initiation Planning & Requirements Design Development Integration & Test

Project Ends

Maintenance Phase Operations & Maintenance (O&M)

Maintenance Lifecycle

O&M Plan

Service Level Agreements (SLA)

Application Corrections / Bug Fix

Refresh/Updates/Patches

User/System Administration

Technical Maintenance

Disposition Plan

O&M Manager Assigned

Disposition Approval (TAB)

Delivery (SDF) Disposition

Quarterly Status Reports (TAB)

Recurring User Training The final output of the SDF is the Operations and Maintenance Plan, which dictates the system’s architecture, configurations, roles, ownership, and procedures for upgrades, patches, and change requests. This document outlines the activities and management structure of the application during the Maintenance Phase.

The Maintenance phase of the project is facilitated by an assigned O&M Manager from within the OCIO. The O&M Manager oversees aspects of the application’s uptime, bug fixes, patches, upgrades, maintenance, reporting and user training.

Any request for additional functionality of the project would have to be managed as a new project request, and the final Output of the SDF would be to update the applications current O&M Plan and a code merge.

At the stage when an application is identified for retirement, the O&M Manager will draft the Disposition Plan, and brief it to the TAB. On acceptance, the Maintenance phase will end, and the Disposition plan will begin.

Disposition Phase Solution Retirement

Maintenance Lifecycle

Disposition Plan

Project Management Plan

PM Assigned

PMP Approval (IPT) Delivery (SDF) Disposition The Final phase of any application’s lifecycle is the Disposition Phase. The disposition phase manages the formal retirement of the system. The disposition shall be managed similar to a regular project (according to the SDF), with or without a replacement system, with the Disposition Plan acting as the project’s charter. Once the system is identified as a candidate for retirement, the Disposition Plan drafted by the O&M Manager will outline the required activities in order to successfully retire/replace the application.

Once the Disposition Plan is approved by the TAB, a PM is assigned, and creates a Project Management Plan which supports the activities described in the Disposition Plan.

On approval from the IPT, the PM manages assigned project resources against the PMP to retire/replace the system. This effort can be a part of, or in conjunction with, another project replacing the legacy system.

Once complete and the application is retired, the PM will update the project SharePoint site, and archive project related documentation.

Resources Assigned

Project Retirement image2.png image1.png