Predefined expected velocity

Fredrik Ivansson Flinta

Is it possible to have a predefined expected velocity using Release Burndown?

From what I have found Jira needs three sprints to be able to calculate an average velocity and after that the forecast of finishing the release can be calculated.  

 

What we want is to make a chart with two lines: one “ideal burndown” and one “actual burndown”.

 

Ideal burndown: this line is based on a predefined hardcoded value provided by team that shows the expected burndown and date of finishing

Actual burndown: Shows our actual burndown based on closed user stories

 

I think the Release Burndown is kind of what we need but we want this hardcoded expected velocity to be able to track if we diverge from the original plan.

Petter Gonçalves

Hello Fredrik, 

Thank you for raising this question.

The release Burndown chart will automatically display the estimation you have configured to your Stories (as you mentioned, the predefined expected velocity) against the current progress on your Stories, so you can easily check if your actual progress is falling behind or ahead of your original estimation.

To calculate your release estimation, the report will sum from your Stories the value of the fields you have configured to track the estimation on your board: Original Time Estimate or Story Time Estimate. 

To calculate your current progress on Issues, the report will use the Time Spent or the Story Point Fields also configured based on your Board estimation.

P.S: the changes performed on these fields will be automatically applied to the report.

Please, check the documentation below to know more details about it:

- Release Burndown Documentation