According to the Scrum Guide, we know that the 'Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.' We also know that product backlogs evolve, that requirements never stop changing, and that the product and the backlog that guides its ongoing evolution should be responsive to market dynamics. What Scrum doesn't define is how a Scrum Product Owner and a Scrum Team can identify customer and stakeholder requirements at scale. This webinar explored frameworks that Product Owners can leverage to identify customer and stakeholder requirements, and ensure that these are shared effectively across multiple Scrum Teams.
Get the latest resources from Scrum Alliance delivered straight to your inbox
Subscribe