comprehensive delivery process sdm lite business issue phase training state of connecticut...

Comprehensive Delivery Process

SDM Lite Business Issue Phase Training

State of Connecticut Department of Information Technology (DOIT)

SDM v2.0 Business Issue Phase Training Confidential - Internal Use Only


Agenda

Overview of SDM Lite Governance Purpose of Business Issue PhaseBusiness Issue Phase Deliverables and Their Owners Team MembersBusiness Issue 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

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.



Business Issue Phase PurposeThe Purpose of the Business Issue Phase is to:

• Identify and validate an opportunity to improve business accomplishments or to identify a deficiency related to a business need;• Formally initiate an project;• Establish the Project Organization;• Identify significant assumptions and constraints which apply to the business need;• Explore alternative concepts and methods to satisfy the business need, producing a recommended solution approach based upon defined constraints (e.g. amount of dollars available, timeframe by which a solution is needed).

The Business Issue phase is usually the shortest phase within the project life-cycle. The duration of this

phase should take no longer than 3 weeks, unless an RFI is deemed necessary within the phase.

The Project Profile is completed and approved. The Project Profile should provide a general project

description including a statement of the business problem, high-level requirements of the desired solution, the

envisioned organizational impact (e.g. Agencies that are impacted), and budget and schedule constraints

provided by the Business (e.g. the solution to the problem can cost no more than $200,000, and is required

within the next 8 months).



(WBS)Business

IssuePhase

1.043Conduct Phase-EndDecision Point

Meeting

Create the Phase-EndDecision Point

Meeting Presentation

Distribute the Project Profile to the PSC

1.02 Create the Project Management

Plan

Document the Project Organization

Create the Project Descritption

Create the Project Issues Log

Create the Cost-Benefit Analysis (CBA)

Create the Detailed Project Schedule forThe Business Issues and Business Requirements Phases

Establish the Scope Statement

Conduct the Phase-End Decision Point

Meeting

ExecuteCommunication

Plan

1.01 Kick-off the Business Issue

Phase

Create the Project Kick-Off

Presentation

Review TeamProcedures and Standards

Review Lessons Learned

From Prior Projects

Review Business Issue Phase Goals, Objectives, Tasks, and Responsibilities

Review Overall Project Goals, Objectives, Scope, and Benefits

Review Team Member Roles & Responsibilities

Create the Communications Plan

Document External Project Considerations

Create the Risk Management Plan

Create the Project Budget Summary

Create the Project Profile

Plan Remaining Phases – Update SDM Lite Project Management Plan

Compare/Contrast Viable Solution Approaches

Organizational Standards and Policies

Develop High-Level Deployment Strategy



Key Deliverables Created in the Business Issue Phase

Team Lead Deliverables:

Project Profile,

Project Steering Committee,

Solution Approach Document

Project Management Deliverables:

Cost-Benefit Analysis,

Detailed Phase Schedule,

Phase-End Decision Point Presentation,

Phase Kickoff Presentation

Project Management Plan,

Project Team Wheel



Business Issue Phase Deliverable Snapshot

Phase Activity Numbers

Team Lead Deliverables Requirement Owner 01 02 03

Phase Kick-off Presentation Mandatory Technology Manager N/C

Project Management Plan Mandatory Technology Manager N

DOIT Project Profile Mandatory Business Manager N/C/S

Phase-End Decision Point Presentation Mandatory Technology Manager N/C/S



Project Steering Committee (PSC)Name / AgencyName / Agency

TECHNOLOGY PARTNERS

BUSINESS PARTNERS

* Name RequiredBusiness Manager

Name RequiredTechnology Manager

Name Required Executive Sponsor

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

* Staffed from the Business

Current Phase: Business Issue

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



Business Division Director (Technology Role) Assists the Executive Sponsor with establishing a Project Steering Committee, and securing resources for the team, as needed. 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 completed Project Profile; Responsible for the completed Solution Approach Document; Responsible for the completed Request for Information (RFI), if required; Responsible for the Creating the Cost/Benefit Analysis; Provides project plan updates for all Business activities and deliverables; Attends/Participates in all Phase-End Decision Point Meetings

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

Business Issue Phase Roles and 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.

Technology Manager (Technology Role) Responsible for the overall coordination and delivery of all Business and Technology deliverables; Creates all Phase-Kickoff Meeting presentations; Facilitates all Phase Kickoff Meetings; Creates and maintains the Project Team Wheel; Responsible for executing all Decision Point Meetings with the Project Steering Committee (PSC); Responsible for managing project risks, issues, and key assumptions; Responsible for creating and maintaining 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;

Business Issue Phase Roles and Responsibilities



Activity 1.01: Initiate the ProjectPurpose:The purpose of this activity is to align the project team on the goals, objectives, and deliverables of the overall project, as well as those which are specific to the Business Issue Phase.

During the Business Issue Phase Kick-off Meeting, communicate the steps, processes, milestones, activities, and responsibilities necessary for the success of the project. Establish project success criteria. Establish and communicate a documentation management process. Establish regularly scheduled project status meeting and status reporting requirements. Utilize the SDM Lite Project Management Plan and update in every phase of the project.

Minimum suggested attendees for the Business Issue Phase Kickoff Meeting include: Executive Sponsor, Business Manager, and Technology Manager.

This Activity Produces the Following:

Project Kick-off Presentation ,

Team Member Roles & Responsibilities ,

Overall Project Goals, Objectives, Scope, and Benefits ,

Business Issue Phase Goals, Objectives, Tasks, and Responsibilities

Team Procedures Standards



Activity 1.02: Create the Project Management PlanPurpose:Create the SDM Lite Project Management Plan that will guide the execution of the project and provide a basis for future status reporting.

The Project Management Plan should include the following plan components:Project Organization, Project Description, Project Scope Statement, Project Detailed Schedule, Project Timeline, Solution Approach, Cost Benefit Analysis, Project Budget Summary, Communication Plan, External Project Considerations, Issues Log, Risk Management Plan, Critical Success Factors, Key Planning Assumptions/Constraints, Organizational Standards and PolicesHigh Level –General Deployment Strategy

Once the Project Management Plan is established, it is updated within each phase before conducting the Phase-End Decision Point meeting with the PSC.


Project Management Plan;

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



Activity 1.03: Conduct Phase End Decision Point Meeting

Purpose:The purpose of this activity is to report a recommended solution approach, estimated cost and delivery timeline, and established resources for the project. The project team seeks to obtain a “Go,” “No-Go,” or “Redirect” decision from the Project Steering Committee (PSC). 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 Business Requirements Phase;A “No-Go” decision – This occurs if the initiative is not economically or strategically feasible; or, A “Redirect” decision – This occurs if the initiative has potential but is not yet achievable.Required attendees are the Executive Sponsor, the PSC, Technology Manager, and the Business Manager. Other project team members should attend as needed.

If the approved solution involves a technology component, then the Project Profile must be completed and signed by the Executive Sponsor during the Phase-End Decision Point Meeting. The Project Profile would subsequently be presented to the Project Profile Committee for review, approval, and formal initiation of an SDM project.


Project Profile



Continuous SDM Support & Training

SDM Resources:

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

SDM Overview & Training

SDM Sample Deliverables

SDM Email Box:

[email protected]

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 feedbackSDM Continuing Education:

SDM open communication forums

SDM Brown Bags

Specific discussion on ‘hot’ SDM topics

Scheduled assistance as requested

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.



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 business issue phase training state of connecticut...

Documents

business issue phase

phase slide

business need

business area

business strategies

business accomplishments

project organization

sdm v2