
Authoritative.
Strategic.

Data-driven project portfolio management Project management suffered an identity crisis half a decade ago, when ever-more-empowered developers were learning to work directly with their business patrons as Agile development philosophies encouraged developers to co-ordinate their activities in tight-knit teams that regularly report, evaluate, reassess and re-plan their short-term strategies.
It’s never easy to bring two organisations together, but when they’re both huge companies with millions of customers and deeply entrenched cultures, the difficulty level goes up dramatically. Throw in the pressures of Australia’s cutthroat telecommunications industries, and it’s no surprise that Chelsea Love looks back on the consolidation of Vodafone and Three Australia with some relief.
Benefits come from change. Therefore, it makes sense that every project should be seen as a ‘change project’.
You’ll only know if you’ve been successful if you know why you’re needed.
To be effective PMOs need to have authority. No authority, no effectiveness. It’s that simple.
If the PMO handles the cross-project issues and challenges the project managers can focus on effectively running their projects.
Standards should exist solely to enable, support and help deliver successful projects. But too often they become ends in themselves.
PMO is an acronym with a range of different meetings with very different implications
The Portfolio Management Office (PMO) should streamline processes, minimize delays and deal with the critical success factors that cross project and program boundaries
Midsize organisations are uniquely positioned to take advantage of a performance management approach to business. Compared with larger companies, they have more agility to bring information and people together and ...
Developed by the CIO executive Council, Pathways is a unique, flexible, self-managed, self-paced 12-month CIO designed and delivered ...