Support for Burndown charts based on story points

[eng.amr...@gmail.com]

Dears,

Do you plan to support burndown charts based on story points? so that
the y access displays the total number of stories, and every time a
story is completed, the number of points decreases.

[Felix Schwarz]

eng.amr...@gmail.com schrieb:

> Do you plan to support burndown charts based on story points? so that
> the y access displays the total number of stories, and every time a
> story is completed, the number of points decreases.

We would implement that probably as 'burn up' (because imho it looks nicer if
you focus on the 'story points completed' than the other way round).

Yes, we plan something like that but not scheduled yet.

fs

[eng.amr...@gmail.com]

Thanks for the reply,

Is there a way to "push" it forward? I mean shall I request it
formally and may be vote for it?

I think it is a very basic feature, which is enabling tracking based
on completed features not spent efforts. This feature is a very basic
requirement by CMMI, as well as agile methods, as far as I know. In
all organizations that I worked for, we did tracking using size not
effort.

I would recommend that you keep the same burn-down chart as is, but
put an option to display it either following the completed story
points, or the remaining time as it does right now.

On Jan 2, 10:50 am, Felix Schwarz <felix.schw...@agile42.com> wrote:
> eng.amr.noa...@gmail.com schrieb:
>
> > Do you plan to supportburndownchartsbased on story points? so that

[Andrea Tomasini]

On 22 Jan, 2009, at 12:42 , eng.amr...@gmail.com wrote:

> Thanks for the reply,
Hi there :-)

> Is there a way to "push" it forward? I mean shall I request it
> formally and may be vote for it?

You can ask a customization, pay for some of the effort and have it
done faster :-)

> I think it is a very basic feature, which is enabling tracking based
> on completed features not spent efforts. This feature is a very basic
> requirement by CMMI, as well as agile methods, as far as I know. In
> all organizations that I worked for, we did tracking using size not
> effort.

True, now thanks to the transition to Flot we will have the chance to
make charts a bit more dynamic, so probably we could use some more
options, like choosing which lines to show... ;-)

We would also try to implement the "new" advanced burndown chart
developed by Mike Cohn which calculates the target released stories
based on worst and best velocities of the team ;-)

Stay in touch... one day it will happen, we are very few and very busy
also running customer projects, which help us surviving and paying the
development of Agilo... so if you want to join the development you are
welcome, and you are also welcomed to donate something, or ask for
customization in which case part of the effort will be payed and
priority set without problems...

Best
ANdreaT

[Amr Noaman]

Hi Andrea, 

Thanks for the clarification and the quick response. 

What I'm trying to do right now is to sell the idea that my company (and others whom I do some consulting for) deploy Agilo/trac as the standard tracking tool. If this is done, I would be pretty sure that we can get some paid customization requests. 

Anyhow, I will keep an eye on Agilo as I personally think that it is the best in the open-source community. The only pitfall is burn-down chart based on effort (not size); otherwise, the tool is typical for an agile community willing to achieve CMMI 3 and beyond. 

Regards,

Amr.