Back to all prompts
AgileIntermediate

Sprint Planning Assistant

Create a realistic sprint goal and proposed scope from backlog items.

Prompt
Act as an experienced Scrum Product Owner and Agile Delivery Lead.

Prepare a sprint planning proposal using the following information:

Sprint duration:
{{sprint_duration}}

Team capacity:
{{team_capacity}}

Backlog items:
{{backlog_items}}

Known dependencies:
{{dependencies}}

Create:

1. A concise Sprint Goal
2. Recommended Sprint Scope
3. Items that should remain outside the sprint
4. Suggested sequence of work
5. Dependencies and blockers
6. Delivery risks
7. Clarification questions for the team
8. Definition of Done checklist
9. A short contingency plan if capacity is reduced

Do not treat the initial backlog as a guaranteed commitment.

Identify items that are too large, unclear or dependent on unresolved decisions.

Return the result as a structured sprint planning summary.

Replace the highlighted variables with information about your own product, feature or business objective before using the prompt.

{{sprint_duration}}{{team_capacity}}{{backlog_items}}{{dependencies}}

Example in action

See how this prompt transforms a real input into a structured result.

Example input

Sprint duration: Two weeks Team capacity: 30 story points Backlog items: - Password reset: 5 points - Profile editing: 8 points - Student verification: 13 points - Referral dashboard: 13 points Dependencies: Student verification requires access to an external verification API. `

Example output

Sprint Goal: Improve account management and prepare the foundation for student eligibility verification. Recommended Sprint Scope: - Password reset: 5 points - Profile editing: 8 points - Student verification integration spike: 5 points - Student verification foundation: 8 points Total: 26 story points Outside Sprint: Referral dashboard Reason: The referral dashboard does not support the Sprint Goal and would exceed available capacity. Primary Risk: External verification API access may not be available at the beginning of the sprint. Contingency: If API access is delayed, complete the integration contract, mocked responses and error-handling design.

Tags

scrumsprintplanning