On 16 Dec, 2009, at 12:21 , dhummel wrote: Hi Dietmar,
> On 16 Dez., 09:54, Martin Häcker <[email protected]> wrote: >> Hi Dietmar, >> >>> First I am wondering on how to define "working days". If I create a >>> sprint from 7.1.2010 to 21.1.2010 Agilo calculates this as 12 working >>> days. But we don't work on saturdays (and neiter on sundays ;-)... >> >> This should definitely not be the case. To understand this better, could >> you please elaborate on the timezones used on the server and on the clients? >> >> Also at what time does the sprint start and end? It may be that we have >> bugs in the calculations that try to mesh the timezones with the concept >> of working days (which turns out to be quite hard). > > Mea culpa! I found the "bug". The problem was that the sprint start > time was set to 0:00 o'clock. > This shows up as 23:00/day before on some clients (difference between > MEZ - UTC). > If I set it to 8:00 the calculation is correct. Keep in mind that the Burndown chart is shown according to the client set timezone, therefore if a client connects from UTC+5 and the sprint was set in UTC, the burndown chart and the dynamic lines will be shown with UTC offset, the weekends will be shown with the client locale. It is not an optimal solution, but the burndown must be bound to where the team sits, so the assumption we make is that the Scrum Master, that can create the sprint (or the Product Owner) are sitting close to the team ;-) We will improve these settings... soon ;-) > Regards Best > dietmar ANdreaT -- 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
