Now on DevOps Radio: Juni Mukherjee of Atlassian on the Art of Digital Transformation

Devops RadioIn this episode of DevOps Radio, Juni Mukherjee, Bitbucket developer advocate at Atlassian, discusses some of the current trending topics in software development with host Andre Pino, including digital transformation, women in tech and DevSecOps. Juni’s extensive resume spans the software development lifecycle at numerous companies including Gap and Walmart, and she has also authored a book on DevOps titled, Continuous Delivery Pipeline - Where Does It Choke?

Juni ultimately gravitated toward DevOps to address some of the pain points she experienced as a developer, such as the days of war rooms for software releases (thankfully, they are gone). Additionally, with the number of security breaches over the last several years, DevOps teams are fighting back by transforming their software delivery processes to DevSecOps. This trend is all about ensuring that security starts at the beginning - with the code-writing phase. DevSecOps shifts security left, into development. This is different from just a few years ago, when security testing would occur once the product was almost ready to be deployed to production. This usually meant delays, as it was the first point in the process that security was thought about and, inevitably, there would be issues. Juni refers to this old way of security testing as “dis-continuous delivery” (LOL - how apt!) and reiterates that the best strategy is to build security in from the beginning.

In her current role, Juni guides developers through digital transformation with continuous delivery. While digital transformation may be defined differently from organization to organization, Juni recommends that rather than establish KPIs, organizations should identify what success looks like for them (for example, is it faster time to market? Fewer errors?). However, she is also quick to debunk the myth that transforming successfully to continuous delivery equates to a successful business transformation. While it may be faster, an organization might just be shipping bad code faster, because there aren’t enough tests in the delivery process or maybe the product isn’t what customers are asking for. That doesn’t translate into revenue or any return for the business. As Juni says, “The product still has to be a very good, nice, kick-ass product.” There is no substitute for good code and excellent products.

For more expert advice on DevOps and continuous delivery, check out this episode of DevOps Radio on the platform of your choice: the CloudBees website, iTunes and NEW this month on Spotify. Then, start a conversation on Twitter by tweeting to @CloudBees and include #DevOpsRadio in your post.