> 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?
I hear you, and I think our product owner has too. We have a prototype implementation for a story point burndown, so this is something we seriously consider for the next release after this one, which means it will probably take a bit more than two months till we can get this out. However as always: patches with tests are welcome! Regards, Martin -- 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
