skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.
Global Search Configuration

Introduction

How should a DevOps organization structure its people, processes, and tools? This is a question of implementation and adoption of DevOps practices, and the answer will vary according to where the organization is situated on its transformation journey.

Highlights

  • The key structural shift is an agile (e.g. Scrum) team that is cross-disciplinary not just across development-related silos (developers, testers, QA, security, DBAs, BAs) but which also includes operations and networking, making it a DevOps team.

Features and Benefits

  • The agile iteration is the heartbeat in a DevOps team, around which continuous integration and continuous testing form key activities.
  • Continuous delivery (CD) is the key supporting technology for DevOps, enabling rapid delivery into production at the speed the business wants it delivered.

Key questions answered

  • How should DevOps teams structure the team member roles in a large organization?
  • What is the role for governance in a DevOps organization?

Table of contents

Ovum view

  • Summary
  • DevOps people
  • DevOps processes
  • DevOps technology and governance

Appendix

  • Further reading
  • Author

Recommended Articles

;

Have any questions? Speak to a Specialist

Europe, Middle East & Africa team: +44 7771 980316


Asia-Pacific team: +61 (0)3 960 16700

US team: +1 212-652-5335

Email us at ClientServices@ovum.com

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Email us at pr@ovum.com

Contact marketing - 
marketingdepartment@ovum.com

Already an Ovum client? Login to the Knowledge Center now