Download as PDF, PPTX
Uploaded byEficode
A beginners guide to scaling DevOps
This document outlines 7 steps for scaling DevOps in an organization: 1) Don't force DevOps but show teams the benefits, 2) Research successful DevOps teams, 3) View DevOps as a journey not a destination, 4) Fake using DevOps tools and processes until teams adapt the mindset, 5) Create consistency across teams, 6) Plan infrastructure for rapid growth, 7) Seek help from DevOps experts when needed. It also identifies common hurdles such as disparate tooling, mindset issues, too many proposed changes, and security/compliance challenges.
More Related Content
Similar to A beginners guide to scaling DevOps
A beginners guide to scaling DevOps
- 1. GIULIO IANNAZZO |SOLUTIONS ENGINEER A beginner’s guide to scaling DevOps
- 2. Agenda Common hurdles DevOps levelset 7 steps
- 3. DevOps A culture wheredev and ops collaborate to build a faster, more reliable release pipeline.
- 4. Agenda Common hurdles DevOps levelset 7 steps
- 5. Disparate tooling Commonly leadsto miscommunication, wasted time, and mass confusion Common hurdles Disparate tooling Mindset Too many changes Security & compliance
- 6. Mindset “If it isn’tbroken, don’t fix it” mindset and cultural silos can stop a DevOps initiative in its tracks Common hurdles Disparate tooling Mindset Too many changes Security & compliance
- 7. Analysis paralysis Easy toget overwhelmed with the amount of possible changes included in “going DevOps” Common hurdles Disparate tooling Mindset Analysis paralysis Security & compliance
- 8. Security & compliance Current “enterprise-ready”tooling doesn’t support modern development techniques Common hurdles Disparate tooling Mindset Too many changes Security & compliance
- 9. Agenda Common hurdles DevOps levelset 7 steps
- 10.
- 11. 1. DON’T FORCEIT Don’t tell them, show them
- 12. LEADERSHIP SERVICE PROJECT TEAM HEALTH MONITORSTEAM PLAYS Team Playbook
- 13. Roles & Responsibilities Define roles& responsibilities and clarify team interactions Rules of Engagement Collaboratively define your team’s social norms Pre-mortem Prevent problems before they come to fruition Retrospectives Reflect on where can improve
- 14. 2. Do yourhomework Search out teams who have already experienced DevOps success and share it
- 16. Photo by Bryan Rodriguez on Unsplash 3.It’s a journey, not a destination
- 17. Process Make small processchanges, offer guidelines and guardrails Workshops Get teams together and run mock Agile sprints with new processes & tooling in place Tooling Get teams into the tools first, the mindset will come shortly after 4. Fake it till you make it
- 18. Build a foundation Sharebest practices, access WIP, manage 1 stack of tooling Customize where needed Customize workflows through integrations 5. Create consistency
- 19. 6. Plan forrapid growth Choose tools built to stay performant and cater to other enterprise needs
- 20. 7. When indoubt, get some help Get help from an experienced DevOps practitioner. Certified Solution Partners & Atlassian Technical Account Managers (TAMs) can help.
- 21. Set up guardrails Makeit easy to do the right thing and harder to do the wrong. Set up guardrails and lower your risk. Change up your team structure Create cross functional teams to share knowledge and speed up reaction times
- 22.
- 23. GIULIO IANNAZZO |SOLUTIONS ENGINEER Thank you!