View
109
Download
5
Embed Size (px)
Citation preview
AGENDA
1
• What is Release Management
• Scope & Types
• Main Activities & Timeline
• Questions
B Y T I J S V A N V E L T H O V E N
WHO ARE RELEASE MANAGEMENT?
Release Management:Part of IT Service Delivery – Service Transition Management
Team located in China (insert Org Chart here)
Release Manager – xxx
Operational Process Manager – Tijs van Velthoven
Release Process Manager –
Related Service Manager –
3B Y T I J S V A N V E L T H O V E N
WHAT DOES RELEASE MGT. DO?
4
Release Management Team coordinates and manages
various types of software updates by:
• Managing planning in Release Calendar
• Collecting content
• Coordinating testing of releases
• Coordinating communication and distribution of releases
• Evaluation and improvement of entire release cycle
B Y T I J S V A N V E L T H O V E N
SCOPE OF RELEASE MANAGEMENT
Contents
Security Update
COE Application
update
Build
5B Y T I J S V A N V E L T H O V E N
SCOPE OF RELEASE
MANAGEMENT
6
Infra Devices
ServersInfra
Managed
Workstations
Workstations
Laptops
B Y T I J S V A N V E L T H O V E N
RELEASE CALENDAR
7
• Release Calendar is a time schedule
of all release activates and must be
strictly followed
• It’s planned by Release Manager and
approved by xxx 1 year ahead
• Release Calendar is published on
free-access SharePoint
B Y T I J S V A N V E L T H O V E N
RELEASE CALENDAR
8
Quarter End Freeze : No Roll-
out to Production
Monthly Security Update
Quarterly COE Update
Network MaintenanceWindow
B Y T I J S V A N V E L T H O V E N
Two main types of Release-categories:
• Security Update
• COE Update
• Build Upgrade
TYPES OF RELEASES
10B Y T I J S V A N V E L T H O V E N
TYPES OF RELEASES
COE UPDATES
11
• Frequency – Quarterly (4x per year)
• Bug fixes and functional updates
• New OS (Windows) service packs
• Removal of COE applications
B Y T I J S V A N V E L T H O V E N
TYPES OF RELEASES
SECURITY UPDATES
12
• Frequency – Monthly (12x per year)
• Risk for not implementing is high
• Content - Security patches issued by Microsoft only(discussion on patching non-MS applications on-going)
B Y T I J S V A N V E L T H O V E N
TYPES OF RELEASES
BUILD UPGRADE
13
• Combination of COE Update + Security Update
• Frequency – Twice a year
• Roll out via
• COE Update (running PC)
• USB Sticks (re-staged PC)
• DVD (server build)
B Y T I J S V A N V E L T H O V E N
Preliminary Freeze
Develop Build
Content Freeze Test Build
Build Freeze
In-house/Busi
ness TestPilot Test Roll out
MAIN ACTIVITIES
15
• Security Update & COE Update follow same process
• Security Update - 4 weeks preparation cycle
• COE Update - 13 weeks preparation cycle
B Y T I J S V A N V E L T H O V E N
Preliminary Freeze (PF)Preliminary Freeze (PF)Preliminary Freeze (PF)Preliminary Freeze (PF)
16
Monthly Security Update Release: OE selects contents based on pre-agreed parameters
COE Update Release: Content added through Change Process; ‘anyone’ can request content
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
DEVELOP BUILD
17
Monthly Security Update: NA
COE Update: A new version of the Build will be created based on:
• Latest COE Build
• All COE-content released since last Build Creation
• All Monthly Security Update-content released since last Build Creation
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
CONTENT FREEZE
18
Monthly Security Update: OE distributes ‘patch-list’ to inform stakeholders about contents of upcoming Security Update
COE Update: Release Manager distributes content-list to Service Management for review and approval
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
TEST BUILD & BUILD FREEZE
19
Monthly Security Update: NA
COE Update: Two goals:
- see if installation runs smoothly
- see if daily operation is disturbed by any content
Handover for further testing
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
IN-HOUSE TEST – BUSINESS
TEST
20
• In-House Testing• Performed by delegation of IT Service
Delivery
• Business Testing• Performed by delegates of BU’s to ensure
CGXP-Compliance
• Approval of the tested Services
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
PILOT TEST
21
• First wave of release deployment in production environment
• Approximately 250 participants
• incl. 180 Business-users
• Critical phase for testing content & deployment success
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
ROLL OUT
22
First Site
ROWRoll Out
First Site Roll-Out:
• Approximately 1000 PCs (IT Services Board)
• x FAP servers
ROW (Rest of the World):
• Approximately 25,000 PCs and Servers
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
DEPLOYMENT STRATEGY
The RollThe RollThe RollThe Roll----Out of Releases is done following a ‘Deployment Out of Releases is done following a ‘Deployment Out of Releases is done following a ‘Deployment Out of Releases is done following a ‘Deployment
Strategy’Strategy’Strategy’Strategy’
Monthly Security Update:Monthly Security Update:Monthly Security Update:Monthly Security Update:� Always ‘Pushed’
� Content deployed and installed unnoticed by end-user
COE Update: COE Update: COE Update: COE Update: � Three-phase roll-out plan
� May involve end-user interaction and possible re-boot of workstation
23
Preliminary Freeze
Develop Build
Content Freeze Test Build Build
Freeze
In-house/Bu
siness Test
Pilot Test Roll out
B Y T I J S V A N V E L T H O V E N
COE UPDATE DEPLOYMENT PROCESS
24
Pull
•Pull Installation•Download & installation of content initiated by end-user
•This option is NOT available for VPN connected user
•Scheduled Pull Installation : 2 weeks for COE update
Push @ Next Logon
•Push at Next Log-on•Automatic installation of content per next log-on to
workstation
•Scheduled Push at Next Log-on :1 week for COE update
Normal Push
•Forced Push•Automatic installation of content within one (1) hour of
receiving content on workstation
•Scheduled Normal Push :1 weeks for COE update
B Y T I J S V A N V E L T H O V E N