Skip to main content
Relative Sizing in Agile Project Management

Relative Sizing in Agile Project Management

$198.00
Toolkit Included:
Includes a practical, ready-to-use toolkit containing implementation templates, worksheets, checklists, and decision-support materials used to accelerate real-world application and reduce setup time.
Your guarantee:
30-day money-back guarantee — no questions asked
How you learn:
Self-paced • Lifetime updates
Who trusts this:
Trusted by professionals in 160+ countries
When you get access:
Course access is prepared after purchase and delivered via email
Adding to cart… The item has been added

This curriculum spans the breadth of relative sizing practices found in multi-team Agile transformations, addressing the same estimation challenges seen in ongoing internal capability programs and cross-team advisory engagements.

Module 1: Foundations of Relative Sizing in Agile Environments

  • Selecting appropriate units for relative sizing (e.g., story points vs. t-shirt sizes) based on team maturity and project scope.
  • Defining a baseline user story to anchor future comparisons during estimation sessions.
  • Establishing team-wide calibration to ensure consistent interpretation of size across different backlog items.
  • Deciding whether to include non-functional requirements in sizing or treat them as separate tracking concerns.
  • Integrating historical velocity data into initial sizing to improve forecast reliability.
  • Addressing stakeholder expectations when relative sizing yields non-linear time predictions.

Module 2: Team Dynamics and Estimation Practices

  • Facilitating planning poker sessions with distributed teams while minimizing bias and anchoring effects.
  • Managing dominant voices during estimation to ensure equitable participation and diverse input.
  • Handling re-estimation when team composition changes significantly (e.g., new members, role shifts).
  • Documenting rationale for high-variance estimates to support future retrospectives and audits.
  • Deciding when to use silent estimation techniques versus open discussion to improve accuracy.
  • Establishing norms for when to stop debating and commit to a consensus size.

Module 3: Backlog Refinement and Sizing Workflows

  • Scheduling refinement cadences that balance preparation needs with delivery sprint capacity.
  • Setting thresholds for story size to trigger splitting (e.g., stories exceeding 8 points).
  • Assigning ownership for leading refinement on specific backlog areas without creating silos.
  • Integrating dependency mapping into sizing to reflect cross-team coordination effort.
  • Managing partially refined items in sprint planning when full sizing was not completed.
  • Using spike stories to reduce uncertainty before final sizing of complex features.

Module 4: Scaling Relative Sizing Across Teams

  • Aligning sizing benchmarks across multiple teams working on the same product portfolio.
  • Choosing between team-specific velocity normalization and cross-team calibration sessions.
  • Handling discrepancies in sizing rigor between co-located and offshore teams.
  • Implementing lightweight coordination rituals (e.g., Scrum of Scrums) to synchronize sizing assumptions.
  • Managing executive pressure to compare team velocities directly despite differing sizing baselines.
  • Using feature-level sizing to enable portfolio-level forecasting without mandating uniform story points.

Module 5: Integration with Planning and Forecasting

  • Translating team velocity into release forecasts while accounting for scope volatility.
  • Adjusting forecasts when new teams join a program mid-cycle with uncalibrated sizing practices.
  • Factoring in non-development work (e.g., production support, compliance) that affects available capacity.
  • Deciding whether to re-estimate backlog items when velocity trends shift significantly.
  • Presenting probabilistic delivery ranges to stakeholders instead of fixed-date commitments.
  • Updating forecasts dynamically after sprint reviews reveal estimation inaccuracies.

Module 6: Governance and Audit Considerations

  • Designing audit trails for sizing decisions to support compliance in regulated industries.
  • Responding to internal audit requests for estimation methodology documentation.
  • Defining thresholds for when estimation variance triggers a formal process review.
  • Archiving sizing data for historical analysis while adhering to data retention policies.
  • Reconciling agile sizing practices with traditional project management reporting requirements.
  • Handling external consultants’ access to backlog and sizing data under confidentiality agreements.

Module 7: Continuous Improvement and Adaptation

  • Using retrospective insights to refine sizing criteria after repeated over- or under-estimation.
  • Introducing sizing heuristics (e.g., complexity, effort, risk) based on domain-specific patterns.
  • Measuring the impact of estimation training on team consistency and forecast accuracy.
  • Adjusting sizing models when transitioning between project phases (e.g., exploration to stabilization).
  • Deciding when to abandon relative sizing in favor of time-based estimation for specific work types.
  • Validating the usefulness of sizing data through correlation with actual cycle time metrics.
!