stephen renouf operational readiness 06-may-2015 release management framework overview

Stephen Renouf Operational Readiness

06-May-2015

Release Management FrameworkOverview

2

Agenda

1. Model of Release Management Being Rolled Out

2. How do Projects and Releases Relate to Each Other

3. Release Management Framework Overview

4. PMF and RMF Interface

5. Release Management Framework Artefact Alignment Map

6. Release Management Framework Forums

7. Release Management Framework Processes

Release Management Assessment

3

Model of Release Management Being Rolled Out

1. Consolidation of all planned changes into 3

standard release cycles (aka Release Trains)

• Monthly Release Train2 month cycle (~1 month delivery, 1 month test)

• 2 x Once Every 2 Months Release Trains4 month cycle (~2 month delivery, 1.5 month test)

Pieces of work requiring more than a 1.5 month test window will be release engineered to fit inside standard release trains


4

Model of Release Management Being Rolled Out


5

How do Projects and Releases Relate to Each Other


Projects have 0 to many releases

Releases contain 0 to many Projects(and other content)

6

Release Management Framework Overview


• Release Management will be delivered in a similar way to Project Management with a guiding Release Management Framework of processes and artefacts

• Release Management Framework has five Phases:

• Release Pipeline• Release Engineering• Release Scoping• Release Delivery• Release Warranty

• Within Release Delivery Phase there are five Release Stages

• Development• Release Candidate• Systems Testing• User Testing• Production Candidate

7



Phase Overview – Release Pipeline Key Inputs

There are four key goals of the Release Pipeline Phase:

• Capture all planned changes and ensure they are accurately reflected in the forward schedule of release

• Agree provisional target release dates for non small and medium change content

• Ensure all small and medium change pass through the pipeline process providing high level design approval, estimation and business prioritisation

• Ensure content is in a suitable state to support release engineering

• Known Errors• Small / Medium Change Requests• Application Maintenance Requests• Service Improvement Activities• Infrastructure Requirements• Technical Debt for Remediation• Projects and Programs

Key Outputs

• Forward Schedule of Release• Early Environment Requirements• Early Resource Requirements

8



Phase Overview – Release Engineering Key Inputs

There are five key goals of the Release Engineering Phase:

• Turn requirements and design into a delivery backlog and dependency map

• Agree a release delivery strategy for any items that need / would benefit from being split over multiple releases

• Where appropriate agree to de-risk delivery through configuration bound behaviour, parallel infrastructure and other similar strategies

• Establish detailed environment and resource requirements

• Establish DevOps enhancements to support new platforms / changes to delivery strategy in upcoming release

• Prioritised Small and Medium Changes

• Change Requirements• Detailed Design (Project / Program)• High-Level Design (Small / Medium)• Other changes requiring release

engineering

Key Outputs

• Development Backlog• Backlog Dependency Map• Project Release Delivery Plan• Project Test Strategy• Project Application Scope List• Environment Requirements• Resource Requirements• Dev Ops Platform Changes

9



Phase Overview – Release Scoping Key Inputs

There are five key goals of the Release Scoping Phase:

• Agree the committed and candidate content that will form the scope of a release

• Agree the draft plan of how the committed content will be delivered within the release development cycles

• Agree upon the testing approach that will be used to build quality into the release

• De-risk delivery by ensuring plans are in-place to seamlessly remove any high-risk content that could jeopardise the release

• Agree the branching and merging plan that will be used to support the release

• Development Backlog• Backlog Dependency Map• Project Release Delivery Plan

Key Outputs

• Release Backlog• Release Dependency Map• Development Cycle Plan• Committed Content• Candidate Content• Master Test Approach• Environment Plan• Branching and Merging Plan

10



Phase Overview – Release Delivery Key Inputs

At the core of the RMF is the Release Delivery Phase which is compromised of five stages of delivery:

• Development• Release Candidate• Systems Testing• User Testing• Production Candidate


Key Outputs

• Successful production implementation of changes within the scope of the release

• Development Cycle Retrospectives• Development Exit Report• Test Cycle Retrospectives• Test Exit Report• Post Implementation Review• Release RAID Log• Release Defect Log

11



RELEASE DELIVERY PHASE

Stage Overview – Development Key Inputs

The “Development” stage of the Release Delivery Phase is the core of the factory where the source code or configuration set are configured.

Key goals of the release management framework is to build quality into the development processes to prevent re-work and increase the overall delivery efficiency

As QBE’s delivery methodology matures the aim is to start integrating embedded testing, show & tells and our global continuous integration framework into the development stage


Key Outputs

• Source Code / Config Set• Unit Test Evidence• Unit Test Signoffs• Implementation Steps• Build Configuration Scripts• Security & Standards Review• Peer Review

12




Stage Overview – Release Candidate Key Inputs

The “Release Candidate” stage of the Release Delivery Phase is where release is staged up ready to be deployed into test environments when the next “Release Candidate” is taken.

Whilst continuous integration practises are not embedded in the development cycle key activities include:

• Source Code / Configuration Merging• Build Preparation• Implementation Scripting• Implementation and rollback testing

• Source Code / Config Set• Unit Test Evidence• Unit Test Signoffs• Implementation Steps• Build Configuration Scripts• Security & Standards Review• Peer Review

Key Outputs

• Release Candidate• Implementation and Rollback

Signoff• Deployment Approval

13




Stage Overview – Systems Testing Key Inputs

The “Systems Testing” stage of the Release Delivery Phase is where release candidate goes through the various types of systems testing.

Whilst embedded practises are not embedded in the development cycle key activities include:

• Functional Systems testing• Integration Testing• Systems Regression Testing• Systems Performance Testing• Operational Readiness Testing• Infrastructure Resilience Testing• Disaster Recovery Testing• Security Testing

• Release Candidate• Implementation and Rollback

Signoff• Deployment Approval

Key Outputs

• Signoffs and Evidence for appropriate types of testing

• Functional• Integration• Regression• Performance• Security etc.

14




Stage Overview – User Testing Key Inputs

Similar to the “Systems Testing” Stage the “User Testing” Stage focuses on user acceptance of the changes, key activities in this stage include:

• User Acceptance Testing• Operational Acceptance Testing

• Signoffs and Evidence for appropriate types of testing

• Functional• Integration• Regression• Performance• Security etc.

Key Outputs

• User Acceptance Signoff• User Acceptance Evidence• OAT Signoff• OAT Evidence

15




Stage Overview – Production Candidate Key Inputs

The Production Candidate stage is the final barrier checkpoint between the delivery and implementation of a release, key activates in this stage include:

• Verification of signoffs and evidence collected during release cycle

• Re-run of the consolidated Implementation and Rollback in the pre-production environment

• Preparation and approval of the change records needed to authorise production deployment

• Implementation of the change set itself• Post Implementation Verification

• Testing Signoffs• Implementation Plans• Implementation and Rollback

Signoff

Key Outputs

• Service Transition Signoff• CRM Record• PIV Signoff• PIV Evidence• Successful Implementation

16



Phase Overview – Release Warranty Key Inputs

There are three key goals of the Release Warranty Phase:

• Ensure appropriate support is provided to the support organisation from the delivery organisation

• Identify production defects that were missed through the quality stages of the release cycle

• Amalgamate the lessons learnt during the Stages of the Delivery Phase and identify improvement initiatives to drive the process and framework forward

• Development Cycle Retrospectives• Development Exit Report• Test Cycle Retrospectives• Test Exit Report• Post Implementation Review• Release RAID Log• Release Defect Log• Production Problems & Incidents

Key Outputs

• Post Release Review• Post Warranty Review• Lessons Learnt• Improvement Initiatives

17

PMF & RMF Interface

1. Release management processes start in Define with awareness and high level evaluation2. Core release processes kick in once Project Requirements and technical design has been

completed at this point Release Managers will be taking over responsibility for the IT delivery turning the requirements and design into a delivery backlog and agreeing delivery options, associated timelines and costs with the PM.

3. Through the Execute Phase the Release Manager manages the project releases keep the project aware of progress, issues, risks and any prospect of a change in delivery time or cost. The RM is responsible for the IT Delivery accountable to the PM who remains responsible for the overall project delivery


18

RMF - Artefact Alignment Map


19

RMF - Process Alignment Map


20

Release Management Forums


Release Engineering

Landing Slot Approval Forum

Projects

CoreRelease ScheduleService OwnersService Owners

Project Releases

Changes to ProjectRelease Schedule

InterimRelease

Requirements

Release ManagersRelease ManagersForward Schedule

of Release

R15.1 R15.2 R15.3 R15.4 R15.5 R15.6 R15.7

R15.2 R15.4 R15.6 R15.8

R15.3 R15.5 R15.7R15.1

Monthly Release Train

Every 2 Months Release Train 1


Release Planning

Release Control Board



Release Control

Project ManagerProject Manager

Enterprise Release Control Board

Transition Approval Board

Service Transition

Service Requirements

Service Design

ServiceTransition

ServiceIntroduction

TransitionWarranty


Service Design

ServiceTransition

ServiceIntroduction

TransitionWarranty


Service Design

ServiceTransition

ServiceIntroduction

TransitionWarranty


Service Design

ServiceTransition

ServiceIntroduction

TransitionWarranty

Enterprise Transition Board

Portfolio Meetings

Environment Control Board

Change Advisory Board

Infrastructure Release Interlock

21

Release Management Forums


R15.2 R15.4 R15.6 R15.8

R15.3 R15.5 R15.7R15.1



R15.3

Release Planning Dev Cycle 1 Dev Cycle 2 Dev Cycle 3 Test Cycle 1

Release Operations

Test Cycle 2 Implementation Phase Warranty

Portfolio Meetings

Environment Control Board

Change Advisory Board

Infrastructure Release Interlock

Development Cycle Planning

Development Cycle Look

Ahead

Development Cycle

Retrospective

Development Control

User Group Meetings

Release Scoping Meeting

Release Scope

Test Cycle Planning

Test Cycle Retrospective

Development Progress and Defect Review Standup

Test Control Feedback Loop

Post Release Review

Post Warranty Review

Implementation

Implementation Walkthroughs

Post Implementation

Review

22

Questions and answers


Stephen RenoufRelease Managertelephone +44 (0)1245 247339 / [email protected]://oneintranet.qbe.eo/sites/QBETeamsites/itrelease/SitePages/Home.aspx

Thank you

http://oneintranet.qbe.eo/sites/QBETeamsites/OR/SitePages/Home.aspx



24

The information contained herein has been prepared by QBE Insurance Group Limited or one of its subsidiaries (“the QBE Group”). Such information is confidential and is being provided to you solely for your information. It is not intended to create any duty towards you or any other business or legal relationship. The QBE Group makes no warranty or representation of any kind in respect of this information, in particular as to its accuracy, completeness, timeliness or suitability for your purpose. To the fullest extent permitted by law, the QBE Group disclaims any responsibility or liability for any loss or damage suffered or any costs incurred arising out of or in connection with your reliance on the information contained herein.

Some of the information in this presentation may contain projections or other forward-looking statements regarding future events or the future financial performance of QBE. The inclusion of such forward-looking information shall not be regarded as a representation by QBE or any other person that the objectives or plans of QBE will be achieved. QBE undertakes no obligation to publicly update or publicly revise any forward-looking statement, whether as a result of new information, future events or otherwise.

By accepting a copy of this presentation, you agree to be bound by the foregoing limitations and conditions and, in particular, will be taken to have represented, warranted and undertaken that you have read and agree to comply with the contents of this disclaimer.

The reproduction or transmission of all or part of this document, whether by photocopying or storing in any medium by electronic means or otherwise, without the written permission of the owner, is prohibited.

© QBE European Operations 2015.

Disclaimer


stephen renouf operational readiness 06-may-2015 release management framework overview

Documents

release delivery phase

release delivery strategy

project management

release pipeline phase

release engineering

standard release cycles

month delivery

delivery backlog