Sprint Planning and Review

This document outlines our process for sprint planning, execution, and review, following the Scrum framework.

Sprint Cadence

Sprint Length: 2 weeks.
Sprint Cycle: Sprints start on a Monday and end on the Friday of the following week.

When: Monday morning of a new sprint.
Duration: 2 hours.
Attendees: Project Manager, development team, QA lead.
Purpose:
- To review the prioritized backlog, which is managed according to our Task Management Guidelines.
- To select a realistic number of tasks for the upcoming sprint (the sprint backlog).
- To break down larger tasks into smaller, manageable sub-tasks.
- To define a clear sprint goal.
Agenda:
- (30 mins) Review & Prioritize: The Project Manager presents the highest priority items from the product backlog.
- (60 mins) Task Selection & Estimation: The team discusses each item and estimates the effort required. The team commits to a set of tasks for the sprint.
- (30 mins) Define Sprint Goal: The team agrees on a concise goal that summarizes what the sprint aims to achieve.

When: Every day at the same time.
Duration: 15 minutes.
Attendees: Project Manager, development team, QA lead.
Purpose: To sync on progress and identify any blockers.
Format: Each team member answers three questions:
1. What did you accomplish yesterday?
2. What will you work on today?
3. Are there any blockers impeding your progress?

When: Friday afternoon at the end of a sprint.
Duration: 1 hour.
Attendees: Project Manager, development team, QA lead, and client stakeholders.
Purpose:
- To demonstrate the work completed during the sprint.
- To get feedback from stakeholders.
Agenda:
- (15 mins) Sprint Goal Recap: The Project Manager reviews the sprint goal.
- (30 mins) Live Demo: The development team demonstrates the new features and functionality.
- (15 mins) Feedback & Discussion: Stakeholders provide feedback and ask questions.

When: Immediately after the Sprint Review.
Duration: 1 hour.
Attendees: Project Manager, development team, QA lead (client does not attend).
Purpose: To reflect on the past sprint and identify areas for improvement.
Format: The team discusses:
- What went well?
- What could be improved?
- What will we commit to changing in the next sprint?
Outcome: Actionable items for improving processes, tools, or communication in the next sprint.