In Scrum, you are not measuring work in absolute terms like hours spent or lines of code to be written. Two reasons for this:
- Not everyone works at the same pace or has the same set of expertise and experience.
- Until you do the job, these are unknown and, at best just guesses.
The problem with absolute sizing using hours is you begin to measure the people, not the work. Relative sizing measures the new work against past work shared by the whole team. Instead, the work is sized relative to past work already completed. So when looking at a new user story, the team asks, “Is this user story A most similar to this past user story B or this past user story C?”
Learn other essential Scrum terms.