Hi Roman, On Thursday 22 April 2010, Roman wrote: > So, what we do in general: create new User Story, set Story Points, > Assign it to Story Owner and split it into the set of Tasks with Task > Owners. Then such User Story is accepted and we start to implement > it. Everything is fine but! Actual\Ideal Burndown Chart shows no > increased Sprint Backlog, it looks like we have no new User Story > and fixing it gives us decreasing of Actual Burndown but it is false > decreasing since we previously increased our volume of tasks by new > hours in new User Story. It looks that if we pressed Confirm > Commitments then all other including User Stories will no affect > Burndown graphic. Is it correct?
Are you sure your added story is not counted for the ideal/actual burndown? What should happen when you add or remove a story mid-sprint is that its tasks are added to the actual and ideal burndown of all previous days, as if the story had been there right at the sprint start (or, for removal, as if the story had never been part of the sprint). Can you confirm this behavior with your installation? This is quite confusing, as you would expect the burndown data of previous days not to change, but rather show a sudden increase in remaining time when you add a story later. We've implemented this historic accuracy for burndowns as one of the major features of the next release, so you may profit from this for new sprints and in the meantime hopefully keep a better commitment ;-) Hope this helps, Robert -- 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
