How the Texas Project Delivery How the Texas Project Delivery Framework Can Chart the Framework Can Chart the

Course for All Your Application Course for All Your Application DevelopmentDevelopment

TASSCC 2008 Annual ConferenceTASSCC 2008 Annual ConferenceAugust 11, 2008August 11, 2008

Purpose:Purpose:

• To illustrate the positive results gained To illustrate the positive results gained by the Texas Lottery Commission after by the Texas Lottery Commission after adopting the Texas Project Delivery adopting the Texas Project Delivery Framework as the standard Framework as the standard methodology for implementing all methodology for implementing all internal software technology projects internal software technology projects regardless of sizeregardless of size

The Agenda

• IntroductionIntroduction• Where We WereWhere We Were• Our GoalsOur Goals• The SolutionThe Solution• Questions???Questions???

Texas Lottery Commission

•East 6East 6THTH Street , Austin Street , Austin

•Comprised of Bingo and LotteryComprised of Bingo and Lottery

•Lottery - Over $15 billion for State of Texas since inception in 1992Lottery - Over $15 billion for State of Texas since inception in 1992

•Lottery – Over $10 billion went to Foundation School FundLottery – Over $10 billion went to Foundation School Fund

•Lottery - Over $1 billion to Foundation School fund in 2007Lottery - Over $1 billion to Foundation School fund in 2007

•Bingo – 18.1 million people played Bingo in 2007Bingo – 18.1 million people played Bingo in 2007

•Bingo - $32 million in charitable distributions in 2007Bingo - $32 million in charitable distributions in 2007

A little about me – Gary Mayes

Worked extensively in software applications design and Worked extensively in software applications design and support for 20 years support for 20 years Started in IT in 1988 as a computer programmer with SP&GSC Started in IT in 1988 as a computer programmer with SP&GSC Spent 10 years supporting Licensing Agencies with SP&GSC Spent 10 years supporting Licensing Agencies with SP&GSC and DIRand DIROutsourced in 1998 to Northrup GrummanOutsourced in 1998 to Northrup GrummanHired by the Lottery in 1998 as a computer programmerHired by the Lottery in 1998 as a computer programmerCurrently assigned as the Quality Assurance and Systems Currently assigned as the Quality Assurance and Systems Analyst CoordinatorAnalyst Coordinator

Where We Were: What needed improvement

•Standards – non-existentStandards – non-existent•Systems Documentation – yeah rightSystems Documentation – yeah right•User Documentation – “It’s your system, don’t you know User Documentation – “It’s your system, don’t you know how it how it works?”works?”•Project Management - “Who me, I’m just a developer?”Project Management - “Who me, I’m just a developer?”•Development Methodology – hodgepodge of different viewsDevelopment Methodology – hodgepodge of different views•Stakeholder Trust - “That’s not what I wanted and why did Stakeholder Trust - “That’s not what I wanted and why did it take it take so long?”so long?”

How did we get there?How did we get there?

• Small shopSmall shop• Differing skill setsDiffering skill sets• Multiple hardware and software Multiple hardware and software

environments. Mainframe, MS servers, MS environments. Mainframe, MS servers, MS software applications, Oracle applicationssoftware applications, Oracle applications

• Stakeholder’s need it now mentalityStakeholder’s need it now mentality• Single point of support ( analysis, Single point of support ( analysis,

development and production ) for each development and production ) for each application with a “Do it my way” attitudeapplication with a “Do it my way” attitude

The Goals of the Project – The Goals of the Project – Charting the Course for Charting the Course for SuccessSuccess

• Adopt a standard methodology for software Adopt a standard methodology for software developmentdevelopment

• Improve software standardsImprove software standards

• Improve system documentationImprove system documentation

• Generate user documentationGenerate user documentation

• Increase user involvement in their own Increase user involvement in their own projectsprojects

• Create an environment of trust with the Create an environment of trust with the project stakeholdersproject stakeholders

• Deliver projects more efficientlyDeliver projects more efficiently

IT management made a decision...IT management made a decision...

• Adopt the Texas Project Delivery Framework as Adopt the Texas Project Delivery Framework as the standard methodology for implementing all the standard methodology for implementing all internal software technology projects.internal software technology projects.

Why? What Were the Intended Why? What Were the Intended Benefits? Benefits? What course do we What course do we take?take?

ScalableScalable AffordableAffordable Project ManagementProject Management Systems DocumentationSystems Documentation User DocumentationUser Documentation Change Control Change Control User involvement and acceptanceUser involvement and acceptance TrainingTraining Audit RequirementsAudit Requirements

Scalable - How many masts Scalable - How many masts does our ship need?does our ship need?

• We could adapt the We could adapt the needed framework needed framework gates according to gates according to the size of the the size of the project.project.

• Only use the gates Only use the gates necessary.necessary.

• From a dingy to a From a dingy to a schooner, the right schooner, the right size for the right job.size for the right job.

Affordable – What’s Affordable – What’s thisthis trip gonna cost? trip gonna cost?• Direction and framework training provided by DIRDirection and framework training provided by DIR• Able to reorganize current staff to meet the needsAble to reorganize current staff to meet the needs

– Quality Assurance and Systems Analyst teamQuality Assurance and Systems Analyst team– Two Development teamsTwo Development teams– Web Design teamWeb Design team– Database Administrator teamDatabase Administrator team

• Transition of systems to integrated hardware and software Transition of systems to integrated hardware and software platforms. Significant costs for hardware / software upgrades, platforms. Significant costs for hardware / software upgrades, but we needed this anyway.but we needed this anyway.

• Staff developmentStaff development– Used current training budgets Used current training budgets – Mentoring programMentoring program

• Transition of the way we did business. Retrofitting existing Transition of the way we did business. Retrofitting existing projects caused some delays. Decisions had to be made.projects caused some delays. Decisions had to be made.

Project ManagementProject Management

• Required by design. Required by design.

• Team leads became project managers.Team leads became project managers.– Attended Project Management trainingAttended Project Management training– Mentored other staffMentored other staff

• Framework gates and document templates are Framework gates and document templates are stepping stones to good project managementstepping stones to good project management

• Provides a System Development Life Cycle Provides a System Development Life Cycle guideguide– http://www.dir.state.tx.us/pubs/framework/extensions/sdlc/sdlcguide/sdlc-http://www.dir.state.tx.us/pubs/framework/extensions/sdlc/sdlcguide/sdlc-

guide.pdfguide.pdf

Systems DocumentationSystems Documentation

• Framework provided the Framework provided the tools.tools.– Templates – modified to fit Templates – modified to fit

our needsour needs• Project CharterProject Charter• Project PlanProject Plan• Software Requirements Software Requirements

SpecificationsSpecifications– Data DictionaryData Dictionary– User Roles and PrivilegesUser Roles and Privileges– Process Flow DiagramsProcess Flow Diagrams– Use CasesUse Cases– Screen PrototypesScreen Prototypes– Report PrototypesReport Prototypes

• Project AcceptanceProject Acceptance• Others as needed Others as needed

User DocumentationUser Documentation• Tweaked existing Tweaked existing

software requirements software requirements and test scripts to and test scripts to provide basic user provide basic user documentationdocumentation

• Turned these Turned these documents over to documents over to business analysts in the business analysts in the corresponding corresponding departments departments

• Business analysts Business analysts added business rules to added business rules to create functional user create functional user process flows. process flows.

Change ControlChange Control

• Software requirements are agreed to Software requirements are agreed to and signed off by user project and signed off by user project managermanager

• Changes to requirements are now Changes to requirements are now obvious to the user obvious to the user

User Involvement and User Involvement and AcceptanceAcceptance• Charter and Project Plan signed by usersCharter and Project Plan signed by users• JADs – user involvement, management and JADs – user involvement, management and

staffstaff• BudgetBudget• Software Requirements DocumentSoftware Requirements Document

– Business Process FlowsBusiness Process Flows– User PrivilegesUser Privileges– Use CasesUse Cases– Screen DesignScreen Design– Report DesignReport Design

• Change ControlChange Control• User Acceptance TestingUser Acceptance Testing• SignoffSignoff

Meets Audit RequirementsMeets Audit Requirements

• Documentation, documentation, Documentation, documentation, documentation. Can’t say it enough.documentation. Can’t say it enough.

• Systems SecuritySystems Security– SRS document defines access and rolesSRS document defines access and roles

• Separation of duties. Separation of duties. – Developers have no access to productionDevelopers have no access to production– DBAs move codeDBAs move code– Users must request system access in writingUsers must request system access in writing

• Approval of project documents in Approval of project documents in writingwriting

TrainingTraining

• Sent Analysts to DIR Framework instructionSent Analysts to DIR Framework instruction• Cross trained Quality Assurance Analysts Cross trained Quality Assurance Analysts

and Systems Analystsand Systems Analysts• Sent Analysts, QA Analysts, Developers and Sent Analysts, QA Analysts, Developers and

Users to Use Case TrainingUsers to Use Case Training• Detailed User Acceptance Testing provides Detailed User Acceptance Testing provides

system training for the core user group system training for the core user group ( Train the Trainer )( Train the Trainer )

• The Trainer then trains the rest of the staff The Trainer then trains the rest of the staff on new systems on new systems

Summary – Avoided most Summary – Avoided most obstacles along the way and obstacles along the way and reached our destinationreached our destination

• Accepted Life Cycle Accepted Life Cycle MethodologyMethodology

• StandardsStandards• Systems Systems

DocumentationDocumentation• User DocumentationUser Documentation• Project ManagementProject Management• Security & ControlsSecurity & Controls• Meets Audit Meets Audit

RequirementsRequirements• User InvolvementUser Involvement• 80-20 rule & Efficiency80-20 rule & Efficiency

Contact InfoContact Info

Gary MayesGary Mayes

QA/Systems Analyst CoordinatorQA/Systems Analyst Coordinator

Texas Lottery CommissionTexas Lottery Commission

gary.mayes@lottery.state.tx.usgary.mayes@lottery.state.tx.us

(512) 344-5311(512) 344-5311