Hi. We are currently evaluating Agilo for use in our environment and while we were able to build a nice backlog, the burndown chart still puzzles us. Or maybe we just aren't sure what we should do during our planning meetings.
Here's the problem: The Agilo documentation (correctly) stresses, that Scrum tries to rely on story points instead of actual hours or days. So we assign story points to our stories. That alone isn't enough to come up with a decent burndown chart it seems. Agilo wants us to fill in the remaining time for our tasks. BUT: How are we supposed to know? Why are we supposed to know? And if that is so important, why can I not simply enter some hours-per-story-point factor somewhere and be done? Am I really supposed to calculate this myself for each task? One problem with the burndown chart is that the ideal burndown is currently (at the beginning of the sprint) about 5 times as large as our actual burndown. Which makes the team look like a bunch of idiots to the outside observer. The only way around this seems to be recalculate the remaining time for each and every story. But if I did that, why would I bother coming up with story points? Is there something really basic I am missing here? Regards, Manni -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en To unsubscribe, reply using "remove me" as the subject.
