Upload
builiem
View
224
Download
9
Embed Size (px)
Citation preview
SESSION 501 Thursday, November 3, 11:15 AM - 12:15 PM
Track: DevOps and Agile
Change Management in a DevOps World
Greg Sanker Enterprise Support Operations Manager,Oregon Department of Transportation [email protected]
Session Description
With DevOps taking the world by storm, is ITSM-based change management hopelessly outdated? In this session, you’ll learn a practical approach for maturing your ITSM change program for DevOps, discover the key differences between change enablement and change management, see how you can integrate DevOps into enterprise change management, and see what legacy change management mistakes you can kiss goodbye. (Experience Level: Intermediate)
Speaker Background Greg Sanker is an ITSM blogger, speaker, and practitioner with decades of global IT experience with organizations ranging from Fortune 10 tech giants to the public sector. After leaving the corporate life, Greg headed the service management office at a state agency, where he led the adoption of a basic change management program. Greg’s blogs about excellence in ITSM can be found on ITSMTransition.com.
Change Management in a DevOps World
Greg Sanker
Session Overview
• What is change management
• What’s wrong with (traditional) change management
• Radical thoughts on managing change
• Turning change management on its ear
The Point of Change Management
• Support timely and effective implementation of business-required changes
• Appropriately manage risk
• Minimize negative impact
• Ensure changes achieve desired business outcomes
What’s Wrong with Change Management?
Bureaucratic
SlowRather have a root canal
Painful
Hostile
DelaySlow down
Unfriendly
Red tape
InquisitionWaterfall
marath
on
meetin
gs
Unnecessary
Cross Examination
CAB Meeting
Gruling
Idiotic
Waste of Time
Terrible
Avoid at all cost
Interro
gation
Archaic
Obsole
te
fossil
Terrible
extinct
antiquated
Paper shuffling
Heavy h
and
ed
antiquated
What’s Wrong with Change Management?
• Quality Assurance (inspection)
• Vertical (soloed)
• Museum piece
• CAB meeting is a bottleneck
Tradition IT Value Stream
If Formula 1 adopted Change Management…
• High risk
• All changes must come to CAB
• Unauthorized changes will not be tolerated
• CAB before every pit stop (aka “change window”)
Unauthorized Changes
• Unauthorized changes to throttle position sensor (aka accelerator)
• Multiple unauthorized gear changes
• Untold numbers of unauthorized brake applications
The need for speed
• Measure time to value
• Is the increase in quality more valuable than the opportunity cost?
• Must match the rate of change required by the business
• Faster is not always better
Change Management vs Change Enablement
• Reactive
• Impact reduction
• Loss elimination
• Proactive
• Capability building
• Outcome
• Value realization
0
+
-0
+
-
“Cease reliance on mass inspection…”
• Engineer Quality into the process
• Toyota Production System
• Focus on the flow
Maturing CAB-Based Change Management
• Standard Changes
• Change Models
• Delegated Change Authority
Maturing CAB-Based Change Management
• Standard Changes• Change Models
• Delegated Change Authority
• Low Risk
• Performed frequently
• Follow documented process
• Pre approved
Maturing CAB-Based Change Management
• Standard Changes
•Change Models• Delegated Change
Authority
• Change templates
• Like changes performed in similar, repeatable ways
• Ensures key predefined steps are taken
• Reduces change risk
• Increases change precision
Maturing CAB-Based Change Management
• Standard Changes
• Change Models
•Delegated Change Authority
• Establish change authority
• Lower risk changes delegated to lower approvers
• Push authority close to the work
• Requires clear authority domains
Dump the change management junk
• Mother-may-I CAB
• CAB as quality inspection
• Concentrate authority with change manager
Change Management is…
• Focused on flow of changes, not individual change
• a feedback mechanism, not a process
• About outcomes
Questions…
?
[email protected] @gtsanker