SERVICE OWNER
To treat Service as a Product
Coordinate Multiple Teams
Keep Integrity of Service Container
Buddying with PO
Communicating Changes
Repository Strategy
Feature Branching
Confirming CONTRACTS are Honoured
Weekly Service Owner standup
Allowing PEOPLE to Move On
Clarity on WHO to GO
Decide WHICH Changes do we PUSH into PROD
DESIGN or Validate DESIGNS
To Be CONSULTED up front
Service Developers
BFS Channels / POs / CPOs
Participate in all Planning Session (???)
INCREASE Quality
REDUCE DownTime
Standardisation
Standard RollOuts
INCREASE Acountability
Open Source Culture
Sharing Responsabilities
Everyone is LandLord
Autonomy to CHANGE (meeting Biz needs)
Allocating TIME to Own
Access to Logs and Tools
Avoid Bottlenecks
REDUCE Cycle Time
Decide Service ROADMAP
Support other Channels
PLAN
Release Plannnig Management