Estimating Agile projects can seem like an overwhelming task for those new to the process, but it doesn’t need to be. nTier’s Agile Project Estimation course teaches participants the difference between estimating for Agile project delivery and traditional waterfall methodologies. This includes learning how to decompose the project scope using epics, themes, features, stories and tasks. Strategies to ensure maximum business value is delivered for the product owner are also included. Agile project reporting is also reviewed in detail, enabling participants to identify concerns.

Course Duration: 2 days
Prerequisites:

All participants are expected to understand Scrum basics prior to attending this course. Prior experience in Agile project execution is also helpful

Course Objectives:
  • 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
  • Grasp the process for developing estimates for a project
  • Be adept at interpreting Agile reporting
  • Gain an understanding of key Agile metrics
Course Outline:
  • Agile Estimation
    • Agile Means Discipline
    • The Agile Microscope
    • People versus Formulas
  • Why Plans Fail
    • Top Reasons Software Planning Fails
    • What Makes a Plan Agile?
  • Managing Requirements
    • Decomposing Scope
    • Developing the Release Plan
      • Leveraging Themes
    • INVEST-ing in Good Stories
    • The Hidden Waterfall
    • Metrics for Managing the Product Backlog
    • Story Metrics and the Story Scale
    • Using Spikes and “Get Smart” Stories
  • Relative Sizing Metrics
    • Understanding Relative Sizing and Why It Works
    • Relative Sizing Techniques
      • Story Points, Ideal Days and More
      • 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 or Changed Requirements
      • Tracking Historical Trends
  • Doing Scrum in a Big Way
    • Team Metrics
    • How Many Teams?
    • How Many Product Backlogs?
  • 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 with Estimates
    • Forecast Fine-Tuning Based on Facts