‹ Back To Training

Agile Project Estimation

Timeline: 2 Days

Topics

Expand All › ‹ Collapse All

  • Agile Means Discipline
  • The Agile Microscope
  • People vs Formulas
  • Top reasons Software Planning Fails
  • What makes a plan an Agile plan?
  • 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
  • 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
  • Team Metrics
  • How Many Teams?
  • How Many Product Backlogs
  • 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