This curriculum spans the full lifecycle of agile estimation in application management, equivalent in scope to a multi-workshop capability program that integrates team-level practices, cross-team coordination, and governance alignment across the application delivery lifecycle.
Module 1: Foundations of Estimation in Agile Application Management
- Selecting appropriate estimation units (story points vs. ideal days) based on team maturity and delivery context.
- Defining a team-specific definition of "done" to anchor estimation consistency across sprints.
- Establishing baseline reference stories to calibrate estimation across team members.
- Deciding whether to estimate bugs and technical debt with the same rigor as feature work.
- Integrating estimation practices with existing application lifecycle management (ALM) tools such as Jira or Azure DevOps.
- Managing stakeholder expectations when estimates are used for forecasting but not as fixed commitments.
Module 2: Team-Based Estimation Techniques
- Facilitating Planning Poker sessions with distributed teams using synchronized digital tools.
- Addressing anchoring bias by enforcing silent voting before group discussion.
- Handling estimation disagreements through time-boxed discussion and escalation protocols.
- Rotating facilitation roles to distribute estimation ownership and reduce facilitator dependency.
- Adjusting estimation frequency based on backlog volatility and release planning cycles.
- Documenting estimation rationale for high-impact or outlier stories to support future refinement.
Module 3: Backlog Refinement and Story Sizing
- Scheduling regular refinement sessions that balance preparation effort with delivery capacity.
- Splitting user stories to meet INVEST criteria while preserving end-user value increments.
- Managing partially refined backlog items that must be estimated under time pressure.
- Applying story mapping to align estimation with broader feature and release objectives.
- Handling cross-team dependencies during refinement in scaled agile environments.
- Tracking refinement efficiency using metrics like story aging or re-estimation frequency.
Module 4: Velocity and Forecasting Practices
- Calculating team velocity using trailing averages while excluding outlier sprints.
- Adjusting forecasts for team capacity changes due to holidays, turnover, or shifting priorities.
- Communicating forecast uncertainty using confidence intervals instead of single-point predictions.
- Updating release plans dynamically based on actual velocity rather than initial estimates.
- Managing stakeholder pressure to inflate velocity by maintaining transparent historical data.
- Using Monte Carlo simulations for probabilistic forecasting in complex application portfolios.
Module 5: Estimation in Multi-Team and Scaled Environments
- Aligning estimation scales across teams without enforcing artificial normalization.
- Coordinating estimation for shared components or platform services used by multiple teams.
- Handling estimation for cross-team epics using dependency mapping and integration sprints.
- Using proxy estimation techniques when full team participation is impractical.
- Resolving conflicts when dependent teams provide mismatched estimates for shared work.
- Integrating program increment (PI) planning outcomes with team-level estimation data.
Module 6: Governance and Stakeholder Integration
- Presenting estimation data to governance boards without misrepresenting uncertainty as precision.
- Aligning estimation cycles with budgeting and fiscal planning calendars.
- Defining escalation paths when estimates reveal delivery risks to committed timelines.
- Managing change control processes that incorporate re-estimation after scope changes.
- Using estimation trends to inform portfolio-level decisions on application modernization.
- Documenting estimation assumptions for audit and compliance purposes in regulated industries.
Module 7: Continuous Improvement and Metrics
- Measuring estimation accuracy using actuals vs. planned story completion rates.
- Conducting retrospective analysis on consistently over- or under-estimated story types.
- Adjusting estimation practices based on team composition changes or skill shifts.
- Integrating estimation feedback into Definition of Ready criteria for backlog items.
- Using control charts to monitor velocity stability and identify systemic estimation drift.
- Retiring outdated reference stories and recalibrating estimation baselines periodically.