The Sprint

Sprints are time-boxed iterations (typically 1-4 weeks) during which Development Teams create potentially releasable product increments. Each Sprint includes Planning, Daily Scrums, development work, Review, and Retrospective. Sprint length remains consistent to establish rhythm and predictability. Sprints provide regular opportunities for inspection, adaptation, and stakeholder feedback whilst maintaining focus through clear goals and boundaries.

Sprint Planning

Sprint Planning is a collaborative ceremony where teams define Sprint Goals and select Product Backlog items for the upcoming Sprint. The Product Owner presents priorities whilst the Development Team assesses capacity and technical feasibility. Teams create Sprint Backlogs, breaking down selected items into tasks. Effective planning balances ambition with realism, ensuring clear understanding of work scope and success criteria.

Daily Scrum

The Daily Scrum is a 15-minute synchronisation meeting where Development Team members coordinate work and identify impediments. Participants typically discuss yesterday’s progress, today’s plans, and any obstacles. This ceremony promotes transparency, enables quick problem-solving, and maintains team alignment. While structured, Daily Scrums should adapt to team needs whilst maintaining focus on Sprint Goal achievement.

Sprint Review

Sprint Reviews demonstrate completed work to stakeholders and gather feedback on the product increment. The Development Team presents working software whilst the Product Owner explains what was accomplished and what remains. Stakeholders provide input on future direction. This ceremony fosters collaboration, validates assumptions, and informs subsequent planning decisions through direct stakeholder engagement and product inspection.

Sprint Retrospective

Sprint Retrospectives provide teams with structured opportunities to reflect on their working practices and identify improvements. Teams examine what went well, what could be better, and specific actions for enhancement. This ceremony occurs after Sprint Reviews, focusing on process and team dynamics rather than product features. Effective retrospectives require psychological safety, honest communication, and commitment to implementing improvements.