Plan for success: advice and architecture during the design phase.
Expert Sitecore development and implementation.
Continuous improvements and site maintenance.
Continuous integration, site monitoring, and trouble-free deployments.
Assess an existing implementation to find the top opportunities for improvement.
Get Sitecore's latest and greatest marketing powers.
Ensure an error-free site before—and after—launch.
Easily move content, templates, workflows, and more to Sitecore.
Create experience-focused commerce with Sitecore.
Maximize Sitecore's advanced market capabilities.
Please reach out with any questions or to schedule a free consultation Contact Us
Digital marketing technology, strategic insights, & technical advice.
Best Practices, tips, and advice for digital marketers & technologists.
When applying Scrum in our projects, one of our core ceremonies (aka ‘meetings’) is backlog refinement. In this ceremony, we prepare the backlog for the upcoming sprint planning session. We order stories by priority or dependencies. Additionally, we estimate the time required to complete each story, which saves time in the sprint planning session.
As with all Scrum ceremonies, it’s worth being mindful of the best way to make backlog refinement sessions as efficient and effective as possible. With that in mind, there are four top objectives we like to get from our backlog refinement sessions:
In more detail...
This is the basic goal of backlog refinement. The outcome of the meeting is an ordered list of stories (based on priority and dependencies) ready to be used in the next sprint planning. At a minimum, the requirements for the top stories should be clearly defined, along with acceptance criteria, and an estimate.
Because each story will be reviewed during this session, it’s a good time to make sure each team member understands what is required for each story. Be careful no to focus on how the story will be solved; the goal is to make sure the team understands the business requirement and the value of the story. This will be our initial team commitment for the next sprint’s work.
By having an ordered backlog with estimates — and knowing the team velocity — the team will be able to have a basic prediction on what tasks will be worked on during the following two sprints. This will help the product owner manage expectations on the business side and provide some predictability for the project.
One of the oft-overlooked items we get from the backlog refinement session are the questions we obtain from the team. The questions can be given to the product owner so the team can receive clarifications by the next backlog refinement. These answers are useful to improve the story definitions.
While these goals may seem simple, they are vital for productive backlog refinement ceremonies — and successful projects.