Service Owner Impact Map
Show Stats
KPIs
WHAT - Deliverables
HOW - Impacts.
WHO - Main Actors who can make an impact in the Outcome. Who does this, Obstructs, Uses, is Impacted
WHY - Purpose. Main reasons to formalise this new Role
PROD Support
Handover Services (Support)
24x7 (???)
Patching (???)
REDUCE Prod Incidents
SERVICE OWNER
Decide Service ROADMAP
Release Plannnig Management
PLAN
Support other Channels
Avoid Bottlenecks
REDUCE Cycle Time
INCREASE Acountability
Access to Logs and Tools
Open Source Culture
Allocating TIME to Own
Autonomy to CHANGE (meeting Biz needs)
Everyone is LandLord
Sharing Responsabilities
INCREASE Quality
Standardisation
Standard RollOuts
REDUCE DownTime
Clarity on WHO to GO
To Be CONSULTED up front
Participate in all Planning Session (???)
BFS Channels / POs / CPOs
Service Developers
DESIGN or Validate DESIGNS
Decide WHICH Changes do we PUSH into PROD
Allowing PEOPLE to Move On
Keep Integrity of Service Container
Weekly Service Owner standup
Confirming CONTRACTS are Honoured
Feature Branching
Repository Strategy
Communicating Changes
Buddying with PO
To treat Service as a Product
Coordinate Multiple Teams