The PMO Integration Problem (Part 1)
It’s been a long time since the events that I am about to recount to you, and it’s taken me all of that time to recover from the emotional scars enough to recount the story here. It was my first ever project as a consultant--I was working for a small firm and was asked to go to a major company to help them integrate their IT PMOs. These PMOs had previously been structured as standalone functions within the IT teams of each of the company’s divisions--and with the decision to centralize IT, all of those different PMOs now needed to come together to form one cohesive unit in a merger of 16 different groups.
Of course, at the same time, the assessment and management of all of the company’s projects had to continue without a loss of performance, and the expected cost savings had to be realized as quickly as possible.
With hindsight, I should have run. But I didn’t, and hopefully now I can look back and find a few lessons in the mess. In this two-part article, I want to help guide you through my experience: what I did, what I took from it and how I would do things differently if given the opportunity to repeat the project.
In the Beginning: The Cat Herding Begins
The first thing that I realized when I walked in the door was that I was not dealing with a newly created PMO, I was dealing with 16 distinct PMOs that just so happened to now
Please log in or sign up below to read the rest of the article.