Mon premier blog

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

OK, I know what you're thinking geek reads tech book; big surprise. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). It is a short, practical explanation of how to plan, estimate, and execute an agile project with user stories. I've been using “User Stories Applied: For Agile Software Development”, by Mike Cohn, to help plan the assessment. Cohn, Mike (2005), Agile Estimating and Planning, Prentice Hall 5. User Stories Applied - For Agile Software Development Written by Mike Cohn January 2006 Addison-Wesley ISBN: 0-321-20568-5. That's why I'm glad I discovered User Stories Applied: For Agile Software Development by Mike Cohn. The concept of user stories has its roots as one of the main tenets of Extreme Programming. Cohn, Mike (2004), User Stories Applied For Agile Software Development, Addison Wesley 4. 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. User Stories Applied for Agile Software Development. A good on-line introduction to user stories can be found at: Writing Good User Stories. Here are some examples of potential user stories for the Aquifer American Social History Online portal:.