Transform backlog items into actionable sprint plans with accurate story point estimates, capacity calculations, and risk identification for agile teams
You are an experienced Agile Coach with fifteen years facilitating sprint planning for software teams ranging from startups to Fortune 500 companies. You specialize in helping teams estimate work accurately, plan realistic sprints, and identify risks before they derail delivery. I need help planning a sprint for my team. Our team has [TEAM_SIZE:number:2-20] developers and we run [SPRINT_LENGTH:select:1-week,2-week,3-week,4-week] sprints. Our methodology is [METHODOLOGY:select:Scrum,Kanban,Scrumban,SAFe,Custom Agile] and we work in the [DOMAIN:select:Web Development,Mobile Development,Backend/API,Data Engineering,DevOps/Infrastructure,Machine Learning,Full Stack,Enterprise Software] space. Our team's historical velocity is [VELOCITY:select:Unknown - new team,10-20 points per sprint,20-40 points per sprint,40-60 points per sprint,60-80 points per sprint,80+ points per sprint]. Here is our team availability for this sprint. Include any planned time off, holidays, meetings overhead, or reduced capacity: [TEAM_AVAILABILITY] Here are the backlog items we are considering for this sprint. Include titles, descriptions, and any existing estimates if available: [BACKLOG_ITEMS] Additional context about technical constraints, dependencies on other teams, or business priorities: [ADDITIONAL_CONTEXT?] Please provide a comprehensive sprint planning analysis that includes the following sections. First, calculate our sprint capacity. Consider the team size, sprint length, and availability information to determine how many story points or hours we can realistically commit to. Account for typical meeting overhead, code reviews, and unexpected interruptions. Second, analyze each backlog item and provide a story point estimate using the Fibonacci scale. For each item, explain your reasoning by comparing it to typical work complexity. Flag any items that seem too large and should be broken down. Third, recommend a sprint goal. This should be a clear, outcome-focused statement that describes what we will achieve, not just what we will build. Fourth, suggest which items to include in the sprint commitment. Prioritize based on business value and dependencies. Ensure the total does not exceed our calculated capacity and leave a buffer for the unexpected. Fifth, identify risks and dependencies. Call out any blockers that must be resolved before work begins, dependencies on other teams or external factors, technical risks that could cause estimates to balloon, and anything that threatens our ability to meet the sprint goal. Sixth, provide a brief sprint planning meeting agenda. Include timeboxes for each activity so the planning session stays focused and efficient. Format your response with clear headings for each section. Use tables where helpful for comparing estimates. Be direct and practical rather than theoretical.
Range: 2 - 20
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessSprint planning sets the pace for everything your team delivers in the next iteration. A weak sprint plan leads to missed commitments, scope creep, and the slow erosion of team confidence. This template produces a comprehensive sprint plan by calculating team capacity from [TEAM_AVAILABILITY], estimating [BACKLOG_ITEMS], recommending a sprint goal, and flagging risks before the first line of code is written.
You provide your team size, sprint length, methodology, and velocity along with [TEAM_AVAILABILITY] details and the [BACKLOG_ITEMS] you are considering. The AI returns story point estimates using the Fibonacci scale, a capacity calculation that accounts for meetings and interruptions, and a prioritized sprint commitment that leaves buffer for the unexpected.
For teams running full agile ceremonies, pair this with the sprint retrospective facilitator to close the improvement loop, or use the project breakdown expert to decompose epics into sprint-sized stories. Save your sprint plans in Dock Editor to build a velocity history over time.
Copy the template into ChatGPT, Claude, Gemini, or Dock Editor. Set [TEAM_SIZE], [SPRINT_LENGTH], [METHODOLOGY], [DOMAIN], and [VELOCITY] to match your current team configuration.
Fill in [TEAM_AVAILABILITY] with any PTO, holidays, or reduced capacity. Paste your [BACKLOG_ITEMS] with titles, descriptions, and any existing estimates.
Use [ADDITIONAL_CONTEXT] to note dependencies on other teams, upcoming releases, or priority shifts from stakeholders.
Check each story point estimate against the complexity reasoning provided. Verify the sprint goal is outcome-focused rather than a list of tasks.
Confirm the recommended items fit within calculated capacity. Remove items that exceed the buffer or carry unresolved blockers that could derail the sprint.
Prepare structured sprint planning agendas with capacity calculations and risk assessments before the team meeting begins.
Validate that sprint commitments are realistic by comparing proposed workload against team availability and historical velocity.
Translate business priorities into sprint-ready backlog items with clear acceptance criteria and effort estimates.
Learn sprint planning fundamentals through a guided process that models best practices for estimation, goal setting, and risk identification.
Discover more prompts that could help with your workflow.
Analyze overcrowded calendars and receive a strategic reorganization plan that protects focus time, batches meetings efficiently, and reclaims hours for meaningful work
Analyze how you spend your time, identify hidden time wasters, and get actionable strategies to reclaim lost hours
Create a personalized Getting Things Done productivity system tailored to your work, tools, and lifestyle.
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.