Thanks for your answer, Felix. On Apr 20, 6:19 pm, Felix Schwarz wrote: > Am 08.04.2010 17:20, schrieb Manni: > > > 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. > > How could Agilo possibly come up with a number of hours just by story > points?
Not at all! I don't care about hours. If a sprint runs for two weeks, it's only logical that two weeks have passed when the sprint is over. I'd like to see a burndown in terms of story points. Whether the team was working overtime in that sprint or whether people spent their time staring out the window is and entirely different question - at least to me. > However there is something that you can do: We implemented a remaining > time/user story points ratio (accessible through the old backlog). So > you can select a few stories that you did detail completely (so you have > all tasks for these stories) and calculate a ratio for user story points > / time. Yes, I have seen that and tried it. But, I am sorry to say, it is awkward to use and it's not at all transparent what Agilo does when I click that button. Besides, when I get that story wrong I have f*ed up my backlog with a single button click. The team spends a lot of effort coming up with story points. Why water that down by applying crude factors that will never reach a stable value? -- 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 agilo@googlegroups.com To unsubscribe from this group, send email to agilo+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/agilo?hl=en
