It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,841

question asked: Sep 11 '08, 1:27 a.m.
question was seen: 7,893 times
last updated: Sep 11 '08, 1:27 a.m.

Related questions

Scrum Release burndown chart

0
Shawn Lauzon (381●7●4) | asked Sep 11 '08, 1:27 a.m.
Wondering if anyone has thought about a release burndown chart, which shows burning down in story points from a set of estimated user stories at the beginning of a release to the end.

At the beginning of the release the team assigns a set of user stories to the release (possibly in specific iterations in the release), and each of them is estimated with story points. Then as the release progresses, stories will be completed and the line goes down. If new stories are assigned to the release, I would expect the line to go up. I think all the information that is needed is there, and it would be very useful for the Scrum template.

I haven't yet investigated if I could do this with BIRT myself, but wanted to see if others figured this out already. Thanks ...

shawn.

12 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
James Moody (3.3k●2●4) | answered Sep 18 '08, 10:11 a.m.
JAZZ DEVELOPER
Artem wrote:
I am a new guy here and not sure how to see whether this request was
implemented already :/

I am also very interested in the release burndown chart, because,
well, release burndown chart and velocity chart (TeamConcert calls it
"story points by iteration") are the must for Scrum.


Hi Artem,

Yes, the new report that Rafik and Shawn were talking about in this
thread has been implemented. It will be included in 1.0.1M3. If you'd
like it now, please have a look at work item 60942:

https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=60942

The .rptdesign file for the new report is attached to that work item, so
if you want to try it out, just download the attachment and create a new
report template with it.

Hope this helps.

james
Jazz Reports Team Lead
0
permanent link
James Moody (3.3k●2●4) | answered Sep 18 '08, 10:11 a.m.
JAZZ DEVELOPER
Artem wrote:
A good example with a picture and short explanation could be found at
http://www.mountaingoatsoftware.com/release_burndown

The key thing is that you show how many story points are still undone
before sprint 1, 2, 3, etc.

I admit that I can hardly imagine how one could do such a graph in
jazz (since to my understanding it is complex to track that a
particular story entered backlog or was reestimated during a
particular iteration), but if you do that, that would indeed move
jazz one big step closer to the Scrum support.


Thanks Artem.

I also see your comments in work item 55875, so that's where I'll follow
up to continue the discussion.

james
Jazz Reports Team Lead

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.