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 Output Recurring Activity

Phase/Activity Input Control Gate Termination Point

2
 Standard Operating Procedures (SOP)
Solution Delivery Framework (SDF)

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 systems 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 applications 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
projects 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.
Project Manager Assigned Project Manager Assigned

Delivery (SDF) Maintenance (O&M) Disposition

Retirement

3
 SDF: Request
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Requestor develops BAM/Requestor Y

IPT BAM/Requestor Request
1 Project Request Form presents PRF to CIO
Approval presents PRF to TAB Termination
(PRF) IPT

Project Request Form PRF Review (IPT) PRF Review (TAB) Termination

CIO IPT provides input BAM/Requestor

BAM/Requestor Y N
and vets Concept develops Concept TAB
presents Concept
Proposal including Proposal elaborating Approval
Proposal to TAB
budget upon PRF
Concept Review (TAB) Concept Proposal

N TAB Approved, Active PM updates Project

Approval SharePoint site with
status and Artifacts Initiation
OCIO PM Assigned
Approved, Pending

Project
PM updates Project
SharePoint site with placed in
Approved
Status and Artifacts
Backlog 4
 SDF: Initiation
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Concept Proposal
Project Team
PM conducts project
PM identifies Project establishes scope and PM prepares the
1 kick-off meeting with
Team members defines high-level Project Charter
Project Team
requirements
Project Charter

PM updates Project
Requirements & PM presents Project PMO Manager reviews
Planning SharePoint site with
status and artifacts Charter to CIO IPT Project Charter

Initiation Review (IPT)

5
 SDF: Planning & Requirements
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Business analysts
conducts requirements
Project Charter
PM assigns elaboration sessions
PM prepares PMP and development of Project team
1
requirements to documents detailed
Tailoring Guide
business analysts and requirements
technical SMEs
PMP, Tailoring Guide Technical SMEs Requirements Document
develop non-functional
requirements

N
PM presents
PM initiates Y IPT Requirements
PM develops schedule Approval
procurement activities Document and
schedule to IPT
Schedule Requirements Review (IPT)

Go to
Slide
Waterfall Development 7
Design
PM updates Project
SharePoint site with Development Go to
Status and Artifacts Type? Slide
Design,
11
Develop,
Agile Development Test 6
Waterfall Development
 SDF: Design (Waterfall)
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Requirements Document
PM manages Developers document
PM schedules Design
1 development of system design in the System
Review for next CIO
design to meet Design Document
IPT
requirements (SDD)
SDD

Requirements and
PM updates Project
Design Documentation PM briefs SDD to CIO
SharePoint site with baselined and IPT
Status and Artifacts development scope set
Design Review

Development

8
 SDF: Development (Waterfall)
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Requirements and SDD

PM manages
PM manages updates PM provides Status
1 development against to project
baselined Reports during weekly
documentation recurring IPTs
Requirements and SDD
Updated Req. and SDD

Tester builds Test

PM completes Test
PM schedules a TRR Cases & Scripts based
Readiness Review
for the next CIO IPT on the finalized
(TRR) Checklist
requirements
Test Readiness Checklist Test Cases

PM updates Project
PM briefs TRR to IPT SharePoint site with
Status and Artifacts Integration &
Test
TRR (IPT)

9
 SDF: Integration & Test (Waterfall)
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Test Cases
Pass Tester updates Test
Pass
1 System and Security Cases for User
/ PM schedules UAT
Testing begins Acceptance Testing
Fail
(UAT)
Test Results Updated Test Cases
Fail

Bug/Defect Fixes by
Development Team PM manages UAT

PM completes
Y UAT
PM schedules DRR Deployment Bug/Defect Fixes by
Acceptance
with IPT Readiness Review Development Team
(DRR) Checklist
DRR Checklist
N

Go to
Slide
PM briefs DRR to IPT 12
Deployment
Deployment Review (IPT) 10
Agile Development
 SDF: Design, Develop, Test (Agile)
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

Project Team
Business Analyst
Project Team continuously
decomposes Product Owner
conducts Sprint 0 Developers work engages
requirements into determines scope of
1 creating skeleton against items in stakeholders to
User Stories and upcoming Sprint
design of the Sprint backlog refine and capture
establishes Product
solution required
Backlog
functionality
Updated Req. and SDD

Y F

Pass Tester prepares Test

Additional Sprint Demo & P Conduct Component
/ Cases/Scripts for
Reqts Incremental Release and Security Testing
Fail each User Story

Test Results Test Cases

N

PM completes
Project Team
Deployment
conducts final UAT PM briefs DRR to IPT
Readiness Review
or demo Deployment
(DRR) Checklist
DRR Checklist Deployment Review (IPT)

12
 SDF: Deployment
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

N
PM
PM submits
submits Change
Change
PM/Requestor PM presents O&M Request (CR),
finalizes Operations PM schedules Plan and Training Deployment
Deployment Plan,
Plan, CCB
1
& Maintenance Plan Deployment Documents to CIO Testing
Testing Results
Results to
to Approval
and Training Plan IPT Change
Change Control
Control Board
Board
(CCB)
(CCB)
O&M and Training Plan Go-Live Review (IPT)
Y

PM conducts
Project deployed to
planning and
production and
O&M coordinates
handed off to O&M
installation

13
 SDF: Closeout
Planning & Integration &
Request Initiation Design Development Deployment Closeout
Requirements Test

PM/Requestor
1 conducts Lessons PM prepares Project PM presents Project
Learned meeting Closeout Form Closeout Form to IPT
with project team
Project Closeout Form Post Implementation Review

PM updates and PM formally releases

Project results finalizes Project OCIO resources back
presented to TAB SharePoint site with to respective
Status and Artifacts directorates

SDF Phase
Complete

Project Ends

14
 Maintenance Phase
Operations & Maintenance (O&M)
Delivery (SDF)
O&M Plan
O&M Manager Assigned
Maintenance
Lifecycle Service Level Agreements (SLA)
Application Corrections / Bug Fix
Refresh/Updates/Patches
User/System Administration
Technical Maintenance
Quarterly Status Reports (TAB)
Recurring User Training
Disposition Plan
Disposition Approval (TAB)
Disposition
The final output of the SDF is the Operations and
Maintenance Plan, which dictates the systems
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
applications 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.
15
 Disposition Phase
Solution Retirement

Delivery (SDF) The Final phase of any applications 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
Maintenance replacement system, with the Disposition Plan acting as the
Lifecycle projects charter. Once the system is identified as a candidate
for retirement, the Disposition Plan drafted by the O&M
Disposition Plan
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

PM Assigned
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

Project Management Plan 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.

PMP Approval (IPT) Once complete and the application is retired, the PM will
update the project SharePoint site, and archive project
related documentation.

Resources Assigned

Disposition

Project Retirement 16