Scrum rules and timeboxes

Sprint — The core container for all other events. It's a fixed-length iteration (1–4 weeks) during which the team builds a potentially releasable product increment. Once it starts, its length doesn't change.

Sprint Planning — Kicks off each Sprint. The whole Scrum Team meets to decide what to work on and how to do it. The 8-hour max is for a 4-week Sprint; shorter Sprints get proportionally shorter planning sessions.

Daily Scrum — A 15-minute daily sync for the Developers (not the whole team by rule) to inspect progress toward the Sprint Goal and adjust the plan for the next 24 hours. Same length regardless of Sprint duration.

Sprint Review — Held at the end of the Sprint. The Scrum Team and stakeholders inspect the increment and discuss what was done, what wasn't, and adapt the Product Backlog if needed. It's a working session, not just a demo.

Sprint Retrospective — The final event of the Sprint, focused on the team itself — what went well, what didn't, and what concrete improvements to commit to next Sprint. It's where continuous improvement happens.

• Backlog Refinement — An ongoing process in which the Scrum Team reviews and revises the Product Backlog items to ensure the backlog is up-to-date and prioritized, enabling effective planning for future Sprints.