3. Service Operations Organization
DevOps live happily ever after over
the cloud infrastructure. Every
aspect written as a code, whenever a
feature fail, simply revert back to the
last code and the show continues
giving time and space to rework the
code or fixing the bugs.
The rest handled by providers.
Service Operations Organization is the provider, the team that drive the infrastructure
4. Why?
• Did you already transforming?
• Is it successful?
• Define success
• On time and meet budget is not enough, is it valuable?
12. Scale the Agile Practices
• Setup scaled agile forum & events
• Allow teams to shape their interaction
• Manage relation across team
• Setup full value stream
13. The Dev andThe
Ops
We Combine Scrum, and Kanban
framework to establish how Agile
Development andAgile Operations
works together within our Service
Operations organization
Agile Dev Agile Ops
14. Dual Band Operating Model
Product Backlog Sprint Backlog Iteration
Requests Small Iteration
Incidents
Agile Dev using Scrum
• Common weeks long iteration
• Handle product backlog
• Prioritized and estimated item selected into iteration
• Deliver working software & measurement metrics to the
Ops
Agile Ops using Kanban
• Iteration as small as 1 day
• Handle requests and incidents
• Prioritized and verified work item set on queue
• Leverage User Stories to the Dev
15. DevOps in Service Operations
Continuous
Creation
Continuous
Resilience
Continuous
Improvement
Define Empathize
Continuous Design
16. Measure & Make Sure
• User Experience
• The system solve user’s problem
• The value proposition is better than the
current alternative