- Your project backlog/board should at any time represent the team’s current understanding of the project or product and its objectives.
- The backlog is understood as a dynamic body of information that changes and evolves as your project changes and evolves.
To ensure that the backlog contains the appropriate items, that they are prioritized, and ready for implementation teams should engage in the following activities on a regularly scheduled and as needed basis:
- Removing user stories that are no longer relevant
- Creating new user stories in response to newly discovered needs
- Re-assessing the relative priority of stories
- Splitting high priority user stories that are too large for one person to work on.
- Adding detail to user stories so that team members can start implementation.