Workshop 2 - Agile Requirements - building and maintaining a Product Backlog The place for Agile Requirements in Scrum is the Product Backlog. What makes a good Product Backlog and how do you build it? In this workshop we will follow the Product Owners work in selecting items for the Product Backlog, and the following collaboration between Product Owner, Scrum Team and other stakeholders in order to prepare the Product Backlog Items for Sprint (iteration) planning. We will cover techniques for selecting and organizing market input and product ideas with the overall goal to build a good Product Backlog. Other techniques will focus on how to describe the Product Backlog Items in a useful way for both Product Owner and Scrum Team. Through exercises and discussions we will experience what the different agile requirement techniques mean to communication, planning, and testability. For example: what is best for communication - Feature Lists or User Stories? Or: what makes the best input for testing - User Stories or Use Cases? Knowing the tradeoffs and pitfalls will help you building the most effective Product Backlog for your project. Outline - Sources for Product Backlog input - Ideas attractiveness evaluation - Product Life Cycle - Boston Matrix - Value Methods - Product Backlog Iceberg - Product Backlog Item as feature, user story, or use case? - Product Backlog Item form - consequence for estimation, ordering, planning, and testing Back