{"id":27346,"date":"2026-11-07T15:00:00","date_gmt":"2026-11-07T14:00:00","guid":{"rendered":"https:\/\/www.eurotechconseil.com\/en\/?p=27346"},"modified":"2026-11-07T15:00:00","modified_gmt":"2026-11-07T14:00:00","slug":"sprint-in-scrum","status":"publish","type":"post","link":"https:\/\/www.eurotechconseil.com\/en\/blog\/sprint-in-scrum\/","title":{"rendered":"What Is a Sprint in Scrum? Length, Ceremonies and Deliverables"},"content":{"rendered":"

[et_pb_section fb_built=”1″ admin_label=”section” module_class=”etc-article” _builder_version=”4.16″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row admin_label=”row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||” theme_builder_area=”post_content”][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

What Is a Sprint in Scrum? Length, Ceremonies and Deliverables<\/h1>\n

[\/et_pb_text][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

The sprint is the heartbeat of Scrum. It is a short, fixed period during which a team turns a set of priorities into a working, tested increment of the product. Understanding how a sprint works helps you follow a software project, read progress reports and take part in the right meetings.<\/p>\n

This guide explains what a sprint in Scrum<\/strong> is, how long it lasts, the events that structure it and what you should receive at the end of each one.<\/p>\n

[\/et_pb_text][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Definition: what is a sprint?<\/h2>\n

According to the Scrum Guide, a sprint is a fixed-length event of one month or less during which the Scrum team creates a usable increment. A new sprint starts immediately after the previous one ends. All the work needed to reach the product goal, including planning, development, review and retrospective, happens inside sprints.<\/p>\n

Each sprint has a sprint goal<\/strong>: a single objective that gives the team focus, for example “Sales managers can approve quotes online”.<\/p>\n

[\/et_pb_text][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

How long is a sprint?<\/h2>\n

The Scrum Guide sets a maximum of one month. In practice, most software teams choose one to four weeks<\/strong>, and two weeks is a very common choice.<\/p>\n\n\n\n\n\n\n\n
Sprint length<\/th>\nAdvantages<\/th>\nPoints of attention<\/th>\n<\/tr>\n<\/thead>\n
1 week<\/td>\nVery fast feedback, easy to adjust<\/td>\nMeetings take a larger share of the time<\/td>\n<\/tr>\n
2 weeks<\/td>\nGood balance between delivery and feedback<\/td>\nRequires well-refined backlog items<\/td>\n<\/tr>\n
3 to 4 weeks<\/td>\nRoom for larger features<\/td>\nSlower feedback, higher risk of drifting<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Whatever the length, it should stay constant so the team can measure its pace and make reliable forecasts.<\/p>\n

[\/et_pb_text][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

The Scrum events inside a sprint<\/h2>\n

Sprint planning<\/h3>\n

At the start, the team defines the sprint goal, selects items from the product backlog and plans how to deliver them. The Scrum Guide timeboxes it to a maximum of eight hours for a one-month sprint, and usually shorter for shorter sprints.<\/p>\n

Daily Scrum<\/h3>\n

A 15-minute daily meeting where developers inspect progress toward the sprint goal and adapt their plan for the next day.<\/p>\n

Sprint review<\/h3>\n

At the end, the team demonstrates the increment to stakeholders, collects feedback and updates the product backlog. This is the key meeting for the client.<\/p>\n

Sprint retrospective<\/h3>\n

The team reviews how it worked (people, tools, process, definition of done) and chooses improvements for the next sprint.<\/p>\n

Backlog refinement, the ongoing work of clarifying and estimating upcoming items, also happens during the sprint so that the next planning runs smoothly. The roles involved in each event are described in our article on Scrum roles<\/a>.<\/p>\n

[\/et_pb_text][et_pb_text _builder_version=”4.27.9″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Sprint artifacts and deliverables<\/h2>\n