in reply to Timesheets: What are they good for?

Timesheets for client billing makes some degree of sense (although I still hate filling them out).

Timesheets to measure productivity are completely pointless. Hours worked (or hours in the office) has almost no bearing on productivity. Measuring this is a far more complex process, although one obvious factor is whether a project was completed on time, on budget and met all agreed upon requirements.

I think flexitime for programmers is essential (so long as they're available for meetings, etc). I might spend 4 hours of the day and complete 2 days worth of work, but forcing me to work another 4 hours wouldn't necessary equate to even 4 more hours worth of work (and could lead to me burning out). A smart manager will recognise this. Fortunately, I currently work with managers like this.
  • Comment on Re: Timesheets: What are they good for?

Replies are listed 'Best First'.
Re^2: Timesheets: What are they good for?
by Anonymous Monk on Apr 18, 2005 at 13:06 UTC
    But timesheets can work beneficial for the programmer (or whatever position you have) as well. If a manager asks why a specific project hasn't been finished, you can point to him how many other projects you have, and how you've allocated hours to the various projects.

    And then you can use that as a basis to come to a different allocation of hours.