Hacker News new | ask | show | jobs
by alexhutcheson 2455 days ago
1. Keep your baseline tasks you're comparing against consistent for as long as you can (as long as the team remembers them and agrees on the effort they required). Don't use a task from week 2 to estimate week 3, etc.

2. Don't use a short time interval or moving average to determine your points->time mapping. You're looking for the long-run average mapping, not a specific estimate for this developer today.

1 comments

+1 , this guy knows what's up. Relative estimates work really well, from my experience!