Scrum for beginners: part 2 — events and artefacts

In the first part, we discussed roles in Scrum. Now it is time for events and artefacts — the elements that give work its rhythm, transparency and predictability.

Events in Scrum

Sprint

A sprint is a fixed timebox lasting no longer than one month, most often 1–3 weeks. The outcome of each sprint is a potentially releasable product increment. Once a sprint has started, its length is not changed; the Product Owner may cancel a sprint only in exceptional situations, for example when the sprint goal no longer makes business sense.

Sprint Planning

Sprint Planning lasts up to 8 hours for a one-month sprint. Based on Product Backlog items prepared by the Product Owner, the team defines the sprint goal (Sprint Goal), selects the scope of work and creates a plan for delivering it. The result is the Sprint Backlog — a forecast of the work along with the approach to delivering it.

Daily Scrum

The Daily Scrum is a meeting of the development team lasting no more than 15 minutes each day. It serves to inspect progress towards the Sprint Goal and adapt the plan for the next 24 hours. It is not a status meeting for control purposes — the goal is to identify obstacles and quickly correct the course of action.

Sprint Review

The Sprint Review takes place at the end of the sprint and lasts up to 4 hours for a one-month sprint. The Product Owner invites stakeholders, and the team presents the Increment created, gathers feedback and proposals for next steps. On this basis, the Product Backlog is updated. This meeting strengthens collaboration between the team and stakeholders and helps maximise the product’s value.

Sprint Retrospective

The Retrospective takes place after the Sprint Review and before the next planning session. For a one-month sprint, it lasts up to 3 hours. The team analyses the past sprint in terms of people, relationships, processes and tools, identifying what works and what needs improvement. It is recommended that at least one improvement be added to the Sprint Backlog of the next sprint. The team also reviews the Definition of Done, refining it to improve quality and collaboration.

Artefacts in Scrum

Increment

An Increment is the sum of all completed work in the sprint, consistent with previous increments. It must meet the Definition of Done and be potentially ready for production release. If it requires additional testing or fixes, it is not complete. Only the Product Owner decides on release.

Definition of Done

The Definition of Done is a shared quality standard that defines when a work item is considered complete. It may include, among other things, the scope of testing, reviews, business acceptance or release. If the organisation has its own standards, the team treats them as the minimum. The Definition of Done should evolve along with the team’s maturity, raising product quality.

Product Backlog

The Product Backlog is an ordered list of everything that may increase the product’s value: features, requirements, ideas or user stories. It is the responsibility of the Product Owner, who ensures priorities and clarity. The backlog is dynamic and changes as the product evolves. The team may co-create and further define backlog items based on the Product Owner’s recommendations. Items do not need to be fully described until they enter the Sprint Backlog; at that point, they should be clear enough for the team to deliver them.

Sprint Backlog

The Sprint Backlog consists of the Product Backlog items selected for a given sprint, supplemented with the Sprint Goal and the delivery plan. The Sprint Backlog is owned by the development team: only the team decides what it will take into the sprint and how it will adapt the plan. The content of the Sprint Backlog evolves during the sprint — items may be added, removed or split if this helps achieve the Sprint Goal. Adaptations may take place on an ongoing basis during short and effective refinement sessions, without distracting from the sprint goal.

Summary

Scrum is simple to understand, yet difficult to master. Understanding the purpose of timeboxes, the role of events and artefacts, and the impact of changes on the process is fundamental. Mastery requires discipline, continuous inspection and the courage to adapt.