4 ms·
I've been at a few companies that required timesheets of software devs, and it was always weird/awkward at best. They never wanted just hours - they wanted to
by mgkimsal 16y ago
I've been at a few companies that required timesheets of software devs, and it was always weird/awkward at best. They never wanted just hours - they wanted to know what was done as well.
Sometimes it's easy, sometimes it's not, but the thing that bugged me was that it eventually was used against you.
Mgr: "Oh.. well.. I see here you've only put in 38 hours on core projects this last week... this doesn't look too good to others."
Me: "Well, I was actually here in the building for 46 hours, but 8 of those hours were doing some other stuff that there's no timesheet entries for."
Mgr: "Oh... like what?"
Me: "Like answering questions from people in the building that have questions about some of the projects I'm working on - status updates, etc. Apparently you and the other managers aren't updating anyone, and they ask me."
Mgr: "That's not your job."
Me: "So... I should silently ignore them, or give them a canned response to go ask their own dept manager?"
Mgr: "yes. But that didn't take 8 hours last week!"
Me: "I was also doing some research on a couple new debugging tools."
Mgr: "There's no need for that - the senior engineers are making their decision next week about what tool you'll use."
Me: "OK...."
Mgr: "I don't want to see you make a habit of 38 hours a week from now on."
Me: "Ummm... the last 3 months I've been putting in 45-50 hours non-stop, and have been in on some weekends to work with some other people to hit the deadlines."
Mgr: "Yeah, that's great, but 38 hours..."
This is a composite of discussions I've had and colleagues have had with various managers over the years whenever timesheets are involved. YMMV.
- dennisgorelik 16y agoMgr could not say it directly, but he implied that timesheet must have 40 hours reported on the main project. How hard could that be to write it down like that? I understand that it's still unpleasant to deal with that.
- mgkimsal 16y agoSo... lie. If they want dishonesty, just ask for it.
- dennisgorelik 16y agoThe manager wanted to see 40 hours reported against his main project. He did not want dishonesty, but probably would not mind some tweaking in how work activities are categorised in a timesheet.
- rbarooah 16y agoHow is this 'not wanting dishonesty'?
- bad_user 16y agoI used to do it. Incredibly easy too. Like once, in a sprint that took 5 weeks, the last week was scheduled for bug-fixes / quality assurance. I did nothing for 3 and a half weeks, finished my assignments in 2 days, then for a whole week I just fixed a couple superficial bugs here and there. Reported time: ~ 170 hours. EDIT: to expand on this point, the secret is in how you do the initial estimation. Hugely overestimate the small / easy tasks (explain with technical babble if needed) , then underestimate the difficult tasks. So not only will you secure lots of free time, but you'll also be that genius that finishes difficult tasks in 1 hour :-) Heck, you might even be promoted to management; that's how all the cool kids in management are doing it :)
- danssig 16y agoYou're taking all this a bit too seriously. It is not time efficient to log what you actually do, so what I always do is just ask my manager what percentage of my time is supposed to go where. Once I know I just fill my time sheet out that way. The whole thing is effectively just a double booking of project spending anyway. It baffles me why everyone does this manually instead of automating it. I don't really need to be involved at all. EDIT: Thought better of it and changed my message. But I still think your manager is a moron since he's unable to point out the above, and life is too short to work for people like that.
- mgkimsal 16y agoJust for the record - this is a composite of various conversations over the years, and does not reflect specifically on any one manager I've directly reported to. Also... I'm taking it too seriously? Over a 2 month period when, say, 400 hours are logged, but one week 2 hours are not accounted for in a specified (yet unspoken, hint hint, nudge, nudge) manner, and I'm taking it too seriously?
- danssig 16y agoOk, so seriously isn't the correct word. You're taking it too literally. They don't want to know how many seconds you spent typing code or thinking about code. They have a budget where some department has purchased 40 hours per week for you to work on their main project. Presumably you have smaller time bookings for other tasks. If you break this down it will come out to something like: 98% main 1% support 0.5% boss' pet task 0.5% other All they want is for your time sheet to match that because that's what they've paid for. Some managers are smart enough to just tell you that, others (like the one you appear to have) don't like to say it for some reason. They should just automate it because the numbers you plug in are completely static. It's just double booking, one side put in a "debit" for the project and now you're putting in the "credit" side saying it was paid. No one cares what you actually did because the exact moments you spent on the project shouldn't affect anything (assuming you're not a problem worker).
- 16y ago