Budgeting, Estimation, Planning, #NoEstimates and the Agile Planning Onion

Observed from the outside, the idea of estimation might seem like a foreign concept when applied to Agile testing. However, agile practitioners implement many levels of estimation, including budgeting, high-level estimation and task planning (detailed estimation). We can link a more classic view of estimation to the Agile planning onion popularized by Mike Cohn. In the Agile planning onion, strategic planning is on the outside of the onion and the planning that occurs in the daily sprint meetings is at the core of the onion. Each layer closer to the core relates more to the day-to-day activity of a team. The #NoEstimates movement eschews developing story- or task-level estimates and sometimes higher levels of estimation. As you get closer to the core of the planning onion the case for #NoEstimates becomes more compelling and, dare I say, useful. A case study will be used to focus on how an organization that tests both within the Agile teams and through an independent testing group has implemented estimates for Agile testing activities.

Learning Objectives:

  • The difference between budgeting, planning and estimation as applied to testing in an Agile environment and when they make sense, when they don’t, and in what combination for testing
  • What does #NoEstimates really mean (and why the hype?) and how these concepts can be applied to Agile testing
  • Why not having a strategy for budgeting, planning and estimation is a losing game

AGILE
Location: Date: April 20, 2016 Time: 11:15 am - 12:15 pm hs__Thomas_Cagley Tom Cagley