What good timesheet should and shouldn't have for a small (non programming) 50 people company?

Posted by MadBoy on Stack Overflow See other posts from Stack Overflow or by MadBoy
Published on 2010-03-22T18:33:55Z Indexed on 2010/03/22 18:51 UTC
Read the original article Hit count: 284

I'm sure most people here had to fill at least one time sheet in their life that made their life miserable, hell it's even the worst time taker ever especially after you have to fill it in hurry. I will be developing some simple TimeSheet application for a small company of 50 people (non programming related, it's actually 4 companies working together) and would like it to be user friendly and as less disturbing as possible.

So what in your opinion makes it a good timesheet (lack of it doesn't count :p), what data it should store? Should be only hours per day with possibility to choose project, company and simple overview what you have worked on like:

Day 1, 3:00, 'Company 1', 'Project5', 'Name', Short Overview
Day 1, 5:00, 'Company 2', 'Project6', 'Name', Short Overview

Or should it gather more data? Would it be realy bad if it were an WinForms application considering that I don't know ASP.NET or any other web based language? I would be deploying it using ClickOnce or so.

© Stack Overflow or respective owner

Related posts about discussion

Related posts about timesheet