M. Cohn. Addison-Wesley Signature Series (Beck) Addison-Wesley, Boston, (2004)
Abstract
The best way to build software that meets users' needs is to begin with 'user stories': simple, clear, brief descriptions of functionality that will be valuable to real users. This book provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing.
%0 Book
%1 Cohn04
%A Cohn, Mike
%B Addison-Wesley Signature Series (Beck)
%C Boston
%D 2004
%I Addison-Wesley
%K -shelf 02041 103 8book agile development engineering requirements software
%T User Stories Applied
%X The best way to build software that meets users' needs is to begin with 'user stories': simple, clear, brief descriptions of functionality that will be valuable to real users. This book provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing.
%@ 978-0-321-20568-1
@book{Cohn04,
__markedentry = {[flint:]},
abstract = {The best way to build software that meets users' needs is to begin with 'user stories': simple, clear, brief descriptions of functionality that will be valuable to real users. This book provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing.},
added-at = {2020-01-12T16:36:44.000+0100},
address = {Boston},
author = {Cohn, Mike},
biburl = {https://www.bibsonomy.org/bibtex/2d38acc3b6bb37031f34625385df3df9f/flint63},
file = {copy:200x/4/Cohn04.pdf:PDF;shop:http\://www.informit.com/title/9780321205681:text/html;archive:https\://www.safaribooksonline.com/library/view/user-stories-applied/0321205685/:text/html},
gender = {sm},
interhash = {72c84fd1cc36e33ddb3c34a9e4f8d3d4},
intrahash = {d38acc3b6bb37031f34625385df3df9f},
isbn = {978-0-321-20568-1},
keywords = {-shelf 02041 103 8book agile development engineering requirements software},
owner = {flint},
pagetotal = {286},
publisher = {Addison-Wesley},
referencetype = {book},
series = {Addison-Wesley Signature Series (Beck)},
subtitle = {For Agile Software Development},
timestamp = {2020-01-12T16:36:44.000+0100},
title = {User Stories Applied},
x.asin = {0321205685},
x.sortdate = {2004-03},
year = 2004
}