Issue Estimation

[oliverschuerch]

As you may remember, we had that discussion some weeks ago, if we should add a number-based estimation to our tickets or not:
Add a number-based estimation

Pro and contra for one or the other approach has been discussed there and we don't need to continue that here...
However, most of us agreed, that we need a number-based estimation, but at the moment we have three redundant fields, to record that.

1. The size field (tiny, small, ..., NOT number-based)
2. The Original Estimation (Person Days) field
3. The Original Estimation (Story Points) field (number-based size field equivalent)

Both number-based fields were used to create some meaningful charts about the completion status of our v10 milestone:

• v10 Release Tasks - Burn down (amount of tasks)
  
• v10 Release Tasks - Burn down (Days)
• v10 Release Tasks - Burn down (StoryPoints)

The changes on these charts have been monitored during the last two weeks (see monitored data). The expected outcome has now occurred, and the percentage completion status of the two number-based fields are very close to each other. This means we can get rid of one of them and continue with the other one, without getting a completely inaccurate picture.

Be aware, that the size field is no longer needed and could/should be removed, as soon as all our open issues have a value in the choosen, number-based estimation field.