In the fourth class of the scrum course we go into detail about the Planning Poker technique, where we see the scoring flow of the entire team.
Once we have compiled some user stories, it is necessary to provide them with a value, a Story score with which later, based on the Priority of the PO and the capacity of the Team, we can determine what we include in a Sprint or not.
We are going to teach some concepts and strategies so that this is done in a coherent way. In addition, and as if that were not enough, we will be able to apply some techniques to validate the estimates, which are called Triangulation Techniques.
We are now going to get down to work and capture in Google Drive and Google Docs what would be the management of the Project with Scrum and some of the User History of the Login Process to our MemberShip Site in the corresponding document in the PB (Product) folder. BackLog).
we invite you to (based on the document that I have shared with you) carry out work similar to the one I have done in a spreadsheet similar to the one I am showing you.
We move on to the next lesson where we review the strategies to determine what finally goes to a Sprint, the division of User Story in Tasks and we will build the first Sprint Backlog dumping it into Trello.
As always, you can send your questions through the contact form of the subscriber Intranet. 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