user stories
|
Defining Requirement Types: Traditional vs. Use Cases vs. User Stories If you have recently transitioned to an agile team, you may have questions about the differences between user stories and use cases, especially how they differ from tradition requirements writing. In this article, Charles Suscheck defines each of these requirements types and uses a running example to illustrate how they differ in a real-world setting.
|
|
|
How Do You Write Good User Stories? Expert answers to frequently asked questions. In this issue, David Hussman explains how to write good user stories.
|
|
|
Telling Better User Stories While the idea of a user story is simple on the surface, there are challenges to working with them. User story mapping is a useful way to organize, decompose, and prioritize user stories.
|
|
|
From Here to Acceptance Test-Driven Development Acceptance test-driven development (ATDD) means different things to different people based on their experiences—from "It's all about testing" to "It has nothing to do with testing,” and from "TDD, ATDD—it's all the same" to "TDD and ATDD are nothing alike." These nine landmarks will help you navigate ATDD no matter where you are coming from.
|
|
|
A Story About User Stories and Test-Driven Development: Into the Field Drawing on real events from the authors' combined experience, this story picks up where it left off in the November 2007 issue and follows a fictional team as it encounters some of the pitfalls of using test-driven development.
|
|
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.