The benefit is that the process is a virtuous loop. But if specialization doesn’t always lead to better quality products, then it is important to rethink how things get built. This goes against more traditional business approaches where specialization is all important. That’s what Sriram means by “Ideate-Build-Run”. Instead, with DevOps, the team who comes up with an idea for an improved software should also build the software and run the software. The designer doesn’t feel the pain of having to maintain what was designed, so designs don’t get better. The problem with this traditional approach is a lack of quality. And the person who builds the new road doesn’t fill in potholes.
The person who designs a new road doesn’t build it.
Recently, Sriram made some slides explaining why it is so important for DevOps to get a new org chart. Sriram Narayan is an IT Management Consultant at ThoughtWorks who wrote the book on Agile IT Org Design. First up, let’s tackle who is advocating this. That’s a mouthful of a sentence, so let me break it down. Time is running out to make an IT organizational structure that can meet the constant “ideate-build-run” iterations of modern development operations (DevOps).
