Summary: Agile development teams that struggle to keep track of UX work in the product backlog can utilize a separate backlog for UX. This method can help siloed teams where UX and development aren't in direct communication. Separate UX backlogs do have pros and cons, which are discussed here.
Three different backlog models enable teams to keep track of UX work in their Agile processes. Each model comes with pros and cons.
Video Author
Rachel Krause is a User Experience Specialist with Nielsen Norman Group. Her areas of expertise include storytelling, UX in agile, design thinking, scaling design, and UX leadership. She has also planned and conducted research on careers, UX maturity, and intranets for clients and practitioners in numerous industries.
