In this article author describes three different backlog models which enable teams to keep track of UX work in their Agile processes. Each model comes with pros and cons. By Rachel Krause.
There is no definitive rulebook when it comes to Agile backlogs – every team may structure its backlog differently. At its core, this is a good thing: every team has its own way of working so a one-size-fits-all process isn’t practical.
The article then goes over:
- Backlogs in Agile
- Backlog structure
- Unified backlog: Explicit UX and development items in the same backlog
- Task-Based unified backlog: Role-Based work expressed as tasks within backlog items
- Multiple Backlogs
The great thing about backlogs is that you’re able and required to be flexible. Don’t be afraid to mix and match different methods until you find something that works for your team.
[Read More]