System Development System Development MethodologyMethodology

““Lite”Lite”

The SDM Lite Team!The SDM Lite Team!Who would have ever thought this would be a good team?

Jim A.K.A. “Popeye”

Rutushni Team Leader

Ron A.K. A. ‘”The Politician”

San Angelo

Len A.K.A. “Jarhead”

Smith

JeanneA.K.A. “The Doctor”

Lee

Keith A.K.A. “ The Farmer”

McHugh

Benefits of a Standard MethodologyBenefits of a Standard Methodology

How does a standard methodology Benefit Us?

• Saves Time and Money

• We will deliver projects successfully

• Effective planning will enable us to achieve agreed upon objectives

• Our resources will be coordinated

• Our risks will be identified and managed

• We will achieve an agreed upon outcome

What are the Benefits of SDM?What are the Benefits of SDM?1. State agencies will utilize the same process for

managing technology projects within established SDM Lite criteria.

2. Allows Project Steering Committees to understand what phase a particular project is in and also to identify that the goals of the project are being met according to the Project Plan.

3. Improves the ability of a Project Manager to clearly understand the Goals and Objectives of an Executive Sponsor.

SDM LITESDM LITECharacteristicsCharacteristics

• SDM Lite Characteristics Check List Form - helps Technology Managers understand SDM Lite criteria. It answers the question: Does my project qualify as a SDM Lite project?

• SDM Lite is designed to support projects that are smaller in scope and are lower in risk, complexity, cost or duration then those that meet the criteria of SDM Standard.

• Projects using SDM Lite can choose to include any of the deliverables that are part of the SDM Standard if that helps manage and improve the project’s outcomes.

General Project CharacteristicsGeneral Project Characteristics (Requires that all apply, regardless of project type).(Requires that all apply, regardless of project type).

• Estimated implementation costs are less than $400,000 Including hardware, software, and all other resource costs, and

• Estimated duration (calendar time) is less than or equal to six (6) months, and

• Limited to one (1) agency (not including DOIT if hosting service is required) and

• Your product / solution is compliant with the Enterprise-Wide Technical Architecture standards and patterns – or – you have an already approved exception by Technology Review Board for your use of a non-standard platform.

Applications Projects, OnlyApplications Projects, Only (Requires that all apply)(Requires that all apply)

• Your application requires data from no more than one (1) other application.

• Your application requires only one (1) dedicated database

Operations Projects, Only Operations Projects, Only (Requires that one be checked)(Requires that one be checked)

• Network Projects - Network Refreshes, New WAN/Router Rollouts and Upgrades, New Switch/VLAN Rollouts, CSS Deployments, Firewall Deployments, Upgrades, Patches and/or Service Packs

• Desktop Projects - Desktop Refreshes, Citrix Server/Client Rollouts, Antivirus, Upgrades, Patches and/or Service Packs

• Application Hosting Projects - New Server Refreshes (Wintel, Linux, Unix), Upgrade, Patches and/or Service Packs, New Software Hosting, Existing Software Hosting Operations projects that only involve patch upgrades Agency Legacy migration to DOIT hosting.

• Database Projects - New/Existing Database Rollouts, Database Conversions, Upgrades, Patches and/or Service Packs

• Directory & Messaging Projects - MS-Exchange Rollouts, Active Directory, Novell Single Sign-on, Server refreshes, upgrade/patches/services packs Projects

• Mainframe Projects - New Software Releases, Software Maintenance, and Hardware Refresh

• Data Center Projects - UPS Upgrades, Air Handling, Server Install & Wiring, and All Electrical and Mechanical Upgrades

Exception ProcessException Process• If your project does not fit the criteria for an SDM Lite

Project and you would like to file an exception with the PMO to use SDM Lite, please complete the SDM Lite Exception Request form. The exception form is located on the SDM Lite portal site under the link titled Reference Materials.

• The DOIT CIO or his/her designee must approve the exception.

7 Phases of SDM Lite7 Phases of SDM Lite

• Business Issues• Business Requirements• Design• Construction• Testing• Implementation• Post Implementation

So what is the Difference between:So what is the Difference between:

SDM Standard/SDM Standard/SDM Lite?SDM Lite?

A number of people have asked me what A number of people have asked me what theythey think is an important question…think is an important question…

Does it Taste great or is it Less Does it Taste great or is it Less Filling?Filling?

Business IssuesBusiness IssuesFormal - Phase Kick–off Presentation

The Business Issues phase it the only phase that requires a formal kick off meeting. SDM Lite Required Characteristics Form Project Description Constraints Key Assumptions

Team Meeting Objectives

Team Wheel

Roles and Responsibilities

Lessons Learned from other Projects

Guiding Principles

Project Management PlanProject Management PlanThe Project Management Plan should include the following plan components that are updated at then end of each Phase:

Project Organization Project Description Project Scope Statement Project Detailed Schedule Solution Approach Cost Benefit Analysis (Standard) Project Budget Summary Communication Plan External Project Considerations Issues Log Risk Management Plan Organizational Standards and Polices High Level –General Deployment Strategy Procurement Plan

All meetings must be Planned and Documented

in the Communication

Plan and approved by the

Executive Sponsor!

PROJECT PROFILE PROJECT PROFILE Project Profile: A DOIT Project Profile is required for all SDM Lite projects that are approved by the PSC to move beyond Phase 1.

Business ManagerCreates Profile

Executive Sponsor Approves Profile

PSC Approves Profile

DOIT Profile Cmte. Accepts Profile

PHASE–END DECISION POINT PHASE–END DECISION POINT PRESENTATIONPRESENTATION

Phase-End Decision Point Presentation

The Phase-End Decision Point presentation summarizes the team’s completion of the requirements for the phase, its recommendation for the project, and the plan for the next phase.

Owner: Technology Manager

Business Requirements PhaseBusiness Requirements Phase

The purpose of the Business Requirements Phase is to define the system or process in more detail with regard to those things that must happen in order for the new solution to be declared usable by the business.  

PROCURE 3RD PARTY SERVICESPROCURE 3RD PARTY SERVICES  

• This activity and deliverable is only needed when there is a need to procure outside 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).

BUSINESS AND TECHNICAL BUSINESS AND TECHNICAL REQUIREMENTS DOCUMENT REQUIREMENTS DOCUMENT

  Business and Technical Requirements Document – One document includes two Deliverables: Business Requirements Workbook and the Technical Requirements Workbook. This document is co-owned by the Business Requirements Lead and Technology Manager.

SOLUTION ALTERNATES DOCUMENTSOLUTION ALTERNATES DOCUMENT

Once the requirements have been fully defined, the project team should provide a list of viable solution alternatives that were considered by the project team.

Viable solution alternatives would be those solutions which would satisfy the defined requirements and fit within the defined constraints of the project (i.e. budget constraints, desired timeline constraints).

The conclusion at the end of this document is the Recommended Solution. Owner: Business Manager 

What are the solutions to

the Business Problem?

DesignDesignThe purpose of the SDM Lite Design Phase is to translate the business and technical requirements into detailed design components that will later be used to construct the business solution in Phase 4, the Construction Phase.

During the Design Phase, there may be 1 design review; the System Design review.

  Was this part of

the design?

System Design DocumentSystem Design Document• Provide a system design specification that shows how

the solution components further decompose into sets of integrated modules and sub-processes.

• This Activity is a combination of the General and Detail

design Activities from SDM Standard.

• Partition the design into a set of subcomponents that can be more easily managed, assigned, and defined to meet the business and technical requirements of the solution.

Owner: Development Lead.

What should this System look like?

Should we meet with the TRB?Should we meet with the TRB?If a project involves technology that is compliant with existing EWTA standards and patterns – or – if the project has been granted a prior EWTA exception, no formal DOIT TRB reviews will be necessary, provided that:

1. Any infrastructure, or shrink-wrap or COTS software changes are limited to an “in place” refresh or upgrade with a newer version of the same basic product, or

2. Changes to any existing application through routine maintenance or enhancements do not materially change the architecture of the application and that the application remains EWTA compliant or within the boundaries of any existing EWTA exception, or

3. The introduction of any new or extended infrastructure or a new or enhanced application features or functionality is compliant with EWTA standards and patterns or remains within the boundaries of any existing EWTA exception.

PHASE-END DECISION POINT PHASE-END DECISION POINT MEETINGMEETING

  Optional in SDM Lite!

The PSC and the Technology Manager decide if a Meeting is needed or not.

The PSC should be sent a project Stautus Report and any other neccesary information according to the Communication Plan within the Project Management Plan.

Construction PhaseConstruction Phase

The purpose of the Construction Phase is to translate the business requirements, technical requirements, and detailed design components into functioning software modules, and supporting test and training artifacts.

 

Deliverables no longer Required in Deliverables no longer Required in SDM Lite!SDM Lite!

• Conduct the Phase Kick-off Meeting • Environment Migration Checklist *• Back-out and Recovery Plan • Disaster Recovery Assessment (If needed get er done) LC• Update and/or Create Training Plan• Phase-End Decision Point Presentation

Smaller projects by nature result in less work in Construction Phase!

* = Required for when DOIT Hosting Services are used – recommend for agency-hosted projects.

TESTING TESTING

The purpose of the SDM Lite Testing phase is to prove that the developed system satisfies the requirements defined in the Business and Technical Requirements Document. Several types of tests will be conducted in this phase.

Minor changes in Testing PhaseMinor changes in Testing Phase

Testing requires a Phase-End Decision Point meeting

Eliminated Deliverable

1. Conduct the Phase Kick-off Meeting

Combined Form

1. Integration Test Case Description

2. System Test Case Description

3. UAT Test Case Description

4. Performance Test Case Description

5. Regression Testing

Implementation Implementation

• The purpose of the SDM Lite Implementation Phase is to introduce the solution to the business users in the selected deployment sites.

• The Implementation Phase allows for pilot deployments.

• Typical deployment strategies are either a “Big-Bang” deployment or a “Phased-Based” deployment.

Deliverables no longer Required in Deliverables no longer Required in SDM Lite!SDM Lite!

• Conduct the Phase Kick-off Meeting• Complete the Environment Migration Checklists• End User Training • Phase-End Decision Point Presentation

Post-Implementation Post-Implementation

The purpose of the SDM Lite Post-Implementation Phase is to ensure a smooth transition to the appropriate teams who will provide the ongoing management of the solution. If there are multiple deployments, many of the activities within this phase will be executed for each deployment.

TRANSITION THE SOLUTION TO TRANSITION THE SOLUTION TO PRODUCTION SUPPORTPRODUCTION SUPPORT

  The purpose of this activity is to ensure that the solution is now accepted as a part of everyday business and will be supported as a matter of doing business.

SHUTDOWN THE PROJECTSHUTDOWN THE PROJECT  

The purpose of this activity is to formally shutdown of the project.

Project Summary:

Create an overall project summary to include phase-based planned to actual schedule comparisons, planned to actual budget comparisons, and lessons learned by the project team. This project summary should be distributed with the formal project closeout communication.

Project ReviewsProject Reviews

Projects that qualify under the SDM Lite criteria are not subject to standard project review meetings at DOIT!

Inventories still need to be maintained.

The CIO or PMO have the right to call for a review of any Technology Project if they deem it to be necessary.

Thank You!Thank You!

The SDM Lite Team!The SDM Lite Team!

Jim A.K.A. “Popeye”

Rutushni Team Leader

Ron A.K. A. ‘”The Politician”

San Angelo

Len A.K.A. “Jarhead”

Smith

JeanneA.K.A. “The Doctor”

Lee

Keith A.K.A. “ The Farmer”

McHugh