Getting Your Organization Excited About Continuous Development
Continuous Delivery Consultant at Diabol AB
Continuous delivery is about making sure an application is always in a releasable state, where manual, repetitive, and error-prone tasks related to a release, such as setting up servers and middleware, have been fully automated. Many discussions on continuous delivery focus on the automation and tooling aspects, but it’s important to remember that continuous delivery requires more than just tools and products to succeed. To successfully implement continuous delivery, you need to change the culture of how an entire organization views software development efforts.
Change is easy to introduce in an organization. The difficult part is making it stick. This is especially true when starting an effort to introduce continuous delivery in an organization, whether it’s imposed by management or an initiative from developers tired of their unproductive, old-fashioned way of working. Every member the initiative affects must understand the benefits of the implementation and how it will affect the way they do their daily work. This is typically not done through one or a couple of formal meetings, where the organization’s management presents the continuous delivery efforts. This is something that has to be done continuously; it has to be rooted in every employee working in the software development departments.
It is also important that all employees feel that they have the proper forum in which to discuss how continuous delivery will affect their daily ways of working. Even after continuous delivery has been introduced, team members will need reminders of why, for example, manual changes to environments are bad or how shortcutting the deployment pipeline negatively affects the overall quality of the system and undermines the continuous delivery principles as a whole.
The biggest boost an organization can get when implementing continuous delivery is to get people excited and passionate about it.