Many organisations are struggling to setup outcome based Product Backlog for their teams, they were stuck in output or scope based backlogs before and kept that behavior. Even though scope isn’t a bad thing, understanding its link to business outcomes and what assumptions are behind is (to me) better.
I do address this working with Product Owners in organizations we support adopting LeSS (Huge) and experimented a lot. When the LeSS Meetup group in Warsaw was looking for an expert level talk I considered this a good topic and went for it, below the result of sharing some good practices / experiments that I find very useful in a Large-Scale Scrum environment. Enjoy!
Update August 28th, 2020: I redid the outcome based backlogs talk for LeSS NY community and made sure the prerequisites to get useful business discussions in (at least) review sessions are known as well. There is no use to apply the techniques in the talk when some of those are not setup to a certain level.