Shivam,
From the design it seems like the tasks are pre-defined for the
developers/coming from planning software. I say this because you
display task status and deadline as well. I think this is good as the
focus is task based.
My main question would be, do you really need to capture how much
effort was spent on each day? What if you keep it simple that the
developers update the remaining hours against each task daily. This
would be much simpler and faster for people to fill in. It also brings
a focus towards task completion and not on what the person spends each
day.
Task | Estimated hours | Remaining hours | Deadline
From analysis standpoint, people care about status of tasks and then
from billing standpoint how many hours have been reported. This will
be able to provide you the same information.
If you make it too granular, then in my experience, people tend to
fill in incorrect details to make sure totals are correct. In this
spirit time capture should not be a way of managing the team but only
manage tasks.
Cheers
AJ
On Aug 2, 2009, at 11:20 PM, Shivan Kannan wrote:
http://uidude.wordpress.com/files/2009/08/pmis.png
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
