A few recent events have left this project manager feeling very positive about PMOs--and that’s something that hasn’t happened in quite some time. While we can't yet proclaim PMOs as saviors of organizations, they are now on the journey to success.
The average lifespan of a PMO from inception to demise is approximately two years. That raises numerous questions regarding the purpose and relevance of PMOs. Those questions, however, can probably summed up with one general one: Have we reached peak PMO?
Repurposing the PMO in an agile environment from being a reporting PMO to a fully trained analytical PMO is something that is urgently needed. CFOs cannot continue to accept the information that they’ve been getting from IT at face value.
For agile teams, a traditional PMO can seem to Present Many Obstacles--but it does not need to be that way. With some alignment and time invested, they can be useful advocates.
Establishing strategies with a sponsored project management office dedicated to overseeing their implementation within an organization can generate a stronger, more refined and professional business environment that is reliable and dependable--and thus more attractive to customers.
Artificial intelligence (AI) has arrived in the business world. It's already making an impact in sales and marketing technology. How will it transform your project work?
PMOs can exist at any level of the organization, and there are compelling advantages to having an enterprise-wide PMO. Here’s proof on why it’s vital to the project environments of 2017 and beyond...
While many projects may not have to adopt the elements of the Federal Incident Command System, some are set up to resolve a certain time-bound resolution of organizational priorities and can reap the benefits.
CMOs, PIOs and PMOs, oh my! Does an organization really need all three of these offices, or would a better approach be to merge them? Enter the Alignment Management Office!
There are a lot of different PMO models in place, but is there a consensus view on how many PMOs an organization should have…or at least how multiple PMOs should be structured?