Agile Product Management: User Stories: How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum

by Paul VII

Thank you and congratulations on taking this class, “User How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum”.
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 give you best practices for working with user stories within agile scrum. In this class, you will
•What User Stories are and why they are so powerful for capturing requirements in complex projects
•Feel confident in writing user stories for any project
•Understand what a Requirements Spec is and Why they are less flexible than a Product Backlog built with Agile User Stories
•Explain what The Three Rs rule, Acceptance Criteria, the INVEST Principle, the Three Cs principle and Edge Cases are and how they will make you a better user story writer or agile practitioner
•Understand how and when to split and amalgamate stories
•Learn techniques to help you to split user stories when working in the real world
•Understand the difference between Epics and Themes and when each is used
•Learn who is responsible for writing user stories in agile and scrum
So let’s get started and let me teach you how to improve product backlog management.





Agile Product
User
How to Capture Requirements for Agile Product Management and Business Analysis with Scrum1
Introduction
SECTION 1: The World Before User Stories (why do we need user stories anyway)
The Traditional Requirements Documents
Intro to Scrum and The Birth of User Stories
What is Agile Scrum?
Scrum Theory
Product Backlog
SECTION 2: User Story Principles
The INVEST Principle
The Three Cs Formula
SECTION 3: User Story basics (capturing a requirement)
How to write a User Story Description (using The Three Rs)
Who writes user stories?
User Stories – The Three Rs
How to write Acceptance Criteria (capturing the detail and any edge cases)
Acceptance Criteria
SECTION 4: Epics and Themes (capturing large or vague requirements)
What is an Epic?
What is a Theme?
When to split user stories
How to split User stories
Example Backlog
Final Words
Conclusion
Free Scrum Ebook
Preview of ‘The Scrum Master Mega Pack’
Check Out My Other Books

Genres: Business

48 pages, Kindle Edition

Published July 7, 2016

About the author

Paul VII is not only an author but a certified scrum master with experience in international blue chip companies dating back to 1999. That experience includes leading projects for the BBC, General Electric, Oracle, BSkyB, HiT Entertainment (responsible for Angelina Ballerina, Bob the builder and other titles that you love watching with your kids or siblings but won't admit to) and Razorfish. These roles have all involved leadership on a wealth of mobile, internet TV and web software projects. He has played the role of portfolio manager, scrum master and in the earlier years, of team lead and technical lead. He has had the privilege of running projects and rolling out working practices in market leading organisations from start to finish.

Reviews

[Bill Lenoir · Rating 2 out of 5]

It's like this book was written with a bad speech-to-text translator. Even if you can follow along with the disjointed narrative, it's not teaching much that's new.

[Avinash · Rating 4 out of 5]

Clean and crisp.

Quick and crisp way to revise concepts on user stories. This is not for beginners. The reader is expected to have some prior knowledge of user stories.

[Michael O'Flaherty · Rating 5 out of 5]

Good Overview

Not a bad overview. Quick read. I don't know if English is the author's primary language, but the verbiage can be a little rough and wordy in spots. However, as in all my evals, if I learned something, that can cover a multitude of grammatical errors. I am glad I read it.

[Fred Fanning · Rating 4 out of 5]

This is a good book that provides the basics needed to develop effective user stories to be used in Scrum. I really liked the way the information is structured for easy referral long after being read.

[Liz Hyde · Rating 3 out of 5]

A quick read with some good tips but it didn't have a lot of new material for me. The examples were helpful but I wish there were more of them throughout the book.

[M · Rating 3 out of 5]

This book needs an editor. There were many mistakes that could have been caught by a proofreader. You get what you pay for though. This was a free book on Amazon. :-)