The Agile Project Estimation training course will teach you how estimating for Agile project delivery is radically different from estimating for traditional waterfall methodologies.
You will learn how to decompose project scope using epics, themes, features, stories and tasks. We also discuss strategies to ensure maximum business value is delivered to the Product Owner. We review Agile project reporting in detail, enabling you to identify concerns.
An understanding of Scrum basics is assumed; prior experience with Agile project execution is helpful.
- Understand practices for decomposing scope into manageable pieces for teams to consume during a Sprint
- Understand the concept of relative sizing and how it is used
- Grasp the process for developing estimates for a project
- Be adept at interpreting agile reporting
- Gain an understanding of key Agile metrics
What You'll Learn
In the Agile Project Estimation training course, you’ll learn:
- Agile Estimation
- Agile Means Discipline
- The Agile Microscope
- People vs Formulas
- Why Plans Fail
- Top reasons Software Planning Fails
- What makes a plan an Agile plan?
- 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
- 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
- Doing Scrum In A Big Way
- 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
Meet Your Instructor
Julian first touched fingers to keypunch in 1972, punching Fortran code onto cards at Imperial College in London (England, that is) and soon moved onto Macro-11 programming on PDP-11s. This qualifies him as a Real Programmer, and until recently, he even had a PDP-11 in his garage at home to remind him of better times.
He learnt Fortran while becoming a geologist at Imperial College, but he has never practised in the rock business, as he succumbed to the...