Toolkit
Sprint Planning Prompts
Net Positive Sprint Kit - Part 3 of 9
Part 3 of 9 · Sprint Planning
Use this tool
- During backlog refinement or sprint planning
- Early in the scoping process for a feature or product
- When prioritising work for a sprint
You'll get
- A short list of sustainability and impact questions to ask alongside usual planning discussions
- A quick way to identify high-impact decisions before they are locked in
- A record of stories or features that may need further review
Getting started
Choose three to five prompts from the list below that are relevant to the work you are planning. Add them to your backlog refinement or sprint planning session, and capture any actions, tags, or story changes that result. Feed those into your backlog or link them to Impact Tags for follow-up.
The promptsAsk these questions about each story, epic, or feature
- What happens if this becomes the default for many users over time?
- Could this feature make it easier for users to choose a lower-impact option in the real world (e.g. shared transport, local pickup, reduced travel)?
- Could the design make more sustainable behaviour easier or more attractive?
- Does this feature work equally well for users with different abilities, devices, or connection speeds?
- Could we meet this need by re-using or adapting something we already have?
- Is this solving a clear, current need, or is it adding unused complexity?
- Could we design this to work with less data, less energy, or fewer steps?
- If we had to disclose the environmental cost of this feature to users, would we build it the same way?
- Are we making assumptions about user context that could exclude certain groups?
- If this feature uses AI, have we considered the inference cost at the scale of expected usage, and whether a lighter-weight approach would meet the same need?
- Are we introducing a third-party service or dependency whose environmental or social practices we have assessed?
Tips for using prompts well
- Keep the session moving. Not every prompt will apply to every story.
- Use prompts as conversation starters, not as rigid criteria.
- Rotate which prompts you use each sprint to keep the thinking fresh.
- If a prompt surfaces a big unknown, tag the story and investigate later rather than derailing the session.
- Check for trade-offs: changes that reduce technical impact should not compromise accessibility, security, or core functionality.
Example
A travel product team used the prompts during sprint planning and asked whether a new search results page could surface lower-carbon travel options more prominently. This led to a design change where train options appeared above flights for journeys under four hours.
Output
Stories or features refined with impact in mind. A backlog with potential high-impact items tagged for follow-up.
Measurement & Validation
Track how many backlog items are tagged for follow-up on impact in a sprint. For shipped features, compare related performance metrics (e.g. page weight, API calls) before and after.
Want help running a net positive sprint?
We facilitate net positive sprints for teams who want to embed sustainability into their digital delivery.