Weighting Issues

Practical Fibonacci for Beginners Here is the transcription of the text in the image:

This table provides a guideline for estimating work items in a Scrum context using a "Practical Fibonacci" scale, where different numbers indicate varying levels of effort, complexity, and risk associated with the tasks.

---

Practical Fibonacci

0	No effort is required, or there is some effort required, but there is no business value delivered, so no Points are accumulated for doing the work. An example is a desired behavioral change deriving from the Scrum Retrospective.
1	Extra small. Developers feel they understand most requirements and consider it relatively easy, probably the smallest item in the Sprint and mostly likely completed in one day.
2	Small. A little bit of thought, effort, or problem-solving is required, but the Developers have done this a lot, so they have confidence in the requirements. Or, it sounds extra small, but they want to hedge their bet just a bit.
3	Average. Developers have done this a lot; they know what needs to be done. There may be a few extra steps, but that’s it. It’s doubtful that they will need to research anything.
5	Large. This is complex work, or the Developers don’t do this very often. Most Developers will need assistance from someone else on the team. This is probably one of the largest items that can be completed within a Sprint.
8	Extra Large. This is going to take some time and research and probably more than one developer to complete within two weeks. In addition, Developers need to make several assumptions that increase the risk and could affect getting it Done.
13	Warning! This is a complex piece of work with a lot of unknowns and requires multiple assumptions to size. It is too much to complete in one Sprint. Instead, split this into multiple items that can be completed independently.
21	Hazard! A “21” or “34” reflects too much complexity to be done within one Sprint. It will need to be refined more. The large size also indicates more risk, assumptions, and dependencies involved to complete this item.
?	Danger! As a Developer, we don’t want to do this work the way it is currently written. It is very complex and cannot be completed in the timeframe of an iteration or Sprint. Perhaps the requirements are so fuzzy that it’s rife with danger.

---