This video provides an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.
Introduction to Agile Requirements Traceability
To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.Read More
This talk shares product management best practices and experiences with you in hopes they will help you in your product development journey to build highly effective teams. It covers key topics including (a) working together, (b) managing and prioritizing the work, (c) customer discovery and readying stories, (d) measuring what and how we work, and […]Read More
Visualizations are a key tool that help organizations change their perspective. Though no silver bullet, mapping experiences diagrams seek to align customers’ experiences with how businesses operate. You are surely familiarly with things like customer journey maps, service blueprint, experience maps, and more.Read More