Guest Book Review: “User Stories Applied: For Agile Software Development” by Mike Cohn

by Jason Brett

As a <type of user> I want <some goal> so that <some reason>.

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.

I’m personally new to writing user stories, so I dove into Cohn’s book from a relatively fresh perspective, and found the entire book highly digestible. Mr. Cohn makes no assumptions about the readers level of expertise or familiarity with Agile methods. At the same time, he writes in a way that gives the reader credit for being intelligent and purposeful.

The book is broken into 3 parts:

Part 1 covers the basics of user stories and so much more. Cohn goes into a well paced discussion of the roles of each member of the agile team at each step of the process. Not only does he dissect the stories themselves, commenting on size and scope of stories, but Cohn pays a great deal of attention to cataloging and working with an appropriate variety of user roles, working with user proxies, acceptance tests, and an exceedingly valuable chapter discussing guidelines of good stories.

Part 2 continues the examination of the user story from the perspective of estimating and planning, stepping deftly from release to iteration, taking care to discuss monitoring and measurement of the release and iteration’s progress.

Finally, in Part 3, the Cohn ties everything together with an in-depth example and a well organized discussion of a variety of topics that naturally emerge in a business environment when applying user stories to an agile development framework. He spends a chapter specifically on user stories with Scrum, and another excellent chapter on “A Catalog of Story Smells.” This chapter provides a great reality check for anyone trying to detect and deal with potential team challenges when user stories may seem to be at the center of the discussion.

What stands out to me most about “User Stories Applied: For Agile Software Development” is not only it’s apparent status as the definitive work on User Stories, but it’s effective introduction to Agile software development from the Product Management perspective. This is a book that I think exceeds its purpose in that regard.

I read this book as an experienced product manager who is new to Agile and Scrum. It has been an invaluable resource to me in that role. What I appreciate even more about Cohn’s work is that after reviewing the table of contents for this review, I can see myself re-reading the book annually (for at least for the next couple of years) and gleaning new insights to help strengthen my process and products.

No matter what your role in an Agile organization, be it product manager, product owner, scrum master or marketing manager, I suspect this book will provide significant insights into your company’s development process that can do nothing but serve you well.

Jason Brett is a Product Manager at Silverpop Systems, Inc, Founder of ProductCamp Atlanta, and currently sits on the board of the TAG Product Management Society. Jason should blog at his own website http://www.jasonbrett.me, but rarely does. You can, however, follow him at http://www.twitter.com/jbrett. Be sure and leave an @ reply to say hi!

If you enjoyed this post, please leave a comment or subscribe to the feed to receive future updates. You can also follow me on Twitter. Tell other people about this post.


Related Posts:

  • The Top Product Management Blogs 2012
  • One Good Release
  • Product Management Is...
    • Pingback: Tweets that mention Guest Book Review: “User Stories Applied: For Agile Software Development” by Mike Cohn » Strategic Product Manager -- Topsy.com

    • Pingback: Guest Book Review: “User Stories Applied: For Agile Software … | Review Gallery

    • Pingback: Guest Book Review: “User Stories Applied: For Agile Software … Software Rss

    • Pingback: Guest Book Review: “User Stories Applied: For Agile Software … | Pulplit Magazine

    • http://twitter.com/runaroo Runaroo

      Hi, I'm a subscriber of your blog here for a few weeks, but have read through your archives and am learning alot.

      By coincidence, I just read the first 4 chapters of the book today in preparation for an interview (prod. manager role). I see it being straightforward for enhancements. However, for sites being built from the ground up, it could get pretty tricky no? In my experience, it is the Information Architects that put the site together as far as flows, wireframes, user experience, front-end.. that kind of stuff. The first 4 chapters didn't mention any of this, only the upfront IA activities of defining user roles and user personas. Maybe I'm missing something (I saw that the later chapters delved into the development aspects of Agile), but this I think is a big part of tying the entire site together. How would customers be properly informed of coming up with user-stories and prioritizing them w/o those IA steps I mentioned? I've never practiced Agile, so am very curious how IA roles tie in here because alot of times, Product Managers also play the IA part on projects (depending on their exp.). Anyways, I think the book is good, but I feel it simplifies the usually very important steps prior to the coming up with the user stories. If I can be convinced of this, then I can see how Agile can be implemented in organizations where the IA role is considered important.

    • http://www.strategicproductmanager.com/ Stewart Rogers

      I suspect the Information Architect role is important in most organizations. However, in most organizations the responsibilities of the IA role is assumed by other team members and not one person. It is also quite possible that for some the IA tasks that you listed above are performed outside of the Agile sprint or as a sprint itself. If the tasks are important the team will do them.

    • http://www.modularhomesprices.org/modular-home-floor-plans/ Modular home floor plans

      Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.

    • http://www.modularhomesprices.org/modular-home-floor-plans/ Modular home floor plans

      Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.

    • http://www.modularhomesprices.org/modular-home-floor-plans/ Modular home floor plans

      Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.

    • http://www.modularhomesnetwork.com/ Modular Homes

      Awesome, Thanks! I was looking for this sort of thing.

    • http://www.findprefab.com Prefab Home

      Thank you for taking the time to create and maintain this…never easy when you’re busy.

    • http://www.hdactioncamera.com.au/ gopro

      thanks for sharing..