user story

Articles

Identifying and Improving Bad User Stories
A written user story is a very short narrative—a sentence or two—describing some small piece of functionality that has business value. User stories are intended to foster collaboration and communication, but writing these short narratives poorly can negate agile’s flexibility. Charles Suscheck and Andrew Fuqua explain some common failure patterns that will help you focus on the right role, value, and business functionality when writing stories.
Helping the Customer Stick to the Purpose of a User Story
I work as a tester on a development team for a financial services company. Our software manages all aspects of 401(k) retirement plans. Even though we've been practicing agile development for eight years, or maybe because of it, our customers sometimes fall into a trap. Rather than tell us the business problem they need to solve, they give us a user story with the technical implementation already all figured out.

Visit Our Other Communities

The home for software testing and QA professionals—practical advice on test automation, test management, test techniques, and more.
Where configuration management and development professionals go for answers on SCM, ALM, change management, DevOps, tools and more.