Please enable JavaScript.

Coggle requires JavaScript to display documents.

AtekPC Project Management Office (PMO), Timeline - Coggle Diagram

- - - - Budget + staffing limits
    - - Competing operational needs
    - - Understaffed, slow PMO
    - - Analysts overstretched
    - - Slower transformation
    - - CIO + Functional Managers
  - - - No measurable goals
    - - Quick creation, no alignment
    - - Confusion, slow adoption
    - - Fragmented practices
    - - Limited enterprise value
    - - CIO, IT leadership (Steinberg), and PMO manager (Nelson)
  - - - Informal history of “order-taker” IT
    - - Lack of training & failed past attempts
    - - Perception of PM as “bureaucracy”
    - - Poor adoption of tools/methods
    - - Hard to prioritize projects
    - - IT & functional leaders
  - - - PMO too new, no system in place
    - - Focus on mentoring, not measurement
    - - Hard to prove ROI
    - - Projects tracked inconsistently
    - - Executives lack performance data
    - - PMO leadership + CIO
- - - - Removes confusion about authority.
      - Sets expectations for employees and management.
      - Easier to measure PMO success.
    - - May cause conflict if role limits flexibility.
        Too much control could create resistance from project managers.
  - - - Provides legitimacy and authority for PMO decisions.
      - Easier to get resources (budget, staff, tools).
      - Strong leadership signals seriousness of the initiative.
    - - Risk of failure if sponsor leaves or changes priorities.
        Could be seen as “top-down enforcement,” increasing resistance.
  - - - Builds skills and confidence in using new processes.
      - Reduces resistance through awareness and communication.
      - Creates a culture more supportive of structured project management.
    - - Requires time and money investment.
        Risk that employees still resist despite training.
  - - - Creates consistency across all projects.
      - Easier onboarding for new employees since processes are uniform.
      - Reduces duplication of effort and confusion.
      - Improves reporting and data comparison across projects.
    - - May reduce flexibility for unique project needs.
      - Requires initial investment in selecting, implementing, and training on tools.
      - Risk of over-standardization, which could slow innovation.
  - - - Demonstrates ROI of the PMO to executives and stakeholders.
      - Builds credibility and trust in the PMO.
      - Identifies areas for continuous improvement.
    - - Can be challenging to define meaningful metrics.
      - Risk of focusing too much on metrics instead of actual outcomes.
      - Requires effort to collect, analyze, and communicate results regularly.
- - - - Initial Phase: Lack of clarity on the PMO’s role
        
        Implementation: Resource limitations, resistance from staff, and cultural pushback slowed adoption.
        
        Early 2007 – PMO introduces standard tools (e.g., “Idea Form” for project requests) and mentoring. Early successes in manufacturing and notebook launch projects.
        
        Current State (Case time): PMO is partially implemented with unclear authority and inconsistent project management standards.