Hi. We did commit the sprint at the first day. This used to work fine in previous sprints, even if they are not committed, and we didn’t anything different. Other projects faces the same problem, that’s why we suspect that it is bug on Agilo tool.
See below a screenshot of what is happening: 1) The “Capacity” line is OK, reflecting the team capacity. 2) The “Ideal Burndown” line is 0 all the time. It should starts with 703 (hours estimation for this sprint) at 16/02 and linearly go down to 0 at 12/03. 3) The “Actual Burndown” line is 0 all the time. It should starts with 703 and go down to 384 at present date (01/03). http://flic.kr/p/9n4pZ5 Versions: Trac: 0.11.7 Agilo: 1.3.0.7 Python: 2.6 Let me know if you need any other info. Thanks, Ronye -- 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
