In our sprint planning for the BBC Food website on Tuesday, we quickly estimated how long each task would take. Thinking about it today, I wonder whether that was sensible. Clearly it's important to ensure that there's enough time to get things done (and that there's enough things to fill the time available), but there are two problems that have struck me this week.
- Unless you're very familiar with the code, there's no way you can make a reasonable estimate (other than by chance).
- Putting a time against a task, even if it's an estimate and you know it's not accurate, means you're less likely to do the right thing when fixing it if that right thing is going to take longer than you've estimated the task will take.