Scrum teams get together to decide on the work items for their next sprint in the sprint planning meeting. But is that the beginning of the conversation for the upcoming sprint, or are there some things that should be done before that?
In my latest article for the TestRail blog, find out what you should be doing before your sprint planning meeting even starts so that you can help make the next sprint successful.
Prioritize the backlog
The first and most important consideration is to have a live product backlog that is up to date and prioritized with changing business needs. The product owner must have a constant eye on adding, removing, editing and updating items in the product backlog. When the time approaches to get into planning the next sprint, the product manager must bring to the table a list of the highest-value items that the team can pick from.
The product owner must spend time researching each of the features and trying to lay out in simple terms the actual need they each describe. They may use bulleted points or simple sentences to explain the feature in some detail. We see this happening mostly during or after the sprint planning meeting, but if any requirements are known before the meeting, the product owner can get a head start.
Decide on a definition of done
During a sprint planning meeting, typically the team picks what they will do within the sprint and deliver by the end of that iteration. It is imperative that they know and agree upon a definition of done that defines each user story as well as every task within that user story. Be it a development task, a test design or execution task, or a review task, everyone must concur on a common understanding of what “done” means in order to ensure a smooth delivery and no conflicts at the end of the sprint.
Groom user stories
Each user story that is brought forth for sprint planning must be groomed, expanded upon and detailed with the entire team’s knowledge and input.
When the testers, developers and the product owner sit together and discuss a new feature, many new questions may arise from the team. Questions often center around integration with existing features, how the feature may behave in specific cases, or how the behavior must be for different types of users. Special cases also form a part of the acceptance criteria that are defined within the user story to make it complete.
Whatever the questions, it is best to have them arise earlier and answer them before picking the user story. Basically, this means a conversation has to happen for each user story, so that the team can gain an understanding and decide on confirmation criteria defined and accepted by all.
These story grooming sessions should happen before the sprint planning meeting so that during the planning, the team knows exactly what is required from that feature and can give better estimates and story points based on its complexity.
Start with Design Tasks
A product owner must be on a constant lookout for user stories that may need design or research work done before beginning them. Have these stories distributed to the relevant people the sprint before to ensure that implementation will be smooth and delivery can take place on time. Continue Reading—>
<Image Credits – DigitalHRTech.com>