Re: [Usability] Google Code-In 2011 time in hours

Hi Andika, 

[For future responses, please strip the long CC list.]

On Thu, 2011-11-17 at 08:56 +0700, Andika Triwidada wrote:
> After you have converted all estimated time from days to hours, it
> seems that every task,
> even the simplest one, need much more time than initially. For
> instance, when I wrote
> a 2-days task of translating 'dictionary manual' into Indonesian, I
> was thinking of
> max two 8-hour days, not two 32-hour ones.

While I increased a few deadlines, you picked a bad example:
Your proposed timeframe for Dictionary Manual was "3-4 days", see
https://live.gnome.org/action/info/GoogleCodeIn/Tasks?action=diff&rev2=193&rev1=192#line-478
I turned your "4 days" into "100 hours". 
I think that's quite appropriate (4 hours more).

> Should each of us revise those time estimations?

No.

In general: It doesn't hurt anybody if a student hands in the work
earlier, plus having more time for reviews/iterations. 
Plus keep in mind the time it takes to set up infrastructure (e.g.
learning git, understand required applications etc, Learning curve, time
zones, etc).

andre
-- 
mailto:[email protected] | failed
http://blogs.gnome.org/aklapper | http://www.openismus.com