PMO’s Journey with DevOps
We can probably all agree that time flies. Two years ago I wrote a post about the PMO’s future and guess what? That future is now. Two years ago I also advised choosing the right methodology like PRINCE2, Waterfall, Scrum, Lean, and Kanban, depending on the requirements of the project. Fast forward two years and we now have to add DevOps to the mix.
Now let’s say you have changed your PMO role to a more agile one. You might be thinking that this should be enough for another 10 – 20 years? Think again!
In today’s reality, organizations do not have a choice to wait or defer these disruptive innovations!
We live in a fast paced environment; change is happening much quicker compared to the past. There are new trends in the market, organizations are starting to tear down the barriers between business and IT, and projects are expected to deliver results much faster.
DASA (DevOps Agile Skills Association) labeled this as ‘Digital business transformation” or ‘digital disruption’. Here’s a helpful post about DASA’s purpose. In today’s reality, organizations do not have a choice to wait or defer these disruptive innovations!
Traditionally, IT waits for a feature request, then PMO assesses and assigns resources and processes for centralized IT operations to make it happen. As you may already have heard, DevOps is a new way of delivering IT services. It helps organizations to completely rethink – or reset – their IT operations. DevOps is a philosophy similar to Agile, not a process or methodology. It is a holistic view of how to accomplish better alignment, collaboration, and empathy between IT Development and IT Operations teams.