SDF Activities & Deliverables By Phase

Any work that prompts reallocation of human and capital resources to grow or transform our business must proceed through the Idea Management to Annual Operating Plan (AOP) process flow. Approved Ideas flow to a Discovery process, where further information is elicited about the objectives, expected value with proposed metrics, preliminary scope, business needs and requirements, rough order of magnitude (ROM) estimates of costs and resources, funding, and identification of lead and support groups. Approved work is prioritized with the portfolio and optimized with resource capacity. Approved work for the current FY schedule will be included in the AOP.

Note that the following phases may be sequential or iterative depending on the methodology used. All templates must be adapted to the unique needs and risk of the project. Based on the needs/risk of the project, some templates may not be required. Tools may be helpful resources. The following list of templates and tools is not exhaustive. Please review items available in the Service Delivery Framework Tools Matrix (SDF Matrix). If you need a template or tool not shown here and neither in the SDF Matrix, first check with the PMO to see if they have additional resources. Otherwise, you may need to create new templates and tools to meet the needs of your project. If a new template or tool is created, please forward it to the PMO for possible inclusion to the SDF Matrix.

Note: Some documentation on this page may be restricted and require authorized access.

Phase 0: Discovery

In partnership with stakeholders, elicit information about the objectives, expected value with proposed metrics, preliminary scope, business needs and requirements, rough order of magnitude (ROM) estimates of costs and resources, funding.

Preliminary Scope Statement	, ,
Procurement Requirements	, ,
Project Funding Needs	, ,
Business Requirements	, ,
Benefit Realization Plan (Qualified)	, ,
Is this a Project? Use Project Calculator	, ,
Metric Data Sheet (for selected metrics that will be tracked throughout project)
Risk Assessment	, ,

Phase 1: Initiation

Phase 2: Planning

Partnering with stakeholders, define the scope (work to be done) of the project and scope of the product to be developed.

Vision, Roadmap
Preliminary Scope Statement	, ,
Milestone Tracker
Deliverable Expectation Document (DED)	,
Deliverables Checklist	, ,
Work Breakdown Structure (WBS)	, ,
WBS Dictionary	,
Requirements Document
Requirements Traceability Matrix, Requirements Tracking Template
Project Change Control Plan, Project Change Request Form,  PMO Change Log	, ,
Timeline
Schedule Plan	,
PMBOK Compliant Schedule (must add product related activities/tasks, activity attributes, and estimates of work effort and duration)
Time Estimation tool
Estimation Tool for Activity and Small Project
Budget Plan
Resource Plan, Roles and Responsibility Matrix, RASCI	,
Quality Assurance Plan, Lessons Learned Template
Communication Plan	,
Communication Log	, ,
Stakeholder Engagement Plan
Organizational Change Management Plan
Procurement Plan
Risk Plan, Risk Log
Issue Management Plan, Issue/Decision Log	,
Knowledge Management Plan
Risk adjusted performance baseline
Kick-off Meeting, Agenda, PMO Project Meeting Notes Template	, ,

Phase 3: Requirements Analysis

Partnering with the stakeholders, define, analyze, and prioritize requirements, including system features, user experience, logical condition, and process flows.

Document As-Is and To-Be Business Flow and Process	,
Master Data Management (MDM) review	, ,
Lessons Learned Team Foundation Server (TFS) project creation
Product Documentation (product web site, AIS, service catalog, etc.)	, ,
Persona Templates
User Requirements
System Requirements
Quality Requirements
Database Design Needs, Database Plan
Web design needs, Web Plan
Infrastructure Requirements
Identify server setups and configuration changes, including server access, ports and firewalls
Job control, network files/folders
Review technical documentation of proposed third party solutions for compatibility
Security Checklist, Security Requirements, Security Plan	, ,
MOU Template
Standards Exemption Request
Assess needs and/or changes to 1820
Project Team Needs
Updates to documents from prior phases	, ,
Stage Gate Review (requirements review and sign off, obtain approval to proceed)

Phase 4: Design

Using prototypes and customer feedback design system, including system features, data model, logical conditions, process flow, user experience, quality expectations, and future expansion.

Data Model Document
Create Dev and Test Environments (server setups and/or configuration changes)
System Architecture and Infrastructure Design
Procurement documents
Design Review and signoff

Phase 5: Development

Build the product, including programming code, and conduct initial unit testing for each module.

Update file layouts, flowcharts, version history, and documents from prior phases	, ,
User Interfaces and Source Code
Refactor (simplify, standardize, clean-up) source code
Job Control setup or changes
Request test server setup or configuration changes
Test Scenario
Test and Validation Plan
Test Case/s
Prepare testing environment and testing tools for user acceptance testing (UAT)
Team Development
Implementation Plan: Deployment Instruction, Rollback Plan	, ,
Disaster Recovery Plan	, ,
Tier 1 Knowledge Transfer	, ,
Knowledge Transfer Plan	,
Development Review (validate quality of the solution)	, ,

Phase 6: integration, test, acceptance

Complete integration and system testing of all modules, document all known issues, place source code in source control. Users conducts UAT. Partnering with stakeholders, create user support documentation.

Update file layouts, flowcharts, version history, and documents from prior phases	, ,
User Training Documents
Support Staff Documentation (Help Desk Scripts)
Production Packages versioned in TFS	, ,
Update Configuration Management Database	, ,
Load balancer
Success/Failure notification, Lessons Learned, Status Reporting	, ,
Formal Quality Review
Stage Gate Review: Approval to promote system to production
Create Staging and Prod environment

Phase 7: Implementation – Deployment - Decommission

Phase 8: Closeout

Project team will verify all documentation and project work is complete.

Updates to all prior documentation	, ,
Product documentation completed and stored in appropriate repository Update AIS Update Service Delivery Catalog	, ,
Update Accomplishment Log	, ,
Project Closure Form (acceptance of project deliverables)	, ,
Project Closure Summary
Procurement closeout, finalize budget, staff augmentation contract closeout
CRQ Review with Deliverable Checklist Completed	, ,
Customer Satisfaction Survey
Compile Lessons Learned	, ,
Update procedures, templates, and tools for continued improvement	, ,
Release of resources	, ,
Project site with project documents archived	, ,
CRQ Closed Out	, ,

Maintenance Release Activity