PMOs are a relatively modern phenomenon. The earliest known maps include cave drawings from around 16,500BC and even older maps inscribed on mammoth tusks. That's a lot of Lessons Learned that PMOs can draw knowledge from! In this article we explore what PMO people and Cartographers have in common, and what we can learn from the pioneers of map making.

Thanks to the growing number of CRM systems with API interfaces, and messaging systems such as Slack that positively embrace the use of bots, more and more simple tasks can be automated. PMOs should be taking advantage.

How many times have you bemoaned the erratic, irrational and illogical decisions that have been made, causing projects to deliver late, dependencies to be missed and seemingly disparate projects to clash? Cogitative Biases effect projects deliver and PMO success. But they can be mitigated and controlled. Here are six to watch out for. 

Marketing and Agile are a match made in heaven. And PMOs have an important role to play in helping Marketing teams take the Agile plunge.

The US Senate has unanimously approved the Program Management Improvement and Accountability Act.  PMI are pretty excited about the bill - they have been vocal about their endorsement of the bill. But what does it mean for Project Management professionals?

An interesting example of Agile in the construction industry that almost lead to London, UK having a tower to rival the Eiffel Tower in Paris.

The problem with lessons learned reports is that they are usually sterilized to the point of being meaningless.

Call3 is a new way of sharing lessons with a simple premise: When project managers initiate new projects, they must call three nominated people and have a 30 minute conversation with them about the project. 

We are in an age where we can (and do) gather increasing amounts or data about our organizations, projects, suppliers, markets and people. These sources could be used to make better data-driven decisions about how we deliver projects and seek to extract value from them. But despite the obvious potential, few PMOs have made progress with tapping into this pool of data.

When delivering within fixed iterations to high standards of quality, the only thing you can flex is the scope. Combining the simplicity or MoSCoW with the customer-centric view that Kano provides, gives us a powerful lexicon with which to explore the mix of requirements we are delivering and make effective decisions.