[Agilo for Scrum] Total Time Remaining wrong in Sprint Backlog
CKoenig
when I add user stories that contain tasks to a sprint, the total time
remaining is calculated wrong in the sprint backlog (in the table and
the burndown chart). Sometimes (haven't figured out when exactly) the
total time remaining grows when I select the user stories and hit the
"calculate story points/time" button.
To make it even more strange, the new values contain fractions of an
hour, e.g. when single remaining time values are set as integers (say
1 + 2 +3 hours), the total result contains fractions (e.g. 10.4
hours)...
Using Agilo 1.1.1 Windows Installer Version on a Windows Vista 32bit
Computer.
Regards, CKoenig
Here is the content of the "About Trac" page: http://www.dglr.de/_agiloconf.htm
Dennis P. Nikolaenko
> Hi everyone,
>
> when I add user stories that contain tasks to a sprint, the total time
> remaining is calculated wrong in the sprint backlog (in the table and
> the burndown chart). Sometimes (haven't figured out when exactly) the
> total time remaining grows when I select the user stories and hit the
> "calculate story points/time" button.
>
> To make it even more strange, the new values contain fractions of an
> hour, e.g. when single remaining time values are set as integers (say
> 1 + 2 +3 hours), the total result contains fractions (e.g. 10.4
> hours)...
>
> Using Agilo 1.1.1 Windows Installer Version on a Windows Vista 32bit
> Computer.
>
>
I have seen this behavior with 1.0.x series of Agilo Pro. Maybe this is
still an issue with 1.1.x.
At one time our current sprint had some tickets, which were transferred
from the previous sprint.
These transferred ticket forced calculation to be wrong.
If I filled 0 in Remaining Time for all of the tickets assigned to the
current sprint, Total Time still remained above 0.
I could not reproduce this problem any more, adjusting several times the
server clock may be needed, to see this effect.
I just was not motivated enough to reproduce this bug in a "minimal case".
--
Dennis
CKoenig
> from the previous sprint.
affected. When I create a new sprint with new stories and tasks, this
the described error does not occur.
CKoenig
Martin Häcker
transfer stories from one sprint to the next.
Could you perhaps make available to us an environment that shows this
behaviour? We can probably reproduce and fix the problem pretty quickly
then.
If you can, just send the link to <sup...@agile42.com>
Thanks in advance!
Regards,
Martin
CKoenig
> behaviour? We can probably reproduce and fix the problem pretty quickly
> then.
It contains the tracenv/test directory from a fresh Agilo Windows
Installer Installation (so usernames and environment are the same as
for the demo project).
To create the error, I did the following steps:
1.) created the sprint test1
2.) added a user story teststory1 and added it to the sprint test1
3.) added 2 tasks (testtask1 and testtask2) to teststory1
3.) closed the sprint
4.) created a new sprint test2
5.) moved the teststory1 and its tasks to sprint test2
6.) created a new teststory 2 and added it to the sprint test2
7.) added 2 tasks (testtask2a and testtask2b) to the teststory2
8.) hit the calculate story points/time button
Regards, CKoenig
Martin Häcker
of sprint two of the environment you sent me.
I don't however.
Could you elaborate on the steps - did you add story points on stories?
Did you add remaining time on tasks?
Did you set any other fields?
Did you move the remaining tasks when closing the sprint, or did you do
it manually after you closed it?
Maybe that helps me debug this.
Regards,
Martin
Felix Schwarz
> Sometimes (haven't figured out when exactly) the
> total time remaining grows when I select the user stories and hit the
> "calculate story points/time" button.
To me this could be explained by the RT/USP ratio:
If you calculate a new RT/USP, this will be applied immediately to all
the stories in the sprint. If you have stories that were not broken down
already and the new RT/USP ratio is higher, you will have a bigger total
remaining time.
Could that solve/explain your problems?
fs
CKoenig
> of sprint two of the environment you sent me.
>
> I don't however.
support email?
> did you add story points on stories?
> Did you add remaining time on tasks?
> Did you set any other fields?
Team)
> Did you move the remaining tasks when closing the sprint, or did you do
> it manually after you closed it?
the first one.
I also changed the computers date to simulate real time flow. For
creating the first sprint and the story I put the computers date back
to 2.12.2009. Set sprint ending to 4.12.. Assigned the story and
tasks, then confirmed the commitment. After that, I changed the
computers date to today and closed the sprint from the roadmap view.
When asked to retarget the remaining tickets, I chose 'None', as there
was no new sprint yet. I created the second sprint, moved the existing
story and its tasks to this sprint, and created the second story and
its tasks.
CKoenig
> If you calculate a new RT/USP, this will be applied immediately to all
> the stories in the sprint. If you have stories that were not broken down
> already and the new RT/USP ratio is higher, you will have a bigger total
> remaining time.
>
> Could that solve/explain your problems?
sprint), the calculated value for the Total Remaining Time at the
bottom of the table for the sprint shows a value larger than the sum
of all tasks. Think that does not have to do anything with the User
Story Points, right?
Felix Schwarz
> Think not. When I sum up all Remaining Times (from all tasks in the
> sprint), the calculated value for the Total Remaining Time at the
> bottom of the table for the sprint shows a value larger than the sum
> of all tasks. Think that does not have to do anything with the User
> Story Points, right?
It could if you have user stories without tasks. If all your user
stories have tasks attached, the increase should not happen.
fs
CKoenig
> stories have tasks attached, the increase should not happen.
>> 2.) added a user story teststory1 and added it to the sprint test1
>> 3.) added 2 tasks (testtask1 and testtask2) to teststory1
Martin Häcker
Am 10.12.09 13:43, schrieb CKoenig:
>> of sprint two of the environment you sent me.
>>
>> I don't however.
> Have you tried the steps or did you use the environment I sent to the
> support email?
>> did you add story points on stories?
> Yes. Chose 5 for both.
>> Did you add remaining time on tasks?
> Yes. Chose different times.
>> Did you set any other fields?
> The sprint field and the 'asign to' field (I chose Mary from the Demo
> Team)
>> Did you move the remaining tasks when closing the sprint, or did you do
>> it manually after you closed it?
> I did move them manually as the new srpint did not exist when closing
> the first one.
> I also changed the computers date to simulate real time flow. For
> creating the first sprint and the story I put the computers date back
> to 2.12.2009. Set sprint ending to 4.12.. Assigned the story and
> tasks, then confirmed the commitment. After that, I changed the
> computers date to today and closed the sprint from the roadmap view.
> When asked to retarget the remaining tickets, I chose 'None', as there
> was no new sprint yet. I created the second sprint, moved the existing
> story and its tasks to this sprint, and created the second story and
> its tasks.
stories and you moved them differently.
Still I can neither see the weird behavior on the existing environment
you sent me nor was I able to reproduce it the way I did.
I'll see that I look into that after the weekend.
Thanks for the detailed steps analysis!
Best Regards,
Martin
Martin Häcker
> Ok, I didn't assign the tasks.
>
>>> Did you move the remaining tasks when closing the sprint, or did you do
>>> it manually after you closed it?
>> I did move them manually as the new srpint did not exist when closing
>> the first one.
>
> Ok, I moved when closing the sprint.
Still this is completely not reproducible.
Could you please provide more details about your runtime environment? As
far as I remember it is a windows mashine. If so, which version? What
python?
Perhaps there lies the root of this problem.
CKoenig
> far as I remember it is a windows mashine. If so, which version? What
> python?
Python 2.5.4
For more details of the system environment I had linked the 'about
trac' details page in my starting-post: http://www.dglr.de/_agiloconf.htm
You may download my complete Agilo Test Installation (from C:\Program
Files\Agilo) containing the whole test environment here:
http://www.dglr.de/_agilo.zip
If time permits I'll try to reproduce the error on another computer
here, too. But at the moment I'm a bit short of time.
Thanks for your efforts to find/solve that problem...
Regards, CKoenig
CKoenig
error.
When I copied the directories from the Vista machine and updated the
pathes (incl. trac-admin resync) I also got the errors in those
projects on the XP machine.
Is there any information stored outside the agilo directory? Maybe
somwhere in users/... ?
Regards, CKoenig
CKoenig
- sorry for that):
I was now able to reproduce it on the XP machine. Think I'm close to
the source of the problem now.
New Installation.
- login as po
- create a new sprint s1
- create a new userstory u1 (assign it to sprint s1, USP=5, assign to
user po)
- create a new userstory u2 (assign it to sprint s1, USP=5, assign to
user po)
- logout
- login as mary
- break up the sprints into two tasks each (task1a, task1b for u1;
task2a, taks2b for u2). Assign each task to user mary. Set remaining
time to [task1a: 2h, task1b: 1h, task2a: 3h, task2b: 2h]
- logout
- login as sm
- view sprint backlog for s1
- mark the userstory u1 and the linked tasks task1a and task1b and hit
"remove selected"
- logout
- login as po
- go to the product backlock, view the details for the userstory u1,
edit details, and assign it to sprint s1 (again)
- logout
- login as sm
- view the sprint backlog for s1
- mark both userstories and hit "calculate story points/time"
I got total time of 12h now, instead of 2+1+3+2 = 8h.
Regards, Ckoenig
CKoenig
mentioned above?
Martin Häcker
> @Martin: were you able to reproduce the issue with the steps I
> mentioned above?
Sorry for taking so long to answer - I was on holiday over the
year-change and thus have an enourmous ammount of mail to work through.
I tried these instructions yesterday and got the correct results from
applying them.
I.e. the resulting hours where again 8.
Either I am still doing somethign different than you do, or we
accidentally fixed this bug in the latest release (thats what I tested
against).
This is a real possibility, as we simplified the way tickets where
gathered from the db for a sprint.
Could you perhaps either tell me again which version this was tested
against or even repeat this test with the current version at your place?
(If it still happens then, it has to be something else still - or I
didn't follow the instructions correctly).
Many Thanks in advance,
Martin
CKoenig
> Either I am still doing somethign different than you do, or we
> accidentally fixed this bug in the latest release (thats what I tested
> against).
>
> This is a real possibility, as we simplified the way tickets where
> gathered from the db for a sprint.
With the new version (1.2.0) it works fine. Thanks for that one ;)
By the way: the new version looks great! But one question: is it right
that one can not see the latest Agilo version number on the agile42
website? At least I wasn't able to find it... maybe you want to change
that. A version history (incl. details on changes) would also be
great, but maybe I was just not looking for it hard enough... :)
Regards,
CKoenig
Martin Häcker
Ahh, great to hear that!
> By the way: the new version looks great!
Thanks!
> But one question: is it right
> that one can not see the latest Agilo version number on the agile42
> website? At least I wasn't able to find it... maybe you want to change
> that. A version history (incl. details on changes) would also be
> great, but maybe I was just not looking for it hard enough... :)
Good point! I've filed that as a feature request (I want that too!)
For now you can find the release notes in the blog. As a quick fix you
could perhaps subscribe to the rss feed.
Best Regards,
--
Martin Häcker
Consultant & Software Engineer
agile42 GmbH
www.agile42.com
Grünberger Str. 54
10245 Berlin, Germany
Office: +49 30 2005 3958
Fax: +49 30 2007 8274
Amtsgericht Charlottenburg: HRB 111402
CEO Marion Eickmann