I always have felt that such reports are only required when your boss is too stupid and/or lazy to understand what you do, let alone remember what they asked you to do in the first place!

Having been a boss several times, let me offer up the other side of this. Status reports serve several purposes. First, they provide a uniform way of gathering some of the information that goes into annual reviews. (A boss should be taking notes along the way, anyway.) Think of this as a record of what happened. You might write something like

"I reworked the vendor's example script, breaking out useful parts so that we could reuse them, and adapting the script to provide two command-line tools that use our database."

Second, status reports provide a way for a boss to verify that you're doing what they expect. It's a poor way, but it's a way. You'd think it would be a simple matter of wandering around and looking, except that takes a lot of time, and bosses are often just as starved for time as you are. (There's often nuttiness going on at a higher level that you see very little of.)

Third, status reports provide weekly time for you to step out of your rut and reflect on what you've been doing. Most good developers will do this on your own, but requiring the status report is a way to stick this opportunity in everyone's face.

Fourth, reports are a way to gather input from people who might otherwise sit on it. Many of the managers I've worked for have asked for a "Problems/Suggestions" section on each report. In your case, a reasonable thing to note (assuming you haven't done this already) is

"I have concerns about the quality of the work we're getting from our vendor. The example they provided was poorly written."

And fifth, there's the possibility that your boss is also under a requirement to provide a status report. Asking his/her staff for reports provides raw material, making his/her job somewhat easier.

In reply to Re: (OT)Employee Status Reports or Shameless self-promoting by dws
in thread (OT)Employee Status Reports or Shameless self-promoting by LameNerd

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.