Agile Project Estimation
Private Training

Course Summary

Estimating agile projects can seem like an overwhelming task to those new to agile. This 2-day Agile Project Estimation training course teaches students that estimating for Agile project delivery is radically different from estimating for traditional waterfall methodologies. Students learn how to decompose project scope using epics, themes, features, stories and tasks. Included in the training are strategies related to ensuring maximum business value is delivered for the Product Owner. Agile project reporting is reviewed in detail to enable students to identify concerns.

Participants are expected to understand Scrum basics prior to attending this course.
Course Length
2 Days
Prior experience with agile project execution is helpful.


Learn practices for decomposing scope to manageable pieces for teams to consume during a Sprint.

Understand the concept of relative sizing and how it’s used.

Be adept at interpreting agile reporting.

Gain an understanding of key Agile metrics.

Detailed Outline

  1. Agile Estimation
    • Agile Means Discipline
    • The Agile Microscope
    • People vs Formulas
  2. Why Plans Fail
    • Top Reasons Software Planning Fails
    • What makes a plan an Agile plan?
  3. Managing Requirements
    • Decomposing Scope
    • Developing the Release Plan
    • Leveraging Themes
    • INVEST-ing in Good Stories
    • The Hidden Waterfall
    • Metrics for Grooming and Managing the Product Backlog
    • Story Metrics and the Story Scale
    • Using Spikes & “Get Smart” Stories
  4. Relative Sizing Metrics
    • Understanding Relative Sizing & Why It Works
    • Relative Sizing Techniques
    • Story Points, Ideal Days and Other Variables
    • Sizing with Planning Poker
    • Constraints on Relative Sizing
    • Team Velocity Calculations
    • Consequences of Not Using Relative Measurement
    • Key Business Metrics
    • Business Value Metrics
    • Prioritizing / Sequencing Using Relative ROI
    • Making Corrections
    • Dealing with Inaccurate Estimates
    • Dealing with Missed Iteration Goals
    • Dealing with New / Changed Requirements
    • Tracking Historical Trends
  5. Doing Scrum in a Big Way
    • Team Metrics
    • How Many Teams?
    • How Many Product Backlogs
  6. Forecasting
    • Forecasting Without Any History
    • Forecasting Using Historical Data
    • To Buffer or Not to Buffer
    • Ensuring Quality
    • What to Measure and When
    • Refactoring Formalized and Measured
    • Measuring TDD and ATTD
    • Forecasting based on estimates
    • Forecast fine-tuning based on facts