Search code examples
project-managementproject-planningestimationtask

How far should you go with estimating your tasks?


What is the good resolution of time to use for estimating duration of your tasks?

is it like 0.5, 1, 2, 5 days or should you go down to hours like 0.5, 1, 2, 4 hours and then continue up to days?

should a change to a label text be task at all? ( ETA < 1min )

Suggestions?


Solution

  • Scrum uses values of 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40 and 100. The time of the values is in hours, when you plan in finer detail (breaking down feature requests into technical tickets) and days, when you plan the bigger picture (big-picture features).

    In general, if you estimate a ticket over 20 hours (or 20 days), your tasks should be split up into smaller pieces.