Scott Ambler is a well-known expert in the practice of Disciplined Agile Delivery (DAD). It’s very much in the thinking of things that we promote around here: holistic, teamwork-oriented and better for the business. It is also an attempt to place an end-to-end framework onto Agile that is mostly absent in such practices as Mary and Tom Poppendieck’s Lean Software Development (our Leadership interview with them is here).
Scott has seen Agile adoption in large companies, helped facilitate adoption and use in large companies, and seemed like a natural to have in the series.
Sco Scott: Yes, Disciplined Agile Delivery is a process decision framework. And what – it came about from my work […and] what happened was a bunch of us started observing what successful organizations were doing in practice with Agile delivery. And one of the things we observed was that the more successful ones had DevOps practices and philosophies linked right in.
That’s basically the approach we took with Disciplined Agile Delivery. We said, hey, DevOps is critical to your success in modern software delivery. So, we said we’ll better just build it right in and make it clear and obvious from the start. So, that’s what we did.
So Disciplined Agile Delivery is basically – we just observe what’s working well and what’s not working well. And we try to do stuff that works well and avoid the stuff that doesn’t. So, there’s a lot of good stuff in the DevOps movement that we promote within Disciplined Agile Delivery.
I think the big thing for existing DevOps professional is to just observe that there’s a lot more to it than just buying [or] adopting one or two practices, like the cool ones like continuous delivery or continuous integration, maybe adopt a new tool. There’s a lot more to it than that. So, you really do need to look at the overall process, the overall how the culture change as it occurs, and what needs to be changed.
There was a bunch of stuff that we potentially need [. . .] within a more disciplined DevOps type of a world, and we’re just trying to make it explicit. We’re pointing out the need to work with developers and operations people that will work together all the way through delivery.
But as well, the development and delivery part of the lifecycle. But also for developers to understand that they need to instrument their tools and that these things that are occurring in operations is very, very important, and you’d better be aware of it and support it well. So, there’s some behavior improvement on both sides of the fence that can occur. So there’s a lot of good things going on right now.