Estimating (Scrum)

Uit De Vliegende Brigade
Naar navigatie springen Naar zoeken springen

Questions

  • How about an issue that is easy but takes a lot of time?

Issue metrics

What issue metrics to use for project management?

  • Effort: Preferably with a short scale. I quite like BUS or maybe fibonacci numbers
  • Time estimate: maybe, within a sprint, using time estimates would be appropriate?
  • Uncertainty: Keep separately track of uncertainty surrounding issues? Might be worthwhile. Example: An unclear bug that can't really be verified, unknown impact and unclear consequences
  • Priority: Priority and therefore precedence is an important metric. Especially if stuff is on the critical path.

Fibonacci numbers & effort

Some indications when using Fibonacci numbers (1, 2, 3, 5, 8, 13, 21) to express effort:

A two-week sprint is about 10 points.

1

You can do two 1-point issues per day

2

Takes a day.

3

About 1.5 days

5

  • Takes about 2-3 days
  • No need to split into smaller issues.

8

  • Takes 3-5 days, or one-third to half a sprint
  • Better split into smaller issues?

13

  • More than a sprint
  • Definitely cut into smaller issues.

See also