1. Comprehensive Delivery Process
State of Connecticut
Department of Information Technology (DOIT)
Comprehensive Delivery Process
SDM Lite
Business Requirements Phase Training

2. Agenda
Overview of SDM Lite
Governance
Purpose of Business Requirements Phase
Business Requirements Phase Deliverables and Their Owners
Team Members
Business Requirements Phase Activities

3. Governance – The Project Steering Committee (PSC)
Who are the typical PSC members?
Agency Commissioners or Designee
Executive Director or Designee
Divisional Directors
Not typically members of the Project Team wheel
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.

4. Business Requirements Phase Purpose
The purpose of the Business Requirements Phase is to:
Define to those things that must happen in order for the new solution to be declared usable by the business.
Evaluate solution alternatives
Document Technical Requirements
Recommend a Solution to the Business Issue
The phase begins with the definition of business requirements (owned by the Business Team). The
business requirements describe functional requirements needed to support the business (e.g. organizational
roles, process & procedure changes, system features and data). Non-Functional requirements needed to
support the business are also defined (e.g. system performance, security, accessibility, maintainability).
Once the business requirements have been defined, the technical requirements are subsequently
defined. Definition of technical requirements is owned by the Technology team. The technical requirements
describe those things that technically must be established in order for the business requirements to be
achieved.
Solution alternatives analysis is performed and a recommended solution is identified by the project team. 4

5. SDM Lite v2.03 Deliverables/Events by Phase
Business
Issue
Business
Requirements
Design
Construction
Testing
Phase Kickoff Meeting
Project Management Plan
Project Profile
Detailed Schedule for Next-Phase
Phase-End Decision-Point Meeting
Bus. and Tech. Rqmts Document
Solution Alternatives Document
Deployment Strategy & Plan
Detailed Schedule for Next-Phase
Phase-End Decision Point Meeting
System Design Document
System Security Profile
System Design Signoff - TRB
System Design Signoff - PSC
Test Strategy & Plan
Detailed Schedule for Next-Phase
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
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
Implementation
Post-Implementation
Technology Solution Deployment
Approved Production Turnover
Phase-End Decision Point Meeting
Project Summary
Project Shutdown
Deliverables Updated in Multiple Phases:
Project Management Plan, Cost Benefit Analysis

6. (WBS)

7. Key Deliverables Created in the Business Requirements Phase
Team Lead Deliverables:
Business & Technical Requirements Document,
Technical Requirements Document,
Solution Alternatives Document
Project Management Deliverables:
Cost-Benefit Analysis (Updated),
Detailed Phase Schedule,
Phase-End Decision Point Presentation,
Project Management Plan (Updated),
Project Team Wheel (Updated)

8. Phase Activity Numbers
Business Requirements Phase Deliverable Snapshot
Phase Activity Numbers
Team Lead Deliverables
Requirement
Owner 01 02 03 04 05
3rd Party Services Evaluation Criteria
If Applicable
Procurement Lead C
3rd Party Services Procurement Activity
Business Requirements Workbook
Mandatory
Business Requirements Lead
Technical Requirements Workbook
Technology Manager
C/S
Solution Alternatives Document and Recommendation
Business Manager
N/S
Phase-End Decision Point Presentation S
Project Management Plan Updated R

9. Current Phase: Business Requirements
Project Steering Committee (PSC)
Name / Agency
Current Phase: Business Requirements
* Staffed from the Business
* Name Required
Business Process Lead
* Name Required
Deployment Lead
* TBD
UAT Lead
BUSINESS PARTNERS
* <Name Required>
Business Manager
* Name Required
Business Requirements
Lead
* Name(s) Required
Business SME Areas
Name Required
Executive Sponsor
Name Required
Development Lead
Name Required
Infrastructure Lead
<Name Required>
Technology Manager
TECHNOLOGY
PARTNERS
TBD
Test Lead
Name Required
Network Lead
Name Required
Security 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 create any new role names; All role names are standardized within the SDM framework
Support/Consulting Roles:
Enterprise Architect: Name Required
Business Division Director: Name Required
Procurement Lead (Optional)
Financial Advisor: (Optional)

10. Business Requirements Phase Roles & Responsibilities
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;
Responsible for the updating the Cost/Benefit Analysis;
Responsible for the completed Solution Alternatives Document;
Provides project plan updates for all Business activities and deliverables;
Attends/Participates in all Phase-End Decision Point Meetings : . 10

11. Business Requirements Phase Roles & Responsibilities
Business Process Lead (Business Role)
Responsible for creating the Business Process Model (if required);
Provides general business process consultation to the project team;
Business Requirements Lead (Business Role)
Creates and maintains the Functional Requirements Workbook;
Creates and maintains the Non-Functional Requirements Workbook;
Responsible for Business Requirements validation in POC (if required);
Provides general business requirements consultation to the project team;
Provides input and revision to the Deployment Strategy & Plan
Business Subject Matter Experts (SMEs) - (Business Role)
Provides business area consultation to the business team as needed to assist with business deliverable review and creation;
Deployment Lead (Business Role)
Creates and owns the Deployment Strategy & Plan document; : . 11

12. Business Requirements Phase Roles & Responsibilities
Enterprise Architect - (Technology Role)
Responsible for ensuring that EWTA requirements are addressed with the solution;
Contributes architecture requirements to the Technical Requirements Workbook;
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;
Responsible for contributing infrastructure requirements to the Technical Requirements Workbook;
Financial Advisor (Finance Role)
Provides budget consultation to the project team as needed;
Procurement Lead (Technology Role)
Responsible for determining the appropriate procurement path for the project (if required);
Responsible for managing the procurement process on behalf of the project team (if required);
Provides procurement consultation to the project team as needed; : . 12

13. Business Requirements Phase Roles & Responsibilities
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 - (Technology Role)
Contributes security requirements to the Technical Requirements Workbook;
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 the technology solution deployment;
Creates all Phase-Kickoff Meeting presentations; Facilitates all Phase Kickoff Meetings;
Creates and maintains the Project Team Wheel;
Responsible for updating 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 Proof of Concept (POC) execution (if required); : . 13

14. Activity 2.01: Procure 3rd Party Services
This activity and deliverable is only needed when there is a need to procure additional staffing support through a third party vendor or contractor.
There may be circumstances that require the State to procure 3rd party human resource services to own full or partial development and implementation of a custom solution (i.e., staff augmentation).
If the project requires the procurement of 3rd party human resource services to support the project delivery, this activity is performed.
The Procurement Procedure Manual must be referenced and fully utilized during this SDM activity. The Procurement Procedure Manual provides detailed, step-by-step process descriptions to guide the procurement process. The Procurement Procedural Manual is located on the SDM website either under the Business Requirements Phase Deliverables, or under the Reference Materials link.
Based on the nature of the project, the Procurement Lead will decide which procurement path is most appropriate for securing external services. Contact DOIT’s Procurement office as soon as possible. The various procurement paths include:
Master Agreement – Utilize existing Master Agreement to procure 3rd party human resources.
Request for Proposal (RFP) - For large projects that involve use of 3rd party solutions to solve a business problem faced by an agency, a Request for Proposals (RFP) process is used. The RFP process provides the ability to evaluate and weigh the quality of proposed solutions. The RFP process is not normally used for SDM Lite projects, except in unusual circumstances.
Invitation to Bid (ITB) - Contracts for readily identifiable goods or services (i.e., those for which specific requirements may be developed) are established using an Invitation to Bid (ITB) process. The ITB path provides less ability to weigh 3rd party solution proposals, and a non-negotiable contract is awarded to the lowest qualified and responsible bidder.
1Sole-Source - Sole source product suppliers are an option when an emergency or unusual market condition exists; such as when a product or service is only available from one source.
The Proposal Review Team may be required to evaluate the 3rd party vendor alternatives.

15. Activity 2.01: Procure 3rd Party Services (continued)
This activity and deliverable is only needed when there is a need to procure additional staffing support through a third party vendor or contractor. (continued)
This Activity Produces the Following:
Review of Team Member Roles and Responsibilities;
Review of overall Project Goals, Objectives, Scope, and Benefits;
Review of phase Goals, Objectives, Tasks, and Responsibilities;
Review of ‘Lessons Learned’ from previous projects;
Review of Team Procedures and Standards; and 15

16. Activity 2.02: Document the Business Requirements
Purpose:
The purpose of this activity is to document business requirements.
All impacted business areas must be involved in the project to contribute their respective business requirements. Business Requirements documentation includes the definition of functional requirements (e.g. the capabilities that the system must provide to support the execution of the business process) as well as non-functional requirements (e.g. system performance, security, availability, legal and regulatory data retention, data conversion).
This Activity Produces the Following:
Functional Requirements
Security Requirements
Legal/Regulatory Requirements
Performance Requirements
Conversion Requirements
Data Retention Requirements
System Availability Requirements
FOIA and HIPAA Assessments 16

17. Activity 2.03: Document the Technical Requirements
Purpose:
The purpose of this activity is to document technical requirements which must be addressed to support the defined business requirements of the new solution.
The DOIT Enterprise-Wide Technical Architecture (EWTA) describes the general architecture requirements that a technical solution must align with. Technical solutions must align with EWTA whether the solution is custom developed or purchased, hosted at DOIT or hosted outside of DOIT.
This Activity Produces the Following:
Architecture Requirements
Architecture/Infrastructure Upgrade Requirements
Network Requirements
Server Requirements
Database Requirements
Desktop Requirements
Application Hosting Requirements
Directory & Messaging Requirements
Application/Data Interface Requirements
User/Transaction Volume Requirements 17

18. Activity 2.04: Document Solution Alternatives
Purpose:
Evaluate the options for custom-development solutions, specifically.
The solution alternatives might include modifying/extending existing applications, writing new applications, or a combination of the two. A sample “pattern” of how custom developed solution alternatives might be captured:
Alternative 1 – Modify legacy App X, Write new Application Y
Alternative 2 – Modify legacy App X, Modify legacy App Z
Alternative 3 – Modify legacy App Z and add web front-end
This Activity Produces the Following:
Solution Alternatives Document 18

19. Activity 2.05: Conduct Phase-End Decision Point Meeting
Purpose:
The purpose of this activity is to obtain direction from the Project Steering Committee (PSC) with regard to how the project team should proceed based on the findings of the current phase.
The output from the Decision Point Meeting for a project results in one of the following decisions:
A “Go” decision – This commits the required resources to proceed into the Design Phase;
A “No-Go” decision – This occurs if the project is not economically or strategically feasible; or,
A “Redirect” decision – This occurs if the project has potential but is not yet achievable.
Minimum Suggested Attendees for the Phase-End Decision Point Meeting:
Executive Sponsor,
PSC,
Technology Manager, and
Business Manager
This Activity Produces the Following:
Business Requirements Phase-end Decision Point Meeting Presentation,
Business Requirements Phase-end Decision Point Meeting,
PSC “Go”, “No-Go”, or “Redirect” Decision,

20. Continuous SDM Support & Training
SDM Resources:
SDM website:
SDM Overview & Training
SDM Sample Deliverables
SDM Box:
Inbox is reviewed on a regular basis (e.g., weekly, bi-weekly, etc.)
Will add input for ‘FAQ’ section of website
PMO Team will respond to feedback
The purpose of the System Development Methodology (SDM) is to establish procedures, practices, and guidelines governing the initiation, concept development, planning, requirements analysis, design, development, integration and test, implementation, and operations, maintenance and disposition of information systems (IS) within the State of Connecticut. 
SDM Continuing Education:
SDM open communication forums
SDM Brown Bags
Specific discussion on ‘hot’ SDM topics
Scheduled assistance as requested

21. The PMO Team also has a group telephone # 860-622-2085.
PMO Team Members
Please contact the PMO Team with any questions that you have. The PMO Team will be reviewing the SDM Feedback Mailbox on a regular basis.
PMO
PMO Team Members:
Lois Bryant  
Tricia Johnson, PMO Director  
Dawn Keiper
Jim Rutushni
Lori Violette
Larry Williford   
The PMO Team also has a group telephone #  
If you receive the voic , please leave a message as the voic will be checked on a regular basis.
PMO Web site: 21

22. + Agencies SDM Successful Projects Thank you for attending!=
Agencies
SDM
Successful
Projects
Thank you for attending!
Any questions, comments or suggestions?