Problem with Confirm Commitment in Agilo PRO 1.0.1 / Trac 0.11.5
Antonio David
I'm starting a sprint with the new release PRO 1.0.1, and once I have
all the tasks entered, with the sprint already started, but yet at its
first day, i press confirm commitment to update the graph of the total
work, and It's not working, It doesn't update the graph to the total
Remaining Time that appears at the bottom of the Sprint's backlog.
I have done it a lot of times with older versions and It has always
worked.
Thank you in advance.
Regards,
Antonio David.
Andrea Tomasini
On 11 Aug, 2009, at 9:32 , Antonio David wrote:
> Hi everybody,
Hi Antonio,
> I'm starting a sprint with the new release PRO 1.0.1, and once I have
> all the tasks entered, with the sprint already started, but yet at its
> first day, i press confirm commitment to update the graph of the total
> work, and It's not working, It doesn't update the graph to the total
> Remaining Time that appears at the bottom of the Sprint's backlog.
Did you try to restart the server? I just want to know if it is a
cache related bug or just a bug ;-)
> I have done it a lot of times with older versions and It has always
> worked.
I know, it should work ;-) I will try to reproduce this and enter a
bug for it if needed. Can you check if the "Estimated Velocity" is
entered in the team statistics for the sprint and if the "Commitment"
is there as well? Than it appears to be a burndown chart problem only...
> Thank you in advance.
YAW, thank you for reporting...
> Regards,
Ciao
> Antonio David.
ANdreaT
CKoenig
server, but the burndown chart still doesn't show the right values
after hitting "calculate story points/time" or "confirm commitment".
Regards,
CKoenig
Issam
Felix Schwarz
Strange for me it works... So we need to find out the difference in our
setups...
Can you send some system information ("About trac" - top right
navigation bar)? Do you use Apache/mod_python?
After you calculated the story points/time, is the remaining time sum at
the bottom of the table updated?
fs
CKoenig
> navigation bar)?
of the page the Agilo Version (1.0.1-pro). On the right are two logos
- "Trac" and "Python powered"...
> Do you use Apache/mod_python?
Don't know (how can I check?). I used the Windows installer. It is
installed on a Windows 2008 Small Business Server Premium 64bit.
> After you calculated the story points/time, is the remaining time sum at
> the bottom of the table updated?
burndown chart is that the remaining time (and therefore the actual
burndown) seem not to be displayed right, but (the gradient of) the
trend is calculated in some way and looks at least somehow right. See
http://www.dglr.de/bdc.png.
Regards,
CKoenig
Tod
CKoenig
Sometimes (??) it works once a day: the last two days, when I reloaded
the sprint backlog the first time (i.e. when I start to work), the
hours in the burndown chart where updated to the actual value. Later
modification of the tasks in the sprint didn't change the burndown
chart.
dbrain
I have similar problems. We use Agilo 0.8.0-RC2-r1719-20090719 and I
always see differences between what Agilo caluclates and what is
displays on Burndown chart. I've uploaded 3 screenshots form our
current sprint:
1. Sprint Backlog (http://online.print2flash.com/content/
8ea2b604e1eea73ca6e81029df8f764a/)
2. Team statistics (http://online.print2flash.com/content/
67a77f1151113307b472fa42f3d45aa3/)
3. Team Planning for Sprint (http://online.print2flash.com/content/
2ba82e5fe93a83ef14e19a23f9d37c00/)
I can point following problems there:
1. Why Burndown chart starts from ~180h when initial commitment was
over 200h?
2. Why in the 2nd day of the sprint the Actual burndown (blue line)
goes up when we did not add any new tasks and only reduce hours in
tasks that day (I can provide log from Timeline)?
3. Why there's "n.a." value in "Total Estimated Remaining Time"
For the time being I love Agilo, but because of this issues I still
did not decide to switch to PRO version.
Are there an ability to make following feature: click on day on
Burndown chart and see what changes has been made that day? That would
be really helpful in understanding what's happening...
--
Best regards,
Anatoly
Felix Schwarz
>> Can you send some system information ("About trac" - top right
>> navigation bar)?
> Eh? There is no more information just licence info and at the bottom
> of the page the Agilo Version (1.0.1-pro). On the right are two logos
> - "Trac" and "Python powered"...
Ah, sorry you have to login in as a user with TRAC_ADMIN rights ('admin'
in the windows installer)
>> Do you use Apache/mod_python?
> Don't know (how can I check?). I used the Windows installer. It is
> installed on a Windows 2008 Small Business Server Premium 64bit.
Ok, then you're using tracd.
fs
CKoenig
> >> navigation bar)?
CKoenig
As I mentioned above, we were running Agilo on a Windows 2008 Small
Business Server Premium 64bit. Today I copied the installation to my
local computer (Win XP SP3 32bit) for testing purposes. There
everything works fine...So I guess it's something with that 64/32 bit
stuff, but no idea, how to solve this..
Martin Häcker
> I can point following problems there:
> 1. Why Burndown chart starts from ~180h when initial commitment was
> over 200h?
This is strange - the burndown looks like your team added lots of tasks
after the start of the sprint (in the first two days) and only then
started working on the stories.
> 2. Why in the 2nd day of the sprint the Actual burndown (blue line)
> goes up when we did not add any new tasks and only reduce hours in
> tasks that day (I can provide log from Timeline)?
This is strange, if you could send the logs, that would be greatly
appreciated.
> 3. Why there's "n.a." value in "Total Estimated Remaining Time"
This seems to be caused by the fact that there are still stories with no
estimates.
To get the total time, you would either need to estimate all stories, or
estimate a subset of those, and then tell trac to use those stories to
calculate an estimation for the rest.
For more details see
<https://enterprise.hosted.agile42.com/agilo-help/user/Backlog#CalculatetheUserStoryPointsRemainingTimeratio>
> Are there an ability to make following feature: click on day on
> Burndown chart and see what changes has been made that day? That would
> be really helpful in understanding what's happening...
Thats actually a nice Idea, I'll send it to our product owner.
HTH
--
Mit freundlichen Grüßen
Martin Häcker
Consultant
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