Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia. The Scrum Guide has a lot to say about the Product Backlog, and rightly so. It's pivotal to everything a Scrum Team does. But one thing the Scrum Guide doesn't tell you, is how you create a Product Backlog.
So, here's one way you can do exactly that. But the Scrum Guide makes no mention of when, or how, to create the Product Backlog. It's up to you to decide what technique you'd like to use. There are a number of techniques that you can use to create a Product Backlog.
I'm going to share one that works well for me and is in common use. Schedule a one-day meeting. Invite the Scrum Team s involved and some stakeholders. It may be a good idea to split the meeting over two days so people don't become fatigued. The task vad är backlog i scrum is for attendees to think of functionality needed for the Product.
We all know that you cannot think of everything up-front but there comes a time where further pondering is of little value. So, ask the attendees for a time-box. One hour often works well and can easily elicit ideas. With the time-box started, ask the attendees to think about the functionality for the Product.
Once they have an idea, write it on a single Index Card and stick it up on a work area, such as a wall. The next task is to remove duplicate ideas. As before, set a time-box. Twenty minutes is a good starting point. What I like about this part of the technique is that, if any cliques had formed in the first part of the meeting, they were all brought together in the search for duplicate ideas.
Agree another time-box and ask the attendees to select the top twenty ideas. This may prove difficult. Stakeholders in particular can get quite passionate at this stage. What's important here are the discussions.