Sprint Planning and Review
📌 1. What is Sprint Planning?
Sprint Planning is a collaborative meeting that kicks off each Sprint. During this event, the Scrum Team decides what will be delivered in the upcoming Sprint and how the work will be accomplished.
Goal:
Define Sprint Goal — What do we aim to achieve?
Select Product Backlog Items (PBIs) to work on.
Create a Sprint Backlog (list of tasks for the Sprint).
✅ Key Participants:
Role
Responsibility
Product Owner (PO)
Clarifies requirements and sets priorities.
Scrum Master (SM)
Facilitates the meeting, ensures Scrum principles.
Development Team
Estimates effort, selects tasks they can commit to.
🛠 Key Inputs for Sprint Planning:
Product Backlog (prioritized list of user stories and tasks).
Team capacity (how much work the team can handle this sprint).
Past Sprint performance (velocity, if available).
📊 Sprint Planning Agenda:
Step
Outcome
1. Define Sprint Goal
Clear objective for the Sprint.
2. Select Backlog Items
Choose top-priority items that meet Sprint Goal.
3. Discuss and Estimate Tasks
Break down stories into actionable tasks.
4. Create Sprint Backlog
Final list of tasks team commits to deliver.
5. Clarify Dependencies and Risks
Identify blockers early.
📏 Duration:
For a 1-month Sprint: Up to 8 hours.
Shorter Sprints (e.g., 2 weeks) → proportionally less time.
📦 Output of Sprint Planning:
Sprint Goal (a clear focus).
Sprint Backlog (tasks/stories to be completed).
Team's commitment to deliverables.
📌 2. What is Sprint Review?
Sprint Review is a collaborative event held at the end of each Sprint to inspect the product increment and adapt the Product Backlog based on feedback. It's a working session, not just a demo!
Goal:
Demonstrate completed work.
Gather feedback from stakeholders.
Plan next steps or adjustments to the backlog.
✅ Key Participants:
Role
Responsibility
Product Owner (PO)
Reviews what was done vs. what was planned.
Scrum Master (SM)
Facilitates the session.
Development Team
Demos the product increment.
Stakeholders
Give feedback, ask questions, suggest improvements.
📊 Sprint Review Agenda:
Step
Outcome
1. Review Sprint Goal & What Was Done
Check if Sprint Goal was achieved.
2. Demonstrate Product Increment
Working features shown in action.
3. Collect Feedback
Stakeholders suggest improvements or changes.
4. Discuss Product Backlog Updates
Adjust priorities or add new items based on feedback.
5. Plan Future Work
PO may update roadmap based on insights gained.
📏 Duration:
For a 1-month Sprint: Up to 4 hours.
Shorter Sprints (e.g., 2 weeks) → proportionally less time.
🚀 Outcome of Sprint Review:
Inspected Increment (potentially shippable product).
Stakeholder Feedback captured.
Updated Product Backlog reflecting new priorities.
🔑 Difference between Sprint Planning and Sprint Review
Aspect
Sprint Planning
Sprint Review
Purpose
Plan what to do in the next Sprint
Review what was done in the completed Sprint
Focus
Define Sprint Goal, select tasks
Demonstrate work, gather feedback
Participants
Scrum Team
Scrum Team + Stakeholders
Outcome
Sprint Backlog
Product Increment and feedback
🎯 Summary:
Event
Key Goal
Outcome
Sprint Planning
Plan and commit to Sprint work
Sprint Goal + Sprint Backlog
Sprint Review
Demonstrate results and gather feedback
Product Increment + Updated Backlog
Last updated