Sprint Planning for E-commerce & Retail
A structured procedure for planning the work to be completed in an upcoming sprint cycle, selecting items from the backlog, estimating effort, and committing to a realistic sprint goal.
Purpose
To ensure the team enters each sprint with a clear, achievable goal, well-understood work items, and a shared plan for how the committed work will be delivered within the sprint timebox.
Scope
Applies to each sprint planning cycle, covering the preparation phase, the planning team sync itself, and the finalisation of the sprint backlog and sprint goal.
Prerequisites
- Groomed product or campaign backlog with prioritised items ready for selection
- Team velocity data from previous sprints for capacity-based planning
- Team availability confirmed for the upcoming sprint including any leave or external commitments
- Definition of done agreed and understood by the entire team
Includes Australian Consumer Law (ACL) compliance features, GST calculations, and product safety record management.
Step-by-Step Procedure
Review and Prepare the Backlog
Ensure the top items in the backlog are sufficiently refined, estimated, and ready to be pulled into the sprint.
- 1.1Review the top-priority backlog items to confirm they have clear acceptance criteria
- 1.2Verify that estimated effort or story points are assigned to all candidate items
- 1.3Identify any items that need further clarification from stakeholders before they can be planned
- Conduct a backlog refinement session before sprint planning to avoid spending planning time on clarification
Determine Sprint Capacity
Calculate the team available capacity for the upcoming sprint by accounting for team size, working days, planned leave, and non-campaign commitments.
- 2.1Count the available working days in the sprint for each team member
- 2.2Subtract planned leave, public holidays, and standing commitments such as training or support duties
- 2.3Calculate the total available capacity in story points or hours based on historical velocity
Conduct the Sprint Planning Team sync
Facilitate the sprint planning team sync where the team reviews the prioritised backlog, discusses each item, and selects the work they can commit to completing in the sprint.
- 3.1Present the product or campaign priorities and any specific goals for the upcoming sprint
- 3.2Walk through each candidate backlog item, discussing scope, dependencies, and implementation approach
- 3.3Allow the team to select items up to their calculated capacity, ensuring they are confident in the commitment
- 3.4Agree on the sprint goal that summarises the primary objective of the sprint
Break Down Sprint Items into Tasks
Decompose each selected backlog item into specific tasks with time estimates, making the work tangible and trackable.
- 4.1For each selected item, identify the individual tasks required for completion
- 4.2Estimate the effort for each task in hours
- 4.3Assign initial task owners based on skills and availability
Identify Dependencies and Risks
Review the selected sprint items for any dependencies on external teams, systems, or decisions that could block progress during the sprint.
- 5.1Map dependencies between sprint items and identify the critical path
- 5.2Flag any external dependencies that need to be resolved before or during the sprint
- 5.3Identify risks to the sprint commitment and agree on contingency approaches
- Front-load work on items with external dependencies to allow time for resolution if delays occur
Finalise and Communicate the Sprint Plan
Document the finalised sprint backlog, sprint goal, and any key decisions, then communicate the plan to all relevant stakeholders.
- 6.1Update the sprint board with all selected items and their tasks
- 6.2Publish the sprint goal and selected items to the wider stakeholder group
- 6.3Ensure all team members have a clear understanding of their first tasks
Quality Checkpoints
Common Mistakes to Avoid
Expected Outcomes
Percentage of sprint commitments completed by the end of the sprint, indicating how well the team plans relative to their capacity
Percentage of sprints where the agreed sprint goal is fully achieved, reflecting the team ability to deliver on their primary objective
Frequently Asked Questions
Should bug fixes be included in sprint planning?
Yes, known bugs should be prioritised alongside feature work in the backlog. They should have acceptance criteria and effort estimates like any other item. Some teams also reserve a portion of sprint capacity for unplanned bug fixes discovered during the sprint.
How do we handle items that span multiple sprints?
Large items should be broken down into smaller increments that can be completed within a single sprint. If an item truly cannot be decomposed further, plan the specific portion that can be completed this sprint and track the remainder as a separate backlog item.
How long should a sprint planning team sync last?
For a two-week sprint, sprint planning typically takes one to two hours. For longer sprints, allow proportionally more time. If planning consistently runs long, it usually indicates that backlog refinement is not being done adequately beforehand.
What if the team cannot agree on the sprint commitment?
The scrum master should facilitate discussion to understand concerns. If disagreement persists, err on the side of committing to less work rather than more. It is better to complete fewer items fully than to carry over partially completed work to the next sprint.
Want this customised for YOUR business?
We'll tailor every step to your exact operations, tools, and team structure.