Project

General

Profile

Defect #1225

Sprint burndown chart calculated incorrectly

Added by Bartosz Firyn over 7 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Category:
Sprint burndown
Target version:
-
Source:
Development
Detected on version:
Scrum v0.14.0
Blocked:
No
Alone:
No
Milestones:
Sprint:

Description

Hi,

After doing several sprints I see that burndown chart is calculated incorrectly for the very first day.

The problem:

Every first day of every sprint has Pending Effort value calculated incorrectly on a Burndown Chart. First day value is way too low, it should never be lower when compared to the next day.

Our setup:

  • Our effort per sprint = 200h
  • Working days = Mon, Tue, Wed, Thu, Fri
  • PBIs = Epic, User Story, Bug
  • Every PBI has Story Points
  • Every PBI subtask (Task) has Pending Effort
  • We plan sprint at the end of previous sprint (Friday) when we close previous sprint. When this is done I create or move all unfinished PBIs to new sprint and create subtasks with estimated Pending Effort. Everything is set up before next sprint starts on Monday (I tried also with Saturday and other date configurations, no effect).

Examples:

Attached I left images with burndown charts for our sprints. Green line is the one calculated originally, and the red one is as I think it should look like. Red line may point too high value, but the idea is important here - it should never be lower than value on the next day unless someone increase Pending Effort which is not pour case.

Files

effort.png (38.7 KB) effort.png Bartosz Firyn, 2016-10-18 16:34
sprint-39.png (47.5 KB) sprint-39.png Bartosz Firyn, 2016-10-18 16:59
sprint-40.png (54 KB) sprint-40.png Bartosz Firyn, 2016-10-18 16:59
sprint-42.png (46.9 KB) sprint-42.png Bartosz Firyn, 2016-10-18 16:59
sprint-41.png (54.1 KB) sprint-41.png Bartosz Firyn, 2016-10-18 16:59
#1

Updated by Emilio González Montaña about 7 years ago

Do you fill the estimated hours field?

Plugin uses that field as the first pending effort value in the burndown because the first date is like the day before the Sprint starts... so there is no pending effort defined for that day.

If you don't define the estimated hours it will use 0... except for not finished tasks from previous Sprints, they have in deed previous pending effort values (that's the reason some Sprints you have no 0 hours first date).

#2

Updated by Vito Marolda almost 6 years ago

Hello Mr. Bartosz Firyn, how dou you manage "Epics"? Do you create User Stories as children of Epics?
I am just curious, thank you for your time if you will answer my question.

Also available in: Atom PDF