I would say that it depends on the business policies and on how strictly one is supposed to follow them...

On my previous job, we were told to fill out timesheets... However, as there were only three people supporting network/Wintel servers/users etc, we decided we do not want to spend time on paperwork and the project promptly died...

In my current company, the timesheets are submitted weekly and are strictly enforced. The official reason is "...to track the time needed for the projects for the purpose of better resource management", although I believe the main reason behind them is the quarterly performance reviews...
The categories are selected from existing list (that's what the PlanView administrator is doing, building those categories); any new category I feel could describe my tasks better, should be properly documented and approved by an immediate manager.
The granularity is not strictly enforced though... you just enter a number in a box, it could be 1, or 1.5, or 1.25... The main goal is that in the end, there should be 37.5 hours of regular work per week.

All in all, I think it comes down to the question: Am I paid well enough to cope with what I believe is unproductive and/or plain stupid?... I know I am now, although that perception might change later :)

In reply to Re: Timesheets: What are they good for? by bofh_of_oz
in thread Timesheets: What are they good for? by eyepopslikeamosquito

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.