agile-sprint-planning_skill

Overview

This skill helps teams plan and execute effective Agile sprints by defining clear sprint goals, estimating user stories, and managing the sprint backlog. It provides structured checklists, meeting agendas, estimation techniques, and standup templates to keep iterations focused and predictable. The guidance is practical and outcome-oriented to maximize team throughput and incremental value delivery.

How this skill works

It inspects sprint inputs—product priorities, team capacity, past velocity, and story details—to produce a timeboxed plan and a committed sprint backlog. It uses planning poker and story-point heuristics to reach consensus estimates and recommends capacity calculations and utilization targets. It also prescribes a structured planning meeting, daily standup flow, and success criteria for validating the sprint outcome.

When to use it

• At the start of a new sprint cycle to build a committed backlog
• When refining priorities or preparing a sprint goal with the Product Owner
• During story estimation sessions to achieve consensus and consistent points
• To structure daily standups and track blockers for timely resolution
• When assessing mid-sprint scope changes or rebalancing work
• While preparing for sprint review and retrospective input

Best practices

• Base capacity on historical velocity and include a 10-20% buffer for interruptions
• Timebox planning (e.g., ≤2 hours for a 2-week sprint) and include the whole team
• Break large stories into 5–13 point pieces and avoid planning to 100% capacity
• Use planning poker to surface disagreements, then discuss and re-estimate
• Document a concise sprint goal and measurable success criteria visible to the team

Example use cases

• Preparing a sprint backlog from a groomed product backlog using team capacity
• Running a planning poker session to align on story complexity and effort
• Calculating utilization and remaining capacity to decide which stories fit
• Facilitating daily standups to identify blockers and assign follow-ups
• Writing a sprint goal with success criteria for stakeholder review and A/B release