Please enable JavaScript.
Coggle requires JavaScript to display documents.
AtekPC PMO Dilemma - Coggle Diagram
AtekPC PMO Dilemma
Timeline
- CIO John Strider creates the PMO, lead by Mark Nelson
- PMO faces questions of heavy or light control, with no agreement of process.
- Lead Analysts came to be informal managers with many duties
- Mark realizes the PMO lacks defined authority and success indicators. Is uncertain of implementation.
- AtekPC Originally developed an informal development process
- Mark and IT leaders decide that with their resources, a phased PMO is best. Showing small progress first.
- Planning office implemented. PMO could possibly fail, as issues pile up and Strider reflects on the decision.
Relevant Facts
-
AtekPC historically uses informal, fast response IT project methods
Cross-functional, complex projects are increasing
-
PMO has unclear authority, limited resources, & cultural resistance
-
Solutions
Make a clear PMO mission & role so everyone is properly informed on what the PMO is supposed to do inside AtekPC.
Pros: Gives all teams a shared understanding of how to use the PMO & reduces confusion & mixed expectations.
Cons: Some managers may resist clearer rules or added structure. It may slow down work temporarily during setup.
Is this feasible: Yes. Leadership already knows the PMO's purpose is unclear and is open to more structure.
Evidence: "There was not a complete consensus regarding its purpose, its responsibilities, and its authority."
-
Change existing lead analysts to designated managers that can communicate with either a light or heavy PMO - they already have experience in this role and are specialized for their groups. Utilizing them reduces necessary investment.
Is this feasible: Yes, since lead analysts are already in a good position to fill this role
Pros: Saves resources by not needing new staff. Leverages the clout and PM experience lead analysts already have. Will work with light or heavy PMO
-
-
Evidence: "As a Lead Analyst, [Star] had dealt with many of the problems of project management, and she was keenly aware of the opportunity that the PMO created for her"