DevOps-driven development and delivery
How many of you are familiar with terms like test, value or behavior-driven development? In this talk, Helen Beal goes over these terms and dives into DevOps-driven development and delivery.
How do you drive development? Via test? Value? Behavior? How do you drive operations? Are they Agile? And Lean?
In this talk, Helen explores the characteristics of DevOps-driven development and delivery, the best practices for regulating organizations where security and auditability are key and what this means for the way we manage change, funding, safety, failure, and experimentation.
SEE ALSO: “Continuous Delivery is a game-changer”
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.