Description

The curriculum spans the end-to-end project portfolio management lifecycle in application development, reflecting the integrated workflows of enterprise PPM offices that coordinate strategic planning, resource governance, financial controls, and delivery execution across hybrid (Agile and waterfall) environments.

Module 1: Strategic Alignment and Portfolio Prioritization

Establish criteria for evaluating project proposals based on business value, risk, and strategic fit during annual planning cycles.
Facilitate cross-functional steering committee meetings to resolve conflicting priorities between business units and IT.
Implement scoring models that weigh technical debt reduction against new feature development in roadmap decisions.
Adjust portfolio mix in response to regulatory changes, such as compliance mandates requiring system updates.
Balance investment across run-the-business (RTB) and change-the-business (CTB) initiatives under fixed budget constraints.
Integrate customer feedback loops into prioritization to reflect market-driven requirements in backlog sequencing.

Module 2: Demand Management and Intake Workflow Design

Design a standardized intake form that captures scope, expected outcomes, and resource estimates for new requests.
Define escalation paths for urgent requests that bypass standard review without undermining governance.
Implement a triage process to classify incoming demands as projects, enhancements, or operational tasks.
Enforce mandatory business case documentation for requests exceeding predefined effort thresholds.
Integrate demand intake with existing service management tools (e.g., ServiceNow) to maintain audit trails.
Monitor cycle time from request submission to approval to identify bottlenecks in the workflow.

Module 3: Resource Capacity Planning and Allocation

Map team capacity by role (developer, QA, analyst) and account for planned leave and non-project work.
Reconcile allocated hours against actual utilization to detect overcommitment or underutilization.
Negotiate shared resource assignments between multiple projects with competing deadlines.
Adjust allocations mid-cycle due to unexpected production incidents consuming development bandwidth.
Use historical velocity data from Agile teams to inform realistic capacity forecasts.
Implement a resource leveling strategy to prevent burnout during peak delivery periods.

Module 4: Project Governance and Stage-Gate Reviews

Define exit criteria for each phase gate, including approved architecture, test coverage, and stakeholder sign-off.
Conduct gate reviews with predefined attendees, ensuring business and technical leadership are represented.
Document and track unresolved risks and dependencies before approving progression to next stage.
Decide whether to continue, rework, or terminate a project based on cost-benefit reassessment at major gates.
Enforce mandatory security and compliance checkpoints in the gate process for regulated applications.
Adjust gate frequency and rigor based on project size, risk profile, and funding source.

Module 5: Financial Oversight and Cost Tracking

Set up cost coding structures that align with general ledger accounts for accurate chargeback reporting.
Monitor actual spend against budget monthly, flagging variances exceeding 10% for investigation.
Allocate shared infrastructure and platform costs across applications using usage-based or headcount-based models.
Track time against financial work breakdown structures (WBS) to support external audit requirements.
Reforecast project costs mid-cycle due to scope changes or extended testing phases.
Report ROI post-implementation by comparing actual benefits to baseline assumptions in the business case.

Module 6: Risk and Dependency Management

Maintain a centralized risk register with ownership, mitigation plans, and escalation triggers for each project.
Map cross-project dependencies and coordinate delivery timelines to avoid blocking critical path activities.
Assess third-party vendor delivery risks and include contractual milestones in the project schedule.
Identify integration points with legacy systems and plan for interface testing well in advance.
Conduct risk review sessions quarterly with project managers to update likelihood and impact ratings.
Implement fallback plans for high-impact risks, such as data migration failures or key personnel attrition.

Module 7: Performance Measurement and Portfolio Reporting

Define KPIs such as on-time delivery rate, budget adherence, and defect escape rate for portfolio health.
Generate monthly dashboards that show project status, resource loading, and financial burn by program.
Use earned value management (EVM) to assess schedule and cost performance for large waterfall projects.
Compare actual release dates against forecasted timelines to improve future estimation accuracy.
Report on application portfolio health, including technical debt levels and support cost trends.
Adjust reporting frequency and detail based on audience—executive summaries vs. operational drill-downs.

Module 8: Integration with Development Lifecycle and DevOps

Align PPM milestones with Agile release trains or CI/CD pipeline stages for continuous delivery projects.
Synchronize portfolio planning with product backlog refinement in SAFe or Scrum-of-Scrums events.
Ensure PPM tools exchange status and effort data with Jira, Azure DevOps, or similar development platforms.
Define how technical spikes and innovation sprints are funded and tracked within the portfolio.
Include automated deployment frequency and lead time metrics in project success criteria.
Coordinate PPM change control with DevOps change advisory boards (CAB) for production deployments.