Please enable JavaScript.
Coggle requires JavaScript to display documents.
the implementation of a Project Management Office (PMO) within the AtekPC…
the implementation of a Project Management Office (PMO) within the AtekPC organization and the challenges it faces in terms of organizational culture, governance, and decision-making.
-
Possible Solutions
Resource Allocation. The would start by gradually increasing the PMO's resources as it proves its value. Then they should think about hiring some more project managers and analysts to help with the projects.
pros
Cost Control. It will allow the organization to control costs by only adding resources as it is needed, and avoiding unnecessary overhead in the initial stages, therefore saving money
It will improve their value. As the PMO gets bigger and demonstrates its value through resources improved project outcomes, It will become easier to secure more resources and support for the higher ups.
cons
It might be slow to start. The gradual resource increase may result in slower progress in building up the PMO's capabilities and may delay their ability to address critical organizational needs.
They might miss opportunities. The delaying of the resources might result in missed opportunities to capitalize on high-potential projects.
Cultural Resistance. They can implement a change in management strategy to address cultural resistance. They should communicate the benefits of project management to employees and provide training and support for transitioning to new processes.
Relevant Facts
The issue of authority was a concern. While there was implied authority, formal authority would only be granted when the PMO had proven itself to the business and IT.
The future of the PMO at AtekPC was uncertain, and its expansion beyond IT projects depended on its success in implementing discipline and standards.
The responsibilities of the PMO at AtekPC were continuously evolving as they sought to gain support and consensus on their mission and charter.
AtekPC primarily used project-focused responsibilities to demonstrate the value of the PMO, with an initial focus on mentoring and supporting individual projects.
Implementing a PMO in a non-PM culture was challenging, as many within the organization viewed project management as administrative overhead.
Governance
Questions on how to measure themselves, how does the project organization measure success, will bureaucracy slow things down
There were no roadmaps or timelines for its maturation so there was no way to measure PMO performance other than through the subjective opinions from those involved
Proving PMO value will be challenging because there has not been any collection of data before but they have to show progress
As long as PMO remains an element a division apart within IT there will always be a division "us-them" and a feeling that we have an axe to grind or it,s to make IT look better.