Spring Cleaning Your Devops--Why Keeping It Fresh Is Crucial to Success.

Author:Kinsbruner, Eran
Position:DATABASE AND NETWORK INTELLIGENCE: OPINION - Development and operations

In rapidly evolving digital environment, where Agile and Digital Transformation strategies are helping the sawiest organisations deliver compelling and high quality services at speed, the idea of 'spring cleaning' isn't new.

It's not unusual to read articles which urge developers to 'get rid of it' if a product request or defect is more than a year old and still hasn't been prioritised. Also discussed is the idea that requests for functionality which aren't in line with immediate business priorities should be removed from a backlog. Simply, savvy developers know that if a backlog is relevant, minimalist and focused, then they'll find planning and prioritising much easier.

But, 'spring cleaning' goes way beyond clearing a backlog. Organisations that are committed to building a strong DevOps function, which has responsibility for the whole development process, must also ensure they've got the capacity to change rapidly, to experiment, to maintain quality and to continue to innovate.

The key to success is to continually re-evaluate three fundamental areas; people, processes and technology.


In the world of DevOps, skills are crucial. The developer's role is constantly evolving and teams are now tasked both with making apps and services and ensuring they are of the highest quality.

It's important that organisations are committed to upskilling their developers--and teams must continuously sharpen their own skill sets too, towards the goal of automating key activities during the DevOps pipeline.

To achieve better test and test automation the sawiest firms recognise the need to tackle skills gaps. For some, this means facilitating the mentoring of testers by highly qualified developers. And for others it means considering a change to software development practices. There are bound to be blind spots between developer, business and test personas and choosing development practices matched to team skills can contribute to accelerating development velocity. For some, ATDD (Acceptance Test Driven Development) works well. ATDD promotes defining tests as code is written. Test automation becomes a core practice during feature development rather than after feature development. And BDD (Behaviour Driven Development) which often implements test automation with simple English like syntax, serves less technical teams extremely well.


Good code is always tested and version controlled. And that also includes more than just making sure production code...

To continue reading