• Agile Product Management: User Stories

  • How to Capture Requirements for Agile Product Management and Business Analysis with Scrum
  • By: Paul VII
  • Narrated by: Randal Schaffer
  • Length: 55 mins
  • 4.3 out of 5 stars (39 ratings)

Prime logo Prime members: New to Audible?
Get 2 free audiobooks during trial.
Pick 1 audiobook a month from our unmatched collection.
Listen all you want to thousands of included audiobooks, Originals, and podcasts.
Access exclusive sales and deals.
Premium Plus auto-renews for $14.95/mo after 30 days. Cancel anytime.
Agile Product Management: User Stories  By  cover art

Agile Product Management: User Stories

By: Paul VII
Narrated by: Randal Schaffer
Try for $0.00

$14.95/month after 30 days. Cancel anytime.

Buy for $5.72

Buy for $5.72

Pay using card ending in
By confirming your purchase, you agree to Audible's Conditions of Use and Amazon's Privacy Notice. Taxes where applicable.

Publisher's summary

In this class you will be given proven methods to create, maintain, and manage your requirements using user stories as part of an agile scrum team. I know you will get value from this class, as it gives you a full introduction to the concept of agile user stories for managing product requirements. I then walk you step by step through everything involved in managing requirements using user stories, including writing, combining, and splitting complex user stories. Following this, I give you a complete overview of epics and themes and how they can be used to capture and group complex requirements in any team or business. Along the way I give you plenty of examples and best practices for working with user stories within agile scrum. In this class you will learn:

  • What user stories are and why they are so powerful for capturing requirements in complex projects
  • How to feel confident in writing user stories for any project
  • How to understand what requirements specs are and why they are less flexible than a product backlog built with agile user stories
  • How to explain the three Rs rule, acceptance criteria, the INVEST principle, the three Cs principle, and edge cases and how they will make you a better user story writer or agile practitioner
  • How and when to split and amalgamate stories
  • Techniques to help you to split user stories when working in the real world

©2016 Pashun Consulting Ltd. (P)2016 Pashun Consulting Ltd.

What listeners say about Agile Product Management: User Stories

Average customer ratings
Overall
  • 4.5 out of 5 stars
  • 5 Stars
    21
  • 4 Stars
    11
  • 3 Stars
    4
  • 2 Stars
    2
  • 1 Stars
    1
Performance
  • 4.5 out of 5 stars
  • 5 Stars
    20
  • 4 Stars
    8
  • 3 Stars
    4
  • 2 Stars
    1
  • 1 Stars
    1
Story
  • 4 out of 5 stars
  • 5 Stars
    19
  • 4 Stars
    8
  • 3 Stars
    3
  • 2 Stars
    3
  • 1 Stars
    1

Reviews - Please select the tabs below to change the source of reviews.

Sort by:
Filter by:
  • Overall
    2 out of 5 stars
  • Performance
    2 out of 5 stars
  • Story
    2 out of 5 stars
  • K.
  • 02-05-19

Not focused on user story development

The title lends me to think the main focus is user stories, but it's not. It only touched on high level concepts with no real value in my opinion. I didn't need scrum explained I needed more thoughtful analysis of the actual thought process methodology of writing user stories effectively. The user story info started at ch 14, and was Maybe 10 mins most.

Something went wrong. Please try again in a few minutes.

You voted on this review!

You reported this review!

1 person found this helpful

  • Overall
    4 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Chapter Titles Needed

In reviewing this material after the first listen, it would have been most helpful to see specific chapter titles or detailed subject labels.

Something went wrong. Please try again in a few minutes.

You voted on this review!

You reported this review!