Hi Ronye, Am 21.02.11 21:21, schrieb ronyepires: > Previously, the Current and Ideal burndown began with the Capacity > (900). Capacity now starts at 900 and others begin at 80 (in this > example: http://flic.kr/p/9jbNxS). In some cases, they zeroed out: > http://flic.kr/p/9jY7jT
Hard to say - the first picture looks like you didn't commit in the sprint which makes the burndown just start at the number of hours that are already in tasks in the sprint when it starts (time based). If you commit after sprint planning, then the ideal burndown should start at the sum of task hours at that point. For the second picture - I have no clue. Could you give more information about your environment? Versions, when and from what you upgraded etc. Thanks! 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 have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
