Do you estimate all tasks at the start of the Sprint?

Last updated by Github-actions[bot] 3 months ago.See history

In Scrum it's important to flesh out the details of a PBI when it makes sense to do so.

You should estimate your PBIs as soon as you can, but you don't need to break all of your PBIs down into fully-estimated tasks as soon as they're added to the backlog.

However, before starting work on a Sprint, you should always break the PBIs in that Sprint into estimated tasks.

Azure DevOps can use the remaining hours assigned to tasks to calculate the burndown. By breaking the PBIs down into tasks with estimates, your burndown will start looking correct right from the first day of the Sprint.

burndown bad example
Figure: Bad Example - The tasks weren't estimated at the start of the Sprint

burndown good example 1710232021934
Figure: Good Example - The tasks were estimated from day one

Note: If you're not using task estimates, you can configure Azure DevOps to create a Sprint Burndown using PBI Effort instead.

We open source. Powered by GitHub