Mon premier blog

User Stories Applied: For Agile Software Development Mike Cohn
Publisher: Addison-Wesley Professional

Cohn, Mike (2005), Agile Estimating and Planning, Prentice Hall 5. Whether you are new to story-driven software development or have been managing products or development with user stories for a decade, “User Stories Applied: For Agile Software Development” (Mike Cohn) is a great read. Some BAs are being The format you describe for writing user stories is the same one I found in Mike Cohn's book, “User Stories Applied for Agile Software Development”, Pearson Education, 2004. I've started reading this book and so far, so good. User stories have been promoted by the iterative and agile software development approaches as a quick way to elicit and document user requirements. Not many use the term "implied requirement" now, with a few exceptions such as Jim Coplien and Neil Harrison in their *Organizational Patterns of Agile Software Development*, which reproduces Cunningham's pattern.[4] "User story" is the more Mike Cohn echoes this sentiment in *User Stories Applied*: "Rather than writing all these details as stories, the better approach is for the development team and the customer to discuss these details. Agile Software Development targets rapid delivery of solutions with ongoing involvement of customer. As I hear more and more BAs talking about user stories I feel the need to begin a dialogue on our blog. Cohn, Mike (2004), User Stories Applied For Agile Software Development, Addison Wesley 4. Mike Cohn, User stories applied: For Agile Software Development, Addison Wesley, New York, 2004. User Stories Applied for Agile Software Development by Mike Cohn (ISBN: 0-3210-20568-5).