DevOps 101

by Süleyman Petek 18. October 2015 19:27
Yet another trendy word in IT world is "DevOps". It is an abbreviaton for Development and Operations

Yet another trendy word in IT world is "DevOps". It is an abbreviaton for Development and Operations. At first look it seems like that it is the combination for Development and Operations as it's name but we should see it as a cultural change. It is not a new technology or a product. This cultural change requires development teams to accept feedbacks from operation teams and consecutively operation teams need to accept frequent updates from development teams. Adapting to the new style of business requires IT to be effective at managing risk while moving faster.


The combination of speed and effectiveness helps make businesses more agile. DevOps overlaps with Agile in the concepts such as Individuals, Interactions and Collaboration. DevOps extends Agile approaches and applies them to the whole organization, not only the development process. Only creating a team called "DevOps" or renaming an existing team to "DevOps" just to check off an item on a checklist  is  neither  necessary  nor  sufficient  for  creating  a  DevOps culture. If  your organization is in a state where the development and operations teams cannot communicate with each other, an additional team adds the potential for more communication issues. (n*(n+1))/2 communication paths, remember.

It is grounded in a combination of speed, efficiency and quality methodologies: 

  • Agile software development
  • Lean Manufacturing 
  • Kaizen 
  • Six Sigma

What DevOps brings to you ?

  • Speed in Release Cycle
  • Shorter Delivery Times 
  • Unified Tools and Process 
  • Integration among different teams
Communication, Integration and Collaboration are the keywords. In order to implement Devops, first of all you should break down the barriers between teams, give people shared responsibilities, focus on business not the technology and build trust in everything.

We can list DevOps principles like below;
  • Culture
  • Automation
  • Measurement
  • Sharing
and we can list DevOps practices ;

  • Version Control For All
  • Automated Testing
  • Proactive Monitoring and Metrics
  • Kanban/Scrum
  • Visible Ops/Change Management
  • Configuration Management
  • Incident Command System 
  • Continuous Integration/Deployment/Delivery
  • Virtualization/Cloud/Containers
  • Transparent Uptime/Incident Retrospectives

Find ways to collaborate and involve others early, find ways to automate and make self service, become metrics driven, metrics are your friend, demand measurable outcomes, learn new things, fail fast, continually improve, understand the larger business goals, metrics, and priorities you support. Communicate, be open and honest and build on small successes to gain broad support for more substantive change. Finally, align roles and responsibilities across groups, enable collaboration.

Tags: , , ,


Comments (1) -

Kerem Öztürk
10/19/2015 10:43:48 PM #

Nice article.

Can you elaborate a little bit about the benefits of DevOps approach to secure software development lifecycle ? Any significant changes expected to more secure code development as the term "Agile" usually understood as "do not plan, deliver quickly and forget about security" ?


Add comment


<<  June 2021  >>

View posts in large calendar