|
|
|
|
|
by kabdib
4642 days ago
|
|
I usually keep a local "todo" list in each project I'm on. It helps me focus, and if I'm away from a project for a while it helps me figure out what I've done (I seldom remove old entries, as it gives me a sense of history). Like most processes, it's better to keep something like this lightweight. "Nested todos" are about as fancy as things get. I also check the todo lists into the project. Sure, it makes things a little dirty. On the other hand, it saved another person's bacon last year when I was forced to flip ownership of a project over to that person without much warning. (He discovered the todo list, and emailed me a huge thanks). Todo lists in a wiki can work well to keep a loose team on the same track, too. Again I think the secret is to keep this lightweight. If you're installing "Whizzy Enterprise TODO" servers or having meetings about how to manage todo items or trying to extract metrics from todo lists, my guess is that you've put too much drama into the process and should take a walk to cool off. :-) |
|
The times that I've shared my TODO list with a project manager, I've regretted it. This /could/ simply be that the kind of PM who makes a schedule based on snapshot of an engineer's loosey-goosey list is a clueless git who is not to be trusted. Even when I've directly shared the list and TOLD the PM "Look, don't make a schedule off of this, it's just a basis for discussion" the next thing I know the list has been enshrined in a PowerPoint deck and has become Gospel all the way up. Whereupon the following conversation happens with my mangler [sic]:
"Figby the PM is a clueless git."
"Don't worry. The PM management chain is trying to fire him."
"Couldn't happen soon enough. But what do we do about his PowerPoint deck?"
"I think we're screwed."
"Next time I'm going to line up the items so the first letter of each line reads 'FIGBY IS A CLUELESS GIT'" and then point that out in the scheduling meeting."
"(sighs heavily)"
My mom thinks I'm in high tech.