Moscow prioritization
I have a question regarding backlog grooming. I have completed product prioritization using MoSCOW method. I have it prioritized it as follows. I have rationalized it working with client and gathering other data.
Question: Now, I am in the sprint backlog phase (sprint planning for the next sprint) and assume that I have 3 developers. How do I create sprint backlog atleast the bare structure. Do I have to pick ONLY Must haves for sprint backlog or use 60% of MUST haves and 20% of should haves and rest 20% of could haves for grooming?
How do you go about this? Do you use some other technique? I am super confused how to go about this. OR should I get into the meeting with this information and let the development team create sprint backlog as they wish (my gut says the team will not appreciate it).
For the purposes of this question, I havent added user stories, acceptance criteria. do assume that I will be writing user stories in reality.
I have a question regarding backlog grooming. I have completed product prioritization using MoSCOW method. I have it prioritized it as follows. I have rationalized it working with client and gathering other data.
From Scrum Guide -
Product Backlog refinement is the act of adding detail, estimates, and order to items in the
Product Backlog. This is an ongoing process in which the Product Owner and the Development
Team collaborate on the details of Product Backlog items. During Product Backlog refinement,
items are reviewed and revised. The Scrum Team decides how and when refinement is done.
Refinement usually consumes no more than 10% of the capacity of the Development Team.
However, Product Backlog items can be updated at any time by the Product Owner or at the
Product Owner’s discretion.
Do you planned to have this session with your team where these requirements will be further refined to make it ready enough to be taken into Sprint ?
How do I create sprint backlog atleast the bare structure.
Why not sprint backlog is created together with team before you start the sprint?
what do you infer from this part of guide -
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast
by the Development Team about what functionality will be in the next Increment and the work
needed to deliver that functionality into a “Done” Increment.
Do I have to pick ONLY Must haves for sprint backlog or use 60% of MUST haves and 20% of should haves and rest 20% of could haves for grooming?
What do the team think about this? If all of the work they plan into their Sprint Backlog is mandatory for the Sprint Goal to be achieved, could that set them up to fail?
Going to start by saying that @Harshal Rathee and @Ian Mitchell have provide you very good advice so I'm going to skip to one thing that they didn't really mention. Your quote:
OR should I get into the meeting with this information and let the development team create sprint backlog as they wish (my gut says the team will not appreciate it).
Simply, yes. From your question I am assuming you are the Product Owner. From the Scrum Guide's section describing the Sprint Backlog
The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment.
If the Sprint Backlog "is a forecast by the Development Team" why would you, as Product Owner, be creating that backlog? And how do you know they won't appreciate being able to plan their own work based upon the information you have provided to identify the importance of each item? I have seen Product Owners do far less than you have and I would think the team would appreciate all of your efforts. At least I hope that they will.