Re: [Usability] Google Code-In 2011 time in hours
- From: Andre Klapper <ak-47 gmx net>
- To: Andika Triwidada <andika gmail com>
- Cc: gnome-love <gnome-love gnome org>, usability gnome org, gnome-bugsquad <gnome-bugsquad gnome org>, GNOME Documentation <gnome-doc-list gnome org>, GNOME i18n <gnome-i18n gnome org>, desktop-devel-list <desktop-devel-list gnome org>
- Subject: Re: [Usability] Google Code-In 2011 time in hours
- Date: Thu, 17 Nov 2011 12:17:08 +0100
[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
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?
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
mailto:ak-47 gmx net | failed
http://blogs.gnome.org/aklapper | http://www.openismus.com
] [Thread Prev