Free shipping on all orders in the USA!

Agile Product Management: User Stories: How to Capture Requirements for Agile Product Management and Business Analysis with Scrum (scrum, scrum ma

ISBN: 9781535194075
Publisher: CreateSpace Independent Publishing Platform
Publication Date: 2016-07-10
Number of pages: 70
  • Sale
  • Regular price $31.96

Any used item that originally included an accessory such as an access code, one time use worksheet, cd or dvd, or other one time use accessories may not be guaranteed to be included or valid. By purchasing this item you acknowledge the above statement.

Description


Introduction

Thank you and congratulations on taking this class, “User Stories: 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 learn:
• 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

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

Scroll Up To The Top Of The Page And Click The Orange "Buy Now" or "Read For Free" Icon On The Right Side!

Customer Reviews


MORE FROM THIS COLLECTION