Here is an article for those who don’t yet know the term product backlog and to gather all the articles around this one that have already appeared on this blog.
Product backlog definition
The backlog of a product is the set of needs collected to create the desired product. If we thinks of user-stories right away, it can also concern technical items, spikes or even bugs.
As we are in agile methods, we must understand that the scope of the backlog is variable; we can see elements appear and others disappear throughout the product development.
Indeed, contrary to a specification, the backlog lives and evolves constantly. Moreover, each of the needs that constitute it are detailed only at the last moment, just before the developments. At startup we have simple titles to know what needs we have but no details on them
It is essential to properly manage our product backlog. Knowing that the scope of it is variable, we have to know how to manage it well. Fortunately, I realized an article on this subject that you can read:
In general, we try to deliver maximum value at the beginning of the project to get the most important feedback as soon as possible. It will only be admitted that there will be a running-in phase of the team of a few sprints. Here is what the value curve should look like throughout the project:
You can use different prioritization methods like the MoSCow method (to macro level) and the ROI = Business Value / story point for all the items.
And our items in the backlog?
Here are some articles that I can advise you about items that we can find in our backlog.
What is an Epic in Agile?
Agile user story
The 3C model for the social aspect of user-stories
Let’s work on our features with MMF
Nonfunctional Requirements (NFR) in Scrum?
Making user-stories of different storyotype
Conclusion product backlog
I sincerely hope that this notion of backlog has no more secrets for you thanks to this complete article on the subject. Feel free to write your definition of the backlog on the comments area.