Refactoring User Stories

User Stories make the team focus on how the product will behave rather than how it will be built.

A story is always something that the business values. Refactoring is never an isolated story or problem.

Code cleanup is never a story.[¹]

Think of a story as a thin vertical slice through the horizontal layers of the system.

Quantifying the business value can be informal. Some teams might use high/medium/low as their business value scale; others might try to use a ten-point scale.

An iteration should contain about the same number of stories as there are developers on the team.

–

[1]: Robert C. Martin (2019): Clean Agile(https://www.amazon.com/Clean-Agile-Basics-Robert-Martin/dp/0135781868)