From the course: Agile at Work: Planning with Agile User Stories

Unlock the full course today

Join today to access over 24,400 courses taught by industry experts.

Input to backlog prioritization and planning

Input to backlog prioritization and planning

From the course: Agile at Work: Planning with Agile User Stories

Start my 1-month free trial Buy for my team

Input to backlog prioritization and planning

“

- What should we implement next? That is a question answered by the product owner of an agile team. The product owner is responsible for the order of the user and technical stories on the backlog. They order based on their determination of what the most important stories are at a point in time. Prioritization enables flexibility and decisions on what to do next. Lower priority stories can wait to have more time and effort investment as the team gets validated learnings on the stories implemented prior. There should be regular movement in the product backlog. Once it's populated by the stories identified for the project and the team begins implementing stories, there should be perpetual action. What should you see? Stories are increasing in priority. Stories are decreasing in priority. Some new stories were added, epics, large stories split into two or more stories. Stories may be removed from the backlog and stories at the top have been discussed, acceptance criteria written and are…

Contents