Prioritizing user stories: using value to users as a key criteriaSophie Freiermuth
schedule 2 years agoSold Out!
Product development in agile is always at risk of favouring velocity and developer's skills.
Favouring velocity means that when it's time to select stories, the team will elect to do many short stories to keep velocity on the rise, or stable.
Favouring skills mean that easy implementation may be selected, or sometimes tricky solutions which will give the developper the satisfaction of solving a difficult problem.
The outcome of the story's execution and value to users is an important criteria, and I'd like to introduce you in this session to a technique that helps prioritize against two sets of criteria: technical difficulty and value to users.
Using Personas, a tool from product design which I will explain, and a simple grid, this technique makes prioritization incredibly easy - which then enables the team to focus on getting stories done, rather than figuring out which stories.