IT Services

1
IT Services

• SDLC, Peer and Gate Review Approach
• September 2011

2
Agenda

• Review three supported Methodologies
• Project Life Cycle
• Software Development Life Cycle
• Scrum
• Review Peer and Gate Review Approaches within
  methodologies
• QA

3
Product Life Cycle (PLC)
4
Project Life Cycle (PLC)

• Non-development life cycle
• Straight Forward
• Internal projects
• Upgrades
• Installs
• Conversions
• Shared artifacts
• Where appropriate

5
Project Life Cycle (PLC)
6
Software Development Life Cycle (SDLC)
7
The SDLC What Is It?

• The SDLC is a hybrid of the Rational Unified
  Process (RUP) and Agile development
  methodologies.
• There are four distinct phases
• Inception
• Elaboration
• Construction
• Transition

• The GAI SDLC
• Phases provide incremental, or staged, delivery
  of functionality.
• Iterations provide the progressive development
  and rework of functionality.
• Provides repeatable/predictable scheduling,
  development, and testing processes.
• Emphasizes the continual delivery of business
  value at predictable intervals.
• Shows consistent progress while being better able
  to respond to changes.

8
A Phased Approach
Inception
Elaboration
Construction
Transition
Propose Define and Approve the Project
Prototype Capabilities Prove-Out the
Architecture
Develop the Solution
Move the Solution into Production
9
Incremental Development

• The progressive development of features and
  functionality via the delivery of smaller pieces
  that are valuable to the customer
• Encourages progressive integration (not big
  bang integration)
• Each Phase can have 1 or more releases
• Each release can add functionality

Phase
Release
Iteration
Things of Value
10
Roles Within Iteration

• Business Partner
• Program Manager
• PMO
• Project Manager
• Business Analyst
• Architect
• Development Lead
• Data Modeler
• Web Services
• Tester

11
SDLC Releases
What comprises a Release? A stable, executable
version of product, together with any artifacts
necessary to use this release, such as release
notes or installation instructions (Rational
Unified Process Glossary)

• GAI ITS Releases
• A release is a completed set of functionality
  with artifacts (business and internal).
• Each Phase may deliver one or more releases.
• A release progresses through each of the
  environments.
• Releases begin with 1 and increment by 1 as
  necessary.
• A release can be major (increment by 1) or
  minor (increment by .1).
• Shows consistent progress while being better able
  to respond to changes.

12
Putting It Together - Iterative Development
Inception
Request

• Business Partner makes requests for product
  development
• Program Manager evaluates request and assigns
  Lead Project Manger (PM)
• PM begins to gather information on request
• PMO, Program Project Manager agree on
  governance approach

Planning

• PM begins Project Charter
• PM coordinates meeting with Resource Managers
  (RM)
• RM understands objectives and assign resources
• Lead PM and PMO coordinate project plan linking
  sessions with all PMs
• BA begins Reqs for iteration 1

Kick-off

• PM conducts Kick-off meeting with resources and
  business partner
• PM coordinates JAD sessions
• Architect creates high level design with Data
  Modeler
• Test Lead creates test plan
• PMO and PM plan gate and peer reviews for project
• Iteration 1 begins

13
Putting It Together - Iterative Development
Iteration 1
Month 1
Iteration 2

• BAs document Iteration 2 Reqs.
• Testers begin creating test cases for Iteration 1
  Reqs.
• Architects, Developers, and Data Modelers may
  begin Preliminary Design for Iteration 1
• BAs validate functionality developed in Iteration
  1

Month 2
Iteration 3

• Developers and Data Modelers perform detail
  design for Iteration 1 Reqs.
• Developers code for Iteration 1 Reqs. Start 2
• BAs document system and data requirements to be
  developed in Iteration 3
• BAs validate functionality developed in Iteration
  2
• Testers finalize test cases for functionality
  developed in Iteration 1 and start 2

Month 3

• Developers and Data Modelers perform detail
  design for Iteration 2 Reqs.
• BAs document system and data requirements to be
  developed in Iteration 4
• BAs validate functionality developed in Iteration
  3
• Testers test functionality developed in Iteration
  2
• Testers finalize test cases for functionality
  developed in Iteration 3
• UAT for functionality developed in Iteration 1
  and 2

14
Elaboration Phase Iteration Tasks
Artifacts Developed During This Phase
Project
Arch., Design, Develop.
Requirements
Data
Testing

• Project Plan
• Project Status Report
• Change Requests

• Architectural Spec.
• Architectural Review Checklist
• Design Review Docs
• Code Review Docs
• High-Level Design Docs
• Detailed Design Docs

• Product Hierarchy
• Coverage Matrix
• Non-Functional Specs
• User Dialogs
• Business Rules
• Data
• Dictionary/Glossary
• Data Mapping
• GUI Screens
• GUI Data Tables
• Data Transformation

• Conceptual Data Model
• Logical Data Model
• Physical Data Model
• CXML Model
• DDL /DML Scripts

• Test Plan
• Test Cases
• Test Scripts

15
Elaboration Phase Artifact Flow
16
Transition Phase Iteration Tasks
Fully tested and major defects corrected
Artifacts Developed During This Phase
Project
Arch., Design, Develop.
Requirements
Data
Testing

• Update Project Plan
• Project Status Report
• Change Requests
• Transition Checklist
• Project Close-Out Report

• Update Arch. Docs
• Update Design Docs
• Design Review Docs
• Code Review Docs

• Update Requirements

• Update Data Models

• Update Test Plans
• Update Test Scripts

User Preparation

• Communication Plan for Delivery
• Training Materials

17
Scrum
18
The Scrum Process

• Implementing Scrum
• Outside Consultants
• Time Frames
• Successful Teams

19
Peer Reviews
20
Formal Reviews
21
Informal Reviews

• Code reviews, logical/physical data models,
  deployment plans, customer care hand-off plans,
  test plans, and ETL Specification reviews
• Audience a peer or team mate
• Value add - formal meetings are not required,
  team/person reviewing will record metrics and
  share with PMO
• Timing as needed efficient and flexible
• The goal is to have a knowledgeable second set of
  eyes reviewing the work prior to development

22
Industry Standards for Proving the Value
23
Proving the Value

• Dashboards
• Time Tracking
• Unit Code Coverage
• UAT Defects
• Peer Review results
• Health check
• Compliance with methodology

24
QA

• Whats on your mind?