1. System Development Methodology
“Lite”
I want to start by thanking the Business Development Directors for giving us some of their time to present the “New” SDM Lite Methodology.
The SDM Lite Team hopes that our work will help make your life as project managers a little easier and your projects more successful!

2. The SDM Lite Team!
Who would have ever thought this would be a good team?
Len
A.K.A. “Jarhead”
Smith
Jeanne
A.K.A. “The Doctor”
Lee
Jim
A.K.A. “Popeye”
Rutushni
Team Leader
I would like to start out by introducing our Team. Jim Also known as “Popeye” Rutushni ( Looks like him doesn’t it!). Jeanne Also know as “The Doctor” Lee. Len Also known as “Jarhead” Smith. Keith Also known as “The Farmer” McHugh. Keith has a farm in Newtown and you can find him tiling the soil when he is not on the computer! Ron Also know as “The Politician” San Angelo.
Keith
A.K.A. “ The Farmer”
McHugh
Ron
A.K. A. ‘”The Politician”
San Angelo

3. Benefits 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
Why are we working so hard to create a System Development Methodology? Is it because our CIO wants one or is it because as a state we need to better utilize our resources?

4. What are the Benefits of SDM?
State agencies will utilize the same process for managing technology projects within established SDM Lite criteria.
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.
Improves the ability of a Project Manager to clearly understand the Goals and Objectives of an Executive Sponsor.
Okay why use SDM Lite? 1. Were all on the same path. Common process, 2. Lets everyone know where we are in a project and where we are going. 3 Agreed upon objectives!

5. SDM LITE Characteristics
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.
The SDM Lite Team want to insure that Project Managers ( Technology Managers) understand what types of projects would qualify as “ SDM Lite Projects” - That’s why we developed what we believe is an easy to understand - Characteristics Check List Form.

6. General Project Characteristics (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.
The form starts with the General Project Characteristics……………less than $400,00. Equal to or less than 6 months……Limited to 1 Agency……..

7. Applications Projects, Only (Requires that all apply)
Your application requires data from no more than one (1) other application.
Your application requires only one (1) dedicated database

8. Operations Projects, Only (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
Operations Projects that qualify for SDM Lite…. There are still conversations ongoing regarding having a separate Operations Methodology, but for now SDM Lite will help to reduce the work effort for those projects that qualify.

9. Exception 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.
You may want to roll the dice, so to speak if you think your project is close, but does not specifically meet the SDM Lite criteria. Remember the DOIT CIO has to approve it so roll carefully!

10. 7 Phases of SDM Lite Business Issues Business Requirements Design
Construction
Testing
Implementation
Post Implementation
SDM Lite still follows the 7 phases of SDM Standard….

11. So what is the Difference between:
SDM Standard/
SDM Lite?
A number of people have asked me what they think is an important question…

12. Does it Taste great or is it Less Filling?
Okay, so it was Steve Lynch ( Not surprising) Who asked me the question. Steve, I am not sure but, I think the answer is less filling!

13. Formal - Phase Kick–off Presentation
Business Issues
Formal - 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
The Business Issues Phase has the only formal Kick-Off Presentation. For the rest of the Phases regular Status Meetings should be held throughout the various phases and your project team should be realigned to insure they are ready for the next phase.

14. Project Management Plan
The 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!
The Project Management plan is the most important document in SDM Lite! This should be a living breathing document and It should be updated and referred to during each phase .
(Read each component). It serves no purpose if you develop it and then throw it on a shelf where it will never be seen again! Update it throughout the phases as needed!

15. 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 Manager
Creates Profile
All Technology Projects Require a Project Profile. What is the process for approval?
Executive Sponsor
Approves Profile
PSC Approves
Profile
DOIT Profile Cmte. Accepts Profile

16. 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
This Deliverable is reduced in SDM Lite from 17 pages to 10 pages. Includes: Project Description, Project Wheel, Timeline, Overall Budget, Team Recommendation, Issues, Risks, Exit Criteria. Eliminated: Program Breakdown, Cost Benefit Analysis, Budget Performance for specific phase.

17. Business 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.  
Business Requirements Phase- Business Leaders are in charge and need to be specific!

18. PROCURE 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).

19. BUSINESS AND TECHNICAL 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.
Because SDM Lite projects are smaller in scope than those that require Standard SDM, the Business and Technical Requirements Workbook Deliverable is simply the folding of the Functional Requirements, Non-Functional Requirements and Technical Requirements Workbooks into one consolidated deliverable to help streamline requirements gathering.  You will find the consolidated deliverable on the SDM Lite Website. If you need more infrormation utilize the deliverables in SDM Standard for reference.

20. SOLUTION 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
In SDM Lite the Solutions Alternatives Document and the Solution Recommendation have been combined into one activity.
What are the solutions to the
Business Problem?

21. Design During the Design Phase, there may be 1 design review;
The 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?
SM Standard requires a General Design Review before the TRB and A Detailed Design Review before the TRB. SDM Lite requires only one design review the System Design Review. If you have serious design concerns you should consult with John Vittner or Alan Treiber. Be prepared to submit your Business and Technical Requirements Document, Design Document, and Security Profile Documents to the TRB.

22. System 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.
For smaller SDM Lite Projects the General Design and Detailed Design Document have been combined into the System Design Document.
What should this System look like?

23. 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:
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
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
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.
If your project does not meet the above criteria, then the Architecture and Standards Division will need to review your project If you are unsure if a EWTA Exception exists for your technology, please contact the Architecture and Standards Division.

24. PHASE-END DECISION POINT MEETING
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.
This is the 1st of Optional Phase-End Decision Point Meetings! The only other required Phase-End Decision Point meeting is in the Testing Phase!

25. Construction 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.
The Construction Phase has some small changes, but the project itself will dictate how much work needs to be done!

26. Deliverables no longer Required in 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!
ONCE AGAIN THE FACT THAT A DELIEVERABLE IS NOT REQUIRED DOES NOT MEAN IT SHOULD NOT BE ACCOMPLISHED! IF YOUR PROJECT REQUIRES IT ( AS LARRY THE CABLE GUY SAYS “ GET HER DONE”!
* = Required for when DOIT Hosting Services are used – recommend for agency-hosted projects.

27. 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.
There are only small changes to the Testing Phase. Again the nature of the project should reduce the work effort during this phase.

28. Minor changes in Testing Phase
Eliminated Deliverable
Conduct the Phase Kick-off Meeting
Combined Form
Integration Test Case Description
System Test Case Description
UAT Test Case Description
Performance Test Case Description
Regression Testing
Reduced work comes from the nature of the project, smaller projects require less testing!
Testing requires a Phase-End Decision Point meeting

29. 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.

30. Deliverables no longer Required in SDM Lite!
Conduct the Phase Kick-off Meeting
Complete the Environment Migration Checklists
End User Training
Phase-End Decision Point Presentation

31. 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.

32. TRANSITION THE SOLUTION TO PRODUCTION 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.

33. SHUTDOWN 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.

34. Inventories still need to be maintained.
Project 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.

35. Thank You! The SDM Lite Team!
Len
A.K.A. “Jarhead”
Smith
Jeanne
A.K.A. “The Doctor”
Lee
Jim
A.K.A. “Popeye”
Rutushni
Team Leader
Keith
A.K.A. “ The Farmer”
McHugh
Ron
A.K. A. ‘”The Politician”
San Angelo