Calculating release date based on velocity and backlog

[Jim Stewart]

We are using hours instead of story points. After three sprints, we have a velocity of 35 hours. That will likely improve. But let's say it doesn't and let's assume that it stays at 35 and the backlog doesn't grow. Is there a way for me to quickly calculate or get a report on how many hours are estimated in the backlog so I can get a rough idea of the completion date? I'm well aware that the actual development times won't be exactly the same as estimates. But we can add in a fudge factor. 

[Fabian Lim · Accepted solution]

Hi @Jim Stewart

I would create a jql filter that picks up all the backlog items with: project = ABC AND Sprint not in openSprints() AND Sprint not in closedSprints() AND Sprint not in futureSprints()

Then try using a gadget in a dashboard that adds up the time estimates.

If this doesn't work you may want to consider other reporting plugins in the marketplace.

[Jim Stewart]

Interesting. I'll give that a shot. I installed an app from the store called Team Health that purports to do what I want. But it kept crashing so I uninstalled it. No time for that. Thanks. 

[Jim Stewart]

Actually, on further research, it turns out that the backlog addition is at the top of the backlog. On discovering that, it was an easy matter to calculate the expected finish based on current velocity. 

[Yuri Lapin _Release Management_]

Hi @Jim Stewart,

Trust you are well.

In our App for Release Management and Roadmaps we have a notion of "projected release date". Below is the link to approach we use to calculate it.

https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081375/FAQ#FAQ-Howtheprojectedreleasedateiscalculated%3F 

Might be helpful.

Cheers,

Yuri.

[Jim Stewart]

That's very interesting, thanks. Just as I was researching this, we went on hiatus as the customer (startup) had to go back for more funding.. We await the next step, one way or the other.