Agile Development: super easy to use bucket estimation system

“ Bucket estimation system ” It is a method to estimate a large number of items with small and medium-sized people , And it can be done quickly . The bucket estimation system has the following characteristics , Make it especially suitable for agile environments ：

• it Soon ！ You can estimate hundreds of items in an hour .
• This is a Cooperative . Everyone in a group participates roughly equally .
• It provides Relative results Not an absolute estimate （ Points and hours ）.
• The results cannot be traced back to individuals , So it encourages The team is responsible for .
• And The team Work together to estimate the workload or with stakeholders Value estimated by cooperation .

Bucket estimation system flow

The estimation work of the bucket estimation system is as follows ：

1. Set the physical environment according to the following figure . Make sure that all items to be estimated are written on the card .
2. Select an item at random from the set . Read it to the group . Put it on “8” In the barrel . This project is our first reference project .
3. Randomly select another item from the set . Read it to the group . The group discussed its relative position in size . once Consensus It has been achieved , Put the item in the appropriate bucket .
4. Choose the third item at random , After discussion and consensus , Put it in a suitable bucket .
5. If the random item has obviously tilted the scale towards one end or the other end , Then rescale the item （ for example , If the first item is actually very small and should be “1” In the barrel ）.
6. Divide and rule . Distribute all remaining items equally to all participants . Each participant puts the project on scale without discussing it with other participants . If a person has a project that they really don't understand , Then the project can be provided to others .
7. Integrity check ！ Everyone quietly reviews projects of scale . If participants find a project that they don't think is appropriate , They are welcome to bring it to the attention of the panel . Then the group discusses it , Until a consensus is reached and placed in one of the buckets .
8. Write the bucket number on the card , To record the estimate .

Some key points to consider ：

• Multiple items can be in the same bucket .
• Item cannot be placed in “ bucket ” To express a more accurate estimate .
• If the distribution of items is skewed to either end of the scale , So during the integrity check step , The group should also discuss whether the project can and should be spread out more evenly on a scale . If so , Then the group will work together .
• The counselor should take care to ensure that “ Sound inspection ” No one moves the placed items before the step .
• The project division between participants does not need to be exactly the same – Don't worry about “ Handle ” project . contrary , They are only roughly divided .
• If “ Divide and rule ” Oneortwo people work very slowly through their projects at this stage , It is acceptable to suggest that they share the remaining projects with those who have already completed them .
• It is not acceptable for individuals to abstain completely . If anyone wants to abstain , They should be told that this means that they will not have any future say in the estimates .
• stay “ Divide and rule ” Stage , Absolute silence is essential . especially , The project should not be discussed bilaterally . This is to protect the anonymity of individuals who place as many items as possible .

Bucket estimation system is a good alternative estimation method , Try planning poker instead . It's much faster than planning poker , But reasonable results can still be obtained .

Publisher ： Full stack programmer stack length , Reprint please indicate the source ：https://javaforall.cn/101125.html Link to the original text ：https://javaforall.cn