The Product Backlog is the center of any Agile product development. Without it, the team does not know what to build when. While the backlog is covered in all of the basic Agile courses, we find that teams still struggle with managing it – especially the user stories themselves. In this course we will take a deep-dive into all of the elements needed to have one single prioritized backlog to aide in successful planning and implementation.
Who Should Attend
This practical workshop is ideal for product teams, Product Owners, business analysts, and development managers who will be working with products and requirements, or who will be supporting teams and individuals who do.
This workshop is designed for participants with some previous knowledge of Agile.
- Defining User Stories
- What is a User Story?
- The Formula: Description, Benefit, Acceptance Criteria
- Ron Jeffries – The 3 Cs
- Acceptance Criteria
- Defining Acceptance Criteria
- Types of Acceptance Criteria
- Non-Functional Stories
- Reviewing the Types of PBIs
- Slicing (Splitting) Stories
- Horizontal versus Vertical Slicing
- Splitting Stories
- Define a product backlog
- Create product backlog items
- Identify the differences between themes, epics, and user stories
- Write user stories that provide a description, benefit, and acceptance criteria
- Practice Ron Jeffries’s 3 Cs
- Evaluate user stories using the INVEST method
- Develop three different types of acceptance criteria
- Utilize FURPS to address non-functional stories
- Learn the difference between horizontal and vertical slicing and the impact to product development
- Prioritize the backlog using several assessment methods
- Benchmark a user story value system
- Conduct an estimating session for developed user stories