Description

This curriculum spans the design and implementation of agile capacity planning systems across teams and portfolios, comparable in scope to a multi-workshop operational readiness program for enterprise agile transformation.

Module 1: Establishing Agile Capacity Baselines

Determine team capacity by calculating available person-days per sprint, accounting for holidays, meetings, and non-project commitments.
Decide whether to use ideal hours or story points when measuring team throughput, based on historical consistency and team preference.
Adjust capacity baselines for part-time contributors by prorating their availability and tracking their actual contribution over multiple sprints.
Integrate team member skill distribution into capacity models to identify bottlenecks in specialized roles such as QA or DevOps.
Document and version control capacity assumptions to maintain auditability during team restructuring or personnel changes.
Address discrepancies between planned and actual capacity by conducting retrospective root cause analysis after each sprint.

Module 2: Forecasting Workload and Demand

Aggregate backlog items by business unit or product line to project demand volume over the next quarter.
Use historical velocity data to model probabilistic delivery ranges under varying demand scenarios.
Implement a triage process for incoming requests to classify urgency and determine inclusion in near-term capacity planning cycles.
Coordinate with product management to align roadmap commitments with realistic capacity constraints.
Adjust forecast models when external dependencies, such as third-party deliveries, introduce variability in workload timing.
Track demand inflation from stakeholder pressure and implement gating mechanisms to prevent scope creep in planning cycles.

Module 3: Cross-Team Capacity Allocation

Allocate shared resources (e.g., UX designers, database administrators) across multiple teams using time-blocking or fractional commitments.
Resolve contention for shared services by establishing a capacity reservation protocol during PI or quarterly planning events.
Implement a capacity dashboard visible to all team leads to increase transparency in resource utilization.
Negotiate trade-offs between feature teams and component teams when allocating time for refactoring or technical debt reduction.
Adjust allocation percentages quarterly based on delivery performance and changing strategic priorities.
Enforce capacity caps on support and operational work to prevent erosion of project delivery time.

Module 4: Managing Velocity Variability

Analyze sprint-to-sprint velocity fluctuations to distinguish between measurement noise and actual performance shifts.
Adjust capacity forecasts when onboarding new team members by applying ramp-up curves based on role and experience level.
Factor in planned absences (e.g., training, sabbaticals) when calculating effective velocity for upcoming sprints.
Decide whether to exclude outlier sprints (e.g., those impacted by production incidents) from velocity averages.
Use rolling median velocity instead of mean to reduce sensitivity to extreme values in forecasting.
Introduce capacity buffers for high-risk initiatives where velocity predictability is historically low.

Module 5: Integrating Dependencies into Capacity Models

Map upstream and downstream dependencies to identify sprints where team capacity may be idle due to blocked work.
Reserve buffer capacity in dependent teams to absorb delays originating from external teams or vendors.
Coordinate integration testing windows across teams to avoid overlapping demands on shared environments.
Adjust sprint planning when regulatory or compliance reviews introduce fixed-date constraints.
Track dependency lead times to improve accuracy in sequencing work and allocating capacity.
Escalate unresolved cross-team blockers to portfolio management when they consistently consume contingency capacity.

Module 6: Capacity Governance and Escalation Protocols

Define thresholds for capacity overruns that trigger formal change control or scope renegotiation.
Implement a governance board to review capacity deviations exceeding 15% from forecast across programs.
Document and approve exceptions to capacity plans when emergency production work displaces planned deliverables.
Require capacity impact assessments for all change requests before they are accepted into the backlog.
Standardize capacity reporting formats across teams to enable portfolio-level aggregation and comparison.
Conduct quarterly audits of capacity utilization to detect misalignment with strategic objectives.

Module 7: Scaling Capacity Planning Across Portfolios

Aggregate team-level capacity data into program and portfolio views using normalized units (e.g., story points per quarter).
Allocate budget-based capacity across strategic themes by mapping team effort to investment categories.
Balance innovation, maintenance, and compliance workloads using a weighted allocation framework.
Implement rolling capacity roadmaps that extend 12–18 months to support long-term staffing and hiring decisions.
Use Monte Carlo simulations to model delivery outcomes under different capacity investment scenarios.
Integrate capacity planning with enterprise architecture initiatives to align technical capacity with system evolution timelines.

Module 8: Tools and Automation for Capacity Management

Select Jira configurations that support capacity tracking through custom fields and sprint reporting plugins.
Automate capacity alerts when team utilization exceeds 80% for two consecutive sprints.
Develop dashboards that overlay planned capacity with actual time tracking from integrated tools like Tempo or BigPicture.
Use API integrations to synchronize capacity data between project management tools and HR systems for headcount planning.
Implement version-controlled forecasting models in Excel or Python to ensure reproducibility and auditability.
Enforce data hygiene by requiring mandatory field entries for story estimation and sprint completion status.