During the dev meeting today, the following discussion (this is a rough transcription) went down:
Manager: So, what can I do to help remind people to send their hours for the last week in on time?
Dan: Well, I don't know about other people, but for me, the problem is that it's hard to tell what hours I've already put in. The ActiveX control only lists which hours have changed, not what changes I've made.
Manager: So, if that were easier to use, you'd be more persuaded to get your hours in on time?
Charles: You know, at any other place, in any other profession, this wouldn't be a problem. The manager would say "get your hours in on time," and there wouldn't be a discussion about it.
Dan: Yeah, well, I'm a software engineer. This isn't Smith-Barney. I'm not wearing a tie.
Manager: I'm not trying to get you guys to come in at 9:00 or 10:00 or anything. All I want are people to submit their hours.
4 comments:
This is why writing and selling a management book is probably the quickest and easiest way to make money.
Which is why Fred Luthans now gets to torture students... funny that I read that while in his class.
Since a couple people have asked, I figured I would clarify. I don't report "hours," per se, as in "I worked 40 hours this week"; I report 24 hours' worth of work as my status report. For example, "I worked 12 on task A, and 12 on task B." I don't really know why it's 24 or why it's "hours"; they're just somewhat-arbitrary effort units.
Actually, come to think of it, I do know why they're called hours. That's what MS Project calls them.
Post a Comment