Martin, Thank you for your response. We use the CSV download to generate release notes at the end of the sprint. we can create that report using a custom query, but it's simpler to just use the link at the bottom of the sprint backlog. We definitely use the story points total to evaluate the volume of work that is allocated to the sprint. it is our best 'rule of thumb' to determine total work vs total team velocity. i would prioritize this above the csv download. i don't know of another simple way to achieve this. Thanks' -Craig
On Tue, May 11, 2010 at 4:13 AM, Martin Häcker <[email protected]>wrote: > Hi Craig, > > > these are all features that are found in the old backlog and we miss > > them :( You may well have already planned to put them in the next > > release. > > Hrm, well, not all of these things will work in the next release. And > some only with kind of workarounds. > > Editing before a sprint starts: sure, thats a bug and we fixed that. > Number of hours in a sprint can be seen in the burndown, but we don't > show the computed number in the backlog for now. > > As for CSV Download and the sum of story points, those are not in the > new backlog yet, so I would really like to know how relatively important > those features are to you and what you use them for so I can use that to > talk to our product owner. > > Thanks! > > Regards, > Martin > -- -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/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
