Here are some things I think you should consider if you look at implementing DevOps and Continuous Delivery.
I will expand on some of these in later posts.
Know the background
The movements of DevOps and Continuous Delivery can be said be solutions or reactions to some common problems we have in traditional software development (more on this in a later post). Implementing DevOps and Continuous Delivery has shown to be a very effective way to solve these problems and create an agile business. DevOps and Continuous Delivery can nowadays be seen as standard in our line of business.
Understand the principles
With traditional development I mean everything that is not part of agile ways of developing software. Traditional development is often called waterfall development or stage-gate development. Agile ways of developing software are often placed under names such as Agile, Lean, Scrum and Kanban.
Under all of these ways of working are important principles we need to understand in order to succeed in implementation. This is especially true for organizations used to work in the traditional way. So: focus on understanding the principles!
Prepare as a leader
When as a leader you start to understand the principles and the differences between agile and traditional you pretty quickly see that changes are needed in widely different areas. You see that changes are required in processes, tools, organization, project-steering and leadership but perhaps mostly in basic assumptions about work (for example Pull instead of Push). This is an exciting discovery since this new way of working hold so much promise for the future!
You also discover that the required changes are connected and reinforce each other. You realize that the journey you are about to begin when you start implementing DevOps and Continuous Delivery is far more extensive than just making changes in delivery and deployment.
Make the case
Is it worth it? The answer in recent years has been a clear yes since DevOps, Continuous Delivery, Agile and Lean has been thoroughly validated as the way to act to meet the requirements of the future. In other words there are many examples of public, private and governmental organizations that has changed with very good results.
Should you dare? The answer is mostly a clear yes since the consequences of not jumping on this “paradigm shift” are unacceptable.Recommend this post
Latest posts by Emil Vikström (see all)
- “Big 5” dangers for your software company - March 10, 2015
- How to produce successful change - November 19, 2014
- Guest blog: Stepping Stones into the Future through Leadership Agility at Ericsson - September 1, 2014
Copyright © 2014 Emil Vikström. All Rights Reserved.