How to understand that planning a sprint went well?
You can measure intuitively, or you can use a checklist. I missed such a check list. And I came up with it for myself.
I share. I collected from everywhere: from books, conversations, scrum guide, my own observations. It can be supplemented at its discretion.
')
Text checklist
Held at the beginning of the sprint?
Does it always start and end on time?
Does it last no more than 8 hours for a monthly sprint and faster if the sprint is shorter?
Was the product backlog up to the beginning of the planning updated and were the backlog elements prioritized?
Backlog elements are evaluated by the development team?
Is the entire scrum team present (product owner, development team, scrum master)?
The number of backlog elements taken into the sprint is determined by the development team?
Does the number of backlog elements taken in the sprint match the capabilities of the team?
Does every team member have access to a sprint backlog?
Does every element of a backlog taken in a sprint have a score (in hours, counter points, etc.)?
By taking the backlog elements in the sprint, each member of the scrum team can tell what kind of element it is, why we create it, what value it carries, how it will be possible to understand what this element is made of, what acceptance criteria are, how to measure the value?
Each member of the development team can answer how, with what tools and practices will the sprint goal be achieved?
Does the development team have all the resources to achieve the goal of the sprint?
Every backlog element taken in the sprint is decomposed into tasks?
Are spawned backlog elements visualized?
Planning takes place without the help of a scrum master?
Is the scrum team going to plan independently?
After planning, each member of the scrum team can answer what he and his team will do during the sprint, what is the goal of the sprint, what value will they bring at the end of the sprint, what will be included in the increment at the end of the sprint?