S is for Sharing tells the father of Devops, Patrick Debois
Patrick tells us of the importance of sharing within the Devops culture and how to go about implementing the concepts
The final keynote of JAX London was delivered by the Father of Devops, Patrick Debois outlining the importance of Sharing within the Devops culture.
The methodology that take the Agile manifesto to the next level has certainly garnered fans and critics in equal measure, but Debois still believes that in some big companies “there’s still a big divide between development and operations”.
Fortunately the Atlassian worker was on hand to offer “a vision into the future” and insight into how to best implement just some of the key Devops concept within even the most steadfast environment.
The word “sharing” formed the basis of the presentation – whether sharing the vision from all angles of the company (from idea inception from the business right up to the user, with developers and operations in the middle) or sharing tools, the codebase and successes/failures. The collective spirit is crucial to Devops.
Debois stated that identifying the bottlenecks throughout the company (either through continuous delivery or monitoring and metrics from the ops side) was the catalyst for seeing Devops’s benefits. He even admitted that the Devops concept might seem obvious, that two groups of people should fundamentally talk to each other and not be siloed.
He added: “You’re thinking this is so obvious but it’s not. It’s like telling your children to brush their teeth – they know they should do it, but you have to keep telling them.”
Whilst quickly covering Continuous Delivery (with an hat tip to Thoughtworker Jez Humble), shared knowledge such as one ticketing system and shared experience tools like Netflix’s random server killer Chaos Monkey, Debois certainly provided a convincing case for why we should all adopt some Devops principles whenever possible.
He even offered views on how to extend beyond just Dev and Ops, into the financial and HR areas of the business to get everyone talking. One interesting note from the end from Debois was that the trademarking of Devops was turned down, due to so many people talking about it – no one could claim the sole rights to it. If that doesn’t tell you how much Devops has permeated the enterprise, then what does?
Check out Patrick’s presentation on Slideshare – well worth reading if you need a hand getting started!