views:

122

answers:

3

My current job has somewhat of a more structured methodology than I'm used to and I'm asked to write detailed task lists and estimations before working on a block of functionality. For some reason, I have an awfully hard time doing these and I spend a lot of energy fighting my resistance to these tasks instead of just doing them. It's kind of a trend I recognize in myself of resistance to anything that is not coding, e.g. time reporting. Any advice on this?

+3  A: 

When presented with these kind of issues, that you don't necessarily agree with but just have to do, there is only really one way forward - do it. I know you want someone to acknowlegde your pain, say it's ok, we'll change the process, but even that won't happen unless you play ball in the short term. So my approach - do the minimum, do it at a set time - first thing is not a good idea, you're wasting the best part of the day. How about working on your list of tasks, last thing each day - that way it impacts least on your productivity, and if it's scrappy so be it.

MrTelly
+1  A: 

I believe the main reason why developers try to avoid those tasks has to do with fear of not been precise/good enough. Another fear (sometimes justified) is that our estimates will be used against us. Sometimes they will, and that's almost unavoidable. :-)

Practice will make it easier, but practice alone is not enough.

Along with doing your task list and estimations, make sure you go back to them to see how good/bad your predictions were.

Practice + learned lessons will make you get better results.

Also, talk to other team members to see how they approach those tasks.

And above all, don't feel that you have to be 100% (or even 50%) right. It's an estimation, isn't it?

Klinger
A: 

I agree with @Klinger in making sure you go back to them to see how good/bad your predictions were. When you see how bad your intitial estimates are, and how many tasks didn't occur to you to add to the initial task list your, competitive juices might start flowing to make it better next time.

A bit like building a SO reputation is mildly addictive, you may find yourself taking pride in producing accurate TODO lists and estimates.

MadMurf

related questions