US-102 – User Story Workshop
Agile User Stores is a one-day workshop to introduce User Stories as a technique for understanding product requirements and how to leverage User Stories for Agile product development. We will work with several techniques for identifying and capturing User Stories to build a shared understanding of the needs of the users and the features of our product. This course provides hands-on experience capturing (writing) User Stories, User Story mapping, defining Acceptance Criteria, and understanding the lifecycle of a Story in an Agile product development framework.
Product Owners, Analysts, Product Managers, and Product Stakeholders who are starting on the first agile project or who have some experience on an Agile project and would like to expand their knowledge and confidence with User Stories to guide product development.
- Understand the practices, principles, and values articulated in the Agile Manifesto.
- Build skills in identifying and capturing stories and building a product backlog.
- Gain experience writing “good” user stories and gain a deep understanding of the purpose and use of user stories throughout the product development lifecycle.
- Learn how to create a story map to identify and capture product requirements.
- Learn strategies for organizing and prioritizing the product backlog.
Course Topics & Outline
- Historical perspective on software product requirements – how did we get here?
- Introduction to agile concepts
- Introduction to the Scrum Framework and Product Backlog
- Effectively communicating product ideas and requirements
- From vision to capabilities
- The life cycle of a story – with just enough and just in-time product definition
- The user story format
- Types of users & Personas
- Telling (and writing) good stories
- Story Writing Workshops
- Creating a User Story Map
- Acceptance Criteria
- Guided Exercise: Capturing User Stories
- Definition of Done
- Definition of Ready
- Structure and Management of the Product Backlog
- Breaking stories apart – right-sizing stories with perspectives and patterns
- Addressing non-functional requirements with stories
- Backlog Prioritization and Organization
- Simulation: Building a product backlog – user story mapping, user story capture, backlog creation and organization for our simulated product.
During the simulation, participants will form into product discovery teams and use story mapping, product analysis and story capture, and workflow process mapping to identify and capture initial user stories. The teams will then organize the stories into an ordered product backlog, progressively elaborate the stories – looking at patterns for decomposing large stories into right sized stories, and refine the highest priority stories to a point where they have a shared understanding of the story and it meets the definition of ready.