DevOps-driven development and delivery

Helen Beal has twenty years’ experience working in the technology industry with a focus on the Software Development Lifecycle for a wealth of cross-industry clients in the UK and abroad. Helen is passionate about DevOps and is the creator of the Ranger4 DevOps LiftOff Workshop and the Ranger4 DevOps Maturity Assessment – winner of the IBM Beacon Award 2015 for Outstanding DevOps Solution. She also started Ranger4’s #DevOpsFriday5 initiative and is on the Board of Regents at the DevOps Institute (Ranger4 are also a Registered Education Provider for the DOI’s DevOps training courses). Helen is also a novelist and ecologist. She once saw a flamingo lay an egg.

While we are on the topic of DevOps-driven development, make sure you check out Rami Sass’ cheat sheet of tools and practices that can help your team become a lean, mean, DevOps machine:

#1 Continuous Integration
#2 Software composition analysis
#3 Teamwork makes the dream work

As the pressure on software organizations to deliver innovative products and ship updates fast continually increases, there is more and more talk in our software development ecosystem of adopting the DevOps model for its increased efficiency and agility. DevOps promises to help teams keep on schedule without compromising quality, even when bypassing slower manual testing and bug fixing that would traditionally come at the end of the process.

When you think about it, the developers and the DevOps attitude aren’t really all that far from each other. Developers are a limber bunch, eager to innovate, quick to learn new languages and adopt new methods when necessary. While no one likes their day to day to be disrupted, the changes that we recommended here have already helped dev teams deliver swiftly, while eliminating tedious manual tests and last minute all-nighter fixes. One last tip that is important to remember is that change doesn’t happen overnight, it is a process. Don’t be daunted by the big buzzwords.

See the full article here.