--- name: it-project-portfolio-management description: Manage IT project portfolios including project selection, resource allocation, budget tracking, risk management, governance, and portfolio optimization. Use when prioritizing IT projects, allocating resources across projects, tracking portfolio health, conducting project reviews, managing IT transformation programs, or optimizing IT investment portfolio. Triggers on phrases like "IT project portfolio", "project prioritization", "resource allocation", "project governance", "IT program management", "portfolio optimization", "project pipeline", "investment portfolio", "project tracking", "PMO". --- # IT Project & Portfolio Management Strategic management of IT project portfolios for maximum business value delivery. ## Workflow 1. Establish PMO (Project Management Office) structure: roles, processes, tools, governance. 2. Build project pipeline: collect project requests from all stakeholders; standardize intake process. 3. Evaluate and prioritize projects: strategic alignment, ROI, risk, resource availability, dependencies. 4. Allocate resources: capacity planning, team assignment, budget assignment, timeline scheduling. 5. Execute projects: agile/waterfall/hybrid methodology; regular status reporting; risk management. 6. Monitor portfolio health: dashboard tracking; variance analysis; escalation of issues. 7. Conduct governance reviews: monthly steering committee; quarterly executive review. 8. Close projects: benefits realization review; lessons learned; team release; asset handoff. 9. Optimize portfolio: reprioritize based on changing business needs; kill underperforming projects. 10. Report outcomes: annual portfolio review; ROI analysis; strategic alignment assessment. ## Portfolio Governance ``` PMO STRUCTURE AND GOVERNANCE ============================== PMO Types: Supportive PMO (Light Touch): - Provides templates, best practices, training - Advisory role; project managers retain autonomy - Suitable for: mature PM teams; decentralized organizations - Staff: 1–3 PMO analysts Controlling PMO (Moderate Oversight): - Requires compliance with standards and methodologies - Project approval and milestone sign-off required - Resource allocation and dependency management - Suitable for: growing organizations; need for consistency - Staff: 3–8 PMO professionals Directive PMO (Full Control): - PMO directly manages all IT projects - Project managers report to PMO director - Full control of resources, budgets, priorities - Suitable for: large enterprises; transformation programs - Staff: 8–20+ PMO professionals Governance structure: IT Project Portfolio Committee (ITPPC): Members: CIO, VP Engineering, IT PMO Director, Finance representative Frequency: Monthly Authority: Approve/reject projects > $50K; reprioritize portfolio Decisions: resource allocation, project initiation, project closure Steering Committee (Executive): Members: CIO, CFO, COO, Business Unit VPs Frequency: Quarterly Authority: Approve projects > $250K; strategic direction; budget approval Decisions: major investments, strategic shifts, portfolio rebalancing Project Board (per large project): Members: Sponsor, Project Manager, Technical Lead, Business Analyst Frequency: Bi-weekly Authority: Project-level decisions; scope changes; risk response Decisions: sprint planning, scope changes, issue resolution Project lifecycle stages: Stage 1 — Idea / Discovery: - Business case drafted (1–2 pages) - Initial cost estimate (± 50%) - Strategic alignment assessment - Go/No-Go decision by ITPPC - Gate criteria: strategic alignment, rough ROI estimate Stage 2 — Initiation: - Detailed business case (10–15 pages) - Cost estimate refined (± 25%) - Resource plan drafted - Risk assessment completed - Go/No-Go decision by Steering Committee (if > $250K) - Gate criteria: detailed business case, stakeholder alignment Stage 3 — Planning: - Project plan created (scope, schedule, budget, resources) - Detailed design completed - Vendor selection (if applicable) - Risk response plans documented - Go/No-Go decision by ITPPC - Gate criteria: complete project plan, baseline approved Stage 4 — Execution: - Development/implementation - Regular status reporting - Change control process - Quality assurance/testing - Milestone reviews - Gate criteria: on-track status, quality standards met Stage 5 — Closure: - Deliverables accepted by sponsor - Benefits realization plan created - Lessons learned documented - Team released or reassigned - Project archived - Gate criteria: sponsor sign-off, benefits plan approved Stage-Gate decision outcomes: GO: proceed to next stage HOLD: pause for additional information; revisit in 30–60 days REWORK: return to previous stage for corrections KILL: terminate project; document rationale; release resources ``` ## Project Prioritization ``` PROJECT PRIORITIZATION FRAMEWORK ================================== Weighted scoring model: Criteria Weight Score (1–10) Weighted ──────────────────────────────── ──────── ───────────── ───────── Strategic alignment 25% [score] [score × 0.25] Financial ROI (NPV/IRR) 20% [score] [score × 0.20] Regulatory/compliance need 15% [score] [score × 0.15] Customer impact 15% [score] [score × 0.15] Risk level (inverse) 10% [score] [score × 0.10] Resource availability 10% [score] [score × 0.10] Dependency on other projects 5% [score] [score × 0.05] ──────────────────────────────── ────────────────────────────────────── TOTAL SCORE [sum] Scoring guide: Strategic alignment: 10 = Directly enables top strategic priority (CEO/CFO endorsed) 7–9 = Supports key business objective 4–6 = Supports departmental goal 1–3 = Nice to have; no clear strategic link Financial ROI: 10 = IRR > 50%; payback < 6 months 7–9 = IRR 25–50%; payback 6–12 months 4–6 = IRR 10–25%; payback 12–24 months 1–3 = IRR < 10%; payback > 24 months; or cost center (no direct revenue) Regulatory/compliance need: 10 = Legal requirement; failure = fines or business shutdown 7–9 = Audit finding; must fix within 90 days 4–6 = Best practice; improves compliance posture 1–3 = No compliance impact Customer impact: 10 = Directly impacts all customers; revenue-generating feature 7–9 = Impacts > 50% of customers; significant UX improvement 4–6 = Impacts specific segment; moderate improvement 1–3 = Internal tool; minimal customer impact Risk-adjusted prioritization: Risk categories and scoring: Technical risk: Can we build it? (1=low risk, 10=high risk) Schedule risk: Can we deliver on time? (1=low risk, 10=high risk) Resource risk: Do we have the people? (1=low risk, 10=high risk) Financial risk: Will costs stay in budget? (1=low risk, 10=high risk) Market risk: Will it still be valuable when delivered? (1=low risk, 10=high risk) Risk-adjusted score = Priority Score × (1 − Average Risk Score / 10) Portfolio balancing: Project types for balanced portfolio: Run projects (40–50%): maintain, upgrade, patch, compliance Grow projects (30–40%): support business growth, new features, efficiency Transform projects (15–25%): innovation, digital transformation, new capabilities Resource allocation targets: Engineering resources: 50% run, 30% grow, 20% transform Budget allocation: 60% run, 25% grow, 15% transform Headcount planning: 1 new engineer for every 2 retiring/innovating projects Fast-track projects (bypass normal prioritization): Security vulnerabilities (CVSS 9.0+): immediate resource allocation Regulatory deadlines (fixed date): priority scheduling Revenue-generating hot leads: dedicated sprint capacity Executive mandate (CTO/CFO directive): resource reservation Limit: fast-track projects should be < 10% of portfolio ``` ## Resource Management ``` RESOURCE CAPACITY PLANNING ============================ Resource inventory: Engineering teams: Backend engineers: [X] FTE × [Y] hours/week available = [Z] hours/month Frontend engineers: [X] FTE DevOps/SRE engineers: [X] FTE Data engineers: [X] FTE QA/Test engineers: [X] FTE Security engineers: [X] FTE Architects: [X] FTE Support teams: System administrators: [X] FTE Network engineers: [X] FTE Database administrators: [X] FTE Help desk: [X] FTE External resources: Contractors: [X] FTE equivalent Consulting firms: [X] project-based engagements Managed service providers: [X] retainer contracts Capacity calculation: Available hours per FTE per month: Total working hours: 160 hours/month (40 hrs × 4 weeks) Less meetings: -24 hours (-15%) Less email/admin: -16 hours (-10%) Less training: -8 hours (-5%) Less PTO/vacation: -20 hours (-12.5%, annualized) Less sick time: -4 hours (-2.5%) ───────────────────────────────────── Available for projects: ~78 hours/month per FTE (49% utilization for projects) Capacity allocation: Project Q1 Hours Q2 Hours Q3 Hours Q4 Hours Total Hours ────────── ────────── ────────── ────────── ────────── ─────────── Project A 400 300 200 100 1,000 Project B 200 400 400 400 1,600 Project C 0 200 600 800 1,600 Project D 300 300 300 300 1,200 Run work 800 800 800 800 3,200 ───────────────────────────────────────────────────────────────────────── Total 1,700 2,000 2,300 2,400 8,400 Available 2,000 2,000 2,000 2,000 8,000 Utilization 85% 100% 115% ⚠️ 120% ⚠️ Alert: Q3 and Q4 overallocated — need to: 1. Shift Project C work to Q1/Q2 2. Add contractor resources (2 FTE in Q3/Q4) 3. Deprioritize Project D (reduce to 200 hours/quarter) Resource leveling: - Identify overallocated resources - Shift non-critical tasks to lighter periods - Add external resources (contractors, consultants) - Deprioritize or defer projects - Extend timelines where dependencies allow ``` ## Project Tracking and Reporting ``` PROJECT TRACKING DASHBOARD ============================ Portfolio summary: Total projects: [X] active, [Y] in pipeline, [Z] on hold Total portfolio budget: $[X]M allocated, $[Y]M spent, $[Z]M remaining On-budget projects: [X]% (target: > 80%) On-schedule projects: [X]% (target: > 80%) Green/Amber/Red projects: [X]🟢 / [Y]🟡 / [Z]🔴 Resources at capacity: [X]% (target: 80–95%) Project status detail: Project Budget Spent % Used Schedule Status Risk Next Milestone ────────────── ──────── ────── ────── ───────── ─────── ───── ──────────────── Cloud Migration $500,000 $225,000 45% On track 🟢 Green Low Phase 2 go-live ERP Upgrade $1,200,000 $900,000 75% 2 wks late 🟡 Amber Med UAT completion Security M365 $300,000 $120,000 40% On track 🟢 Green Low Pilot launch Data Warehouse $800,000 $650,000 81% 4 wks late 🔴 Red High Architecture review Mobile App $400,000 $180,000 45% On track 🟢 Green Med Beta release CRM Integration $250,000 $60,000 24% On track 🟢 Green Low Vendor selection ───────────────────────────────────────────────────────────────────────────────────────── Project health scoring: Score Status Definition ──────── ──────── ─────────────────────────────────────── 8–10 🟢 Green On budget, on schedule, risks managed 6–7 🟡 Amber Minor issues; recovery plan in place 4–5 🟠 Orange Significant issues; executive attention needed 2–3 🔴 Red Critical issues; project at risk of failure 1 ⚫ Black Project failure; recommend kill or major reset Health score calculation: Schedule variance: on time (10), < 10% late (7), 10–20% late (4), > 20% late (1) Budget variance: on budget (10), < 10% over (7), 10–20% over (4), > 20% over (1) Scope: no creep (10), minor (7), significant (4), major (1) Quality: meets standards (10), minor issues (7), defects (4), fails testing (1) Stakeholder: satisfied (10), concerns (7), dissatisfaction (4), active resistance (1) Risk: well managed (10), controlled (7), elevated (4), uncontrolled (1) ───────────────────────────────────────────────────────────────── Average score → project status Monthly project report template: 1. Executive Summary (1 paragraph) 2. Status: [Green/Amber/Red] with brief reason 3. Key accomplishments this month (3–5 bullets) 4. Key challenges/risks this month (3–5 bullets) 5. Budget: planned vs. actual (variance %) 6. Schedule: planned milestones vs. actual (variance weeks) 7. Resource utilization: planned vs. actual hours 8. Next month priorities (3–5 bullets) 9. Decisions needed from sponsor/steering committee 10. Updated risk register (top 5 risks) ``` ## Integration Points - **Jira / Jira Align**: Agile project management; sprint planning; backlog management; portfolio views; reporting - **Microsoft Project / Project Online**: Gantt charts; resource management; critical path; enterprise project management - **Smartsheet**: Spreadsheet-based project management; Gantt views; resource management; reporting - **Asana / Monday.com**: Lightweight project management; task tracking; team collaboration; templates - **Planview / Clarizen**: Enterprise project portfolio management; resource management; financial integration - **ServiceNow PPM**: IT project management integrated with ITSM; change management alignment; asset tracking - **Azure DevOps**: Development-focused project management; backlog, sprints, boards; CI/CD integration - **Confluence / SharePoint**: Project documentation; knowledge base; meeting notes; decision logs - **Power BI / Tableau**: Portfolio dashboards; resource utilization analytics; trend analysis; executive reporting ## Edge Cases - **Megaproject management** (>$5M, >12 months, >50 people): Break into phases with individual gates; establish dedicated PMO for the program; weekly executive steering; monthly benefit tracking; stage-gate funding (release funds per phase completion); dedicated risk manager; communication plan for 100+ stakeholders - Example: ERP implementation ($5M, 18 months, 75 people) - Phases: Discovery (3 months), Design (3 months), Build (6 months), Test (3 months), Go-Live (3 months) - Governance: weekly PMO review, bi-weekly steering committee, monthly executive brief - Risk buffer: 20% schedule contingency, 15% budget contingency - **Agile portfolio management** (managing multiple agile teams): Portfolio Kanban board; capacity planning per sprint; dependency management across teams; release train (SAF/LeSS for scaled agile); quarterly business reviews; product roadmap alignment - Scrum of Scrums: daily 15-minute sync across team leads - Program Increment (PI) planning: quarterly 2-week planning event (all teams) - Portfolio metrics: flow rate, cycle time, cumulative flow diagram, team velocity trends - Limit WIP: max 3 active initiatives per team to prevent context switching - **Project cancellation** (killing a project gracefully): Common causes: strategy shift, budget cut, technology change, scope creep, poor ROI; process: formal review by steering committee; document rationale; communicate to stakeholders; release resources with recognition; archive documentation; conduct lessons learned; celebrate effort (even failed projects learn) - Communication: "Project X is being paused due to [reason]; team will be reassigned to [projects]; lessons learned will be documented" - Financial: recalculate budget; reclaim uncommitted funds; close POs; settle vendor contracts - Emotional: recognize team effort; provide transition support; maintain morale - **Cross-functional project dependencies** (IT project depends on business process change): Align IT and business timelines; joint governance (business sponsor + IT sponsor); integrated status reporting; shared risk register; combined change management plan; UAT with business stakeholders - Common failure: IT delivers on time but business not ready to adopt - Mitigation: business readiness milestone before IT go-live; change management starts in planning phase - Communication: weekly sync between IT PM and business change manager - **Vendor-managed projects** (outsourced implementation): Clear scope of work with deliverables; milestone-based payments (not time-and-materials); vendor PM integrated with internal PMO; quality gates at each milestone; retention amount (10–20%) until acceptance; penalty clauses for delays; knowledge transfer requirement - Contract structure: 30% upfront, 40% at midpoint milestone, 20% at UAT, 10% at go-live + 30 days - Governance: weekly status calls; monthly steering committee; issue escalation path - Risk: vendor under-resources project; mitigation: right to audit resource allocation; performance bonds - **Innovation and R&D projects** (uncertain scope, unknown timeline): Stage-gate with option to kill early; lightweight documentation; time-boxed experiments (4–8 week sprints); success criteria defined as learning outcomes (not delivery); budget for failure (allocate 15–25% of innovation budget to failed experiments) - Investment model: 70-20-10 rule — 70% core projects, 20% adjacent projects, 10% transformational/innovative - Evaluation: OKR-based rather than traditional project metrics; speed of learning over delivery timeline - Team structure: dedicated innovation team (not pulled from core projects); T-shaped skills encouraged