In the third class of the Scrum course, we are going to see the theoretical background of what the Product Backlog or Product Backlog is.
This is where what our project will ultimately be is condensed. It begins with a definition of it as a list of User Stories, for this, we envision how to write these, what elements they must contain and what is the completion of each one of them.
In order to optimize how to write them, Jeff Patton’s User Story Mapping technique is explained with an example. Some examples of User Stories are viewed and the degrees of weight and estimation are analyzed. Let’s go there!
As we can see, the summary is the structure that the Prodcut Backlog could have as rows of a spreadsheet with each of the columns the elements that we have explained.
We move on to the next lesson where we translate it into a Google Doc and we will begin to see how from User Stories we move on to Development Tasks.
As always, if you have any doubts or questions, you can send them through the subscriber Intranet form. See you in the next lesson! 🙂
Remember that if you will have access to everybody the courses and you can also enjoy everything from .
Facebook Comments
Disqus