The Product Backlog, sometimes called simply backlog, is the first document to be implemented in a Scrum project. This replaces traditional specifications in favor of "User Stories", which will be adjusted as the project progresses: this is agility.
... What did you say ?
What does it look like ? 🤔
Look at those resources below to understand how a basic Product Backlog looks like :
Focus on priorities is the key of success ! 🏅
In order to have a useful backlog, it's important to identify what you will to develop first. Your top priority is to get a "Minimum Viable Product" (MVP), i.e. a version of your product that contains only its most essential features. To conclude, there are many methodologies. Look at this example below about MoSCoW methodologie :
Did you understand everything in this video ? Let's see this ! Based on what you just watched, with your team, apply the MoSCoW method to this "real life case" from this Workshop How to apply Scrum in real life? When you're done, show your teacher how you've divided items into the different columns.
What am I supposed to do ? 🧐
With everyone else on your team, write your project's product backlog using prioritization.
A few points that need your attention:
- Global vision: student management application
- Personas: student, trainer, Campus Manager
- Main themes: Home, Promotion, Students, Admin ...
- Writing the first User Stories (INVEST method)
eg a CRUD = 5 US (list all, show, create, update, delete) - Choice of priorities with MoSCoW
At the end, show to your trainer how your product backlog looks like. Let's see if he has any advice for you regarding:
- How you wrote your User Stories, "As a user, I want to do something in order to reach this purpose".
Be careful, the common mistake is to summarize too much, or to write 2 user stories in one. If you wrote "and" or "or" in your User Story, you are certainly on the wrong track. - How you prioritize tasks. Are you sure this feature is more important than this one ?