The Cadence Journey

Transcript The Cadence Journey

Operational Advantages An Overview of Facets Release Management - Cadence & Agile Process

Chris Heller – Monday 5/19 - 11:45-12:45 & 1:45-2:45

Agenda

     

The Cadence Journey Agile Release Development Release Delivery Release Adoption Preparing for the Future Vendor Platform Updates 3

The Cadence Journey



Yearly Releases:

Too Big!



8 Week Cadence:

Too Small!



Quarterly:

Just Right!

(For Now!)

The Cadence Journey



Quarterly Cadence

 FMAN –

ebruary,

ay,

ugust,

ovember  12 Week Release Development  Four, 3 Week Sprints  Sprint 4 Dedicated to Release Hardening  Sprint 0 In-Between Releases  Release Preparation (Environments, Source mgmt., etc.)

The Cadence Journey



What We’re Doing with the Time

   

Continuously Refine the Agile Process

 Inspect & Adapt

Improve Grooming

 More Focus on Theme/Feature/Story & Acceptance Criteria  More Analysis on Solution Design & Performance

Advance Practices Around Software Quality

 Focus on Test Collaboration   Automated Unit & Regression Testing Capabilities Continuous Build & Integration

Deliberate and Complementary to Targeted Deliverables*

Agile Release Development

Release Development



What We’ve Learned After 2+ Years of Agile:

 When it Come to Agile,

One Size Does Not Fit All!

 Retrospectives & Sharing Best Practices is Integral  Behavior Modifications & Reinforcement Facilitate Change  Development Served by Tools, Not Slaves to Them  Be Very Careful on your Commitments!

Release Development



REFINEMENT IN PROCESS: Continuous Grooming

 Theme/Feature: Product Management, Owners & SMEs  Feature/Story: Delivery Teams & SMEs  Acceptance Criteria developed at Feature & Story Grooming  Artifacts Produced as a Result of Grooming

Release Development



REFINEMENT IN PROCESS: Test First

 PD/SE/QA Collaborate on Test Planning  Comprehensive Test Plan Ready

Before Coding Begins

 Testing Assignments Distributed Between SE & QA

Release Development



REFINEMENT IN PROCESS: Demo Planning & Delivery

 Target Features for Release Demo with Teams DURING PLANNING!

 Prepare for Demonstrations Throughout Development & Let Demo Prep Affect How Development is Executed  Sprint Demo Accordingly & Don’t Think Any Feature Too Small!

 Approaching as an afterthought is a CHORE!

Release Development



Tooling

   HP ALM/AGM (Application Lifecycle Mgmt, Agile Manager) HP Defect Module Adoption Q3 Q4 2014’14 HP QTP (Quick Test Pro)-Test Automation    MS TFS (Team Foundation Server) – Source & Build Mgmt MS Test, (C#, C++ automated unit testing) JUnit, NUnit, TestStack.White

  Batch Regression Compares (

Paying Dividends Already!

) Interactive & Services Automation Under Development

Release Development



And Why Are We Doing Agile Development?

 Drive Changes in Behaviors over Processes  Become Highly Responsive to Our Market & Client Needs!

Release Delivery



Delivery Terminology



Release:

Scheduled Deliverable of New Functionality 

Release Delivery Methods

 

Incremental:

Discrete Set of Deliverables & Functionality

Cumulative:

Current & Previous Deliverables & Functionality  

Full Binary Replacement:

Full System Build & Delivery

Selective Binary Replacement:

Specific DLL Build & Delivery  

Cumulative Delivery Promotes System “Known State” Selective Binary Replacement Promotes Adoption

Release Delivery



4.81, 4.71:

Maintenance Releases,  Incremental, Selective Binary 

5.01 Maintenance

 Going forward with 5.01 R17 in May  Selective Binary (First Select Binary of 5.01 Release Line 

5.01 R15 MUST BE INSTALLED BEFORE APPLYING R17 & BEYOND!



Subsequent Releases will be Cumulative Selective Binary Replacement



5.10 “Release Under Development” (RUD)

  Full Binary Replacement (FBR) Releases Quarterly Cadence (FMAN –

ebruary,

ay,

ugust,

ovember)

Release Delivery

Release Schedule Full Year Release Schedule - 2014

5.1

5.01

4.81

2/5 3/19 5/7 8/6 2/12 3/26 5/7 8/13 2/19 4/2 5/15 8/20 11/12 11/12 11/26 Release Optional

Quarterly Releases = First Wednesday 19 February, May, August, November 5.2 Release Target November 5 th

2014

Application Release Schedule

Release Adoption

5.10 R

n (

13%)

Release

Less than 4.71

(5%) 4.71 & 4.81

(34%) 5.01 R

(48%) A snapshot of production releases in place with clients as of mid-April 2014

Release Adoption



We Are In A Transition Period

 5.x Release Adoption Based on Reform/Exchange Needs, Not Release Adoption Practice - True or False?

  Out-of-Compliance on Supported Releases May Increase Quarterly Cadence May Improve Adoption Cadence 

Keys To Client Release Adoption:

  Release Quality Ease of Upgrade Process

Preparing for the Future

Upgrade Framework

    .NET based application used to deploy database objects. Run conversions; install procedures, tables, indexes

Restartable Cumulative Across Releases Multi-threaded/concurrent actions Multiple databases upgraded during a single execution.

   

Table driven, no lists - Capable of detailed reporting Verification scripts Dependency handling built in GUI front end 25

5.2 Installation Re-Architecture



5.2 Targeted to be the Last Major/Minor Release Upgrade Requiring Full Binary Uninstall/Reinstall



Includes Enhancements to Installation & Runtime Infrastructure to Support Future “In-Place” Upgrades



Wide System Impact

  Runtimes (Interactive, Batch, Services) TriZetto Product Integrations   3 rd Party Software Integrations Extensibility

Test Automation & Refactoring



Integral to Improving Software Quality

  “Out-of-the-Box” for New Development Development Staff Collaborating on “Test First” & Automation 

Application of Practice to Legacy Code is Challenging

 Characterization/Unit Tests Written & Executed Before Refactoring Begins; Ensure Adequate Coverage of Use Cases & Scenarios   Consider Risks & Impacts to Existing Functionality & Client Usage Choose Targets Carefully Based on Performance, Maintenance, etc.

Services Development



Opportunity to Advance Architecture & Improve Enterprise Application Integration

 Interfaces that are “

Less Brittle” and Better Accommodate “Change Through Time”



Advance ReST Services Development

  Accumulator Update ReST Service Provide Real-Time Accumulator Updates To/From Facets

Application Patterns

 

Another Opportunity to Advance Architecture

  Web-Based Applications leveraging T3 Technology Stack (HTML/ASP.Net, C#, Object Repository, MVC, etc.) TDD & AUT Practice “Out-Of-The-Box”

Leverage in Workflow & BPA Configuration Application Performance Redesigns



Leverage New ReST Services Behind New Applications



Develop Transition Plan From Legacy UI

 Target Domains & Applications in New Technology   Attack Domains Requiring Attention Improve TCO; Create a “Tipping Point”

Collaborations

• • Improve Collaboration across Clients, Consulting, Hosting, BMS through new Partnership Program Refine Best Practices in Deployment with Internal Partners • • Too Casual and “As-Needed” in the Past Some early wins • • Sprint reviews / Sprint testing Smoke testing with Hosting

Vendor Platform Update

Expanding LINUX Support



Formal Support of Sybase 15.7 on Red Hat Enterprise

LINUX (RHEL 6.5) during 5.10 R6 Development    Development Environment Build-Out in ABQ Datacenter Underway Subset of R6 Sybase platform development to migrate to new RHEL Servers “Validation” of Platform Targeted Upon Delivery of 5.10 R6  Oracle 11g Support on Oracle Enterprise LINUX (OEL6)

already established.

 “Validation” Status of Oracle on OEL 6.4 Targeted for 5.10 R6 As Well.

Citrix XenApp Support

 

History

 Citrix has been Supported for Years  Never Formalized by Facets in Compatibility Matrix

Actions

    Development to Adopt XenApp 6.5 for Subset of QA Deployment in 5.10 R6 “Supported” Designation in CM During 5.10 R6 “Validated” Designation in CM Upon Delivery of 5.10 R6 Hosting/Development Pursuing “Citrix Ready” Certification

And in Closing …..

Workshop Survey We would like to extend you an opportunity to provider candid feedback.

During the workshop you should’ve received an e-mail notification for you to take an on-line survey.

If you could take a few minutes to complete at this time, we would greatly value your feedback. For your convenience, the survey will be available throughout the remainder of the conference should you not be able to complete immediately.

The Cadence Journey

Transcript The Cadence Journey

Operational Advantages An Overview of Facets Release Management - Cadence & Agile Process

Agenda

The Cadence Journey

The Cadence Journey

The Cadence Journey

Yearly Releases:

Too Big!

8 Week Cadence:

Too Small!

Quarterly:

Just Right!

(For Now!)

The Cadence Journey

The Cadence Journey

Agile Release Development

Release Development

Release Development

Release Development

Release Development

Release Development

Release Development

Release Delivery

Release Delivery

Release Delivery

Release Delivery

Application Release Schedule

Release Adoption

Release Adoption

Release Adoption

Preparing for the Future

Upgrade Framework

5.2 Installation Re-Architecture

Test Automation & Refactoring

Services Development

Application Patterns

Collaborations

Vendor Platform Update

Expanding LINUX Support

Citrix XenApp Support

And in Closing …..

Workshop Survey We would like to extend you an opportunity to provider candid feedback.

Thank You!

Directory