Scrum Explained: Roles, Events and Artifacts

Scrum is a lightweight agile framework for delivering complex work in short, fixed-length cycles called sprints. A small team commits to a goal for each sprint, builds a usable increment, shows it to stakeholders, and then reflects on how to work better. It is defined by three accountabilities, five events and three artifacts.

Scrum is deliberately small. The official Scrum Guide fits in under twenty pages, which is part of why it is easy to start and hard to do well.

The three accountabilities

Scrum used to call these "roles". The current guide calls them accountabilities, because they describe responsibilities rather than job titles.

• Product Owner. Owns the Product Backlog and decides what gets built next. One person, not a committee, so priorities stay clear.
• Scrum Master. Helps the team use Scrum effectively, removes impediments and protects the team from disruption. A coach, not a manager.
• Developers. Everyone who builds the increment: engineers, testers, designers. They decide how to deliver the sprint goal.

The five events

1. The Sprint. The container for everything else, a fixed period of one month or less. A new sprint starts as soon as the previous one ends.
2. Sprint Planning. The team agrees the sprint goal and selects the backlog items to achieve it. Our guide to sprint planning walks through it step by step.
3. Daily Scrum. A fifteen-minute check-in for Developers to inspect progress towards the goal and adapt the day's plan.
4. Sprint Review. The team shows what was built and stakeholders give feedback. It is a working session, not a slide presentation.
5. Sprint Retrospective. The team reflects on how it worked and picks improvements. See how to run a sprint retrospective that changes things.

Running sprints right now? See how Flow handles boards, sprints and burndown together. Get started with Flow →

The three artifacts

• Product Backlog. The ordered list of everything the product might need, tied to a longer-term Product Goal.
• Sprint Backlog. The sprint goal, the items selected for the sprint and the plan to deliver them.
• Increment. The usable, finished work produced in the sprint. It only counts if it meets the team's definition of done.

Each artifact has a commitment attached (Product Goal, Sprint Goal, Definition of Done) that keeps it focused.

Where Scrum goes wrong

• Ceremonies without outcomes. Holding every event but never shipping a usable increment.
• A Product Owner without authority. If every priority needs sign-off from three managers, the backlog stalls.
• Treating velocity as a target. Once points become a performance metric, estimates inflate and the number stops meaning anything.
• Skipping the retrospective. It is the first meeting cut under pressure and the one that would have fixed the pressure.

Scrum tools

Jira is the most widely used Scrum tool in software, with Scrum boards, backlogs, sprint reports and a vast ecosystem of add-ons. Teams comparing a Jira Scrum alternative are often looking for the same sprint basics with less setup, or with testing and client approval built in rather than added on.

How Flow helps

• Sprints built in. Start, complete and bulk-complete sprints, with burndown and sprint figures in project reporting.
• Backlog on a planner timeline. Epics, milestones and stories sit on one timeline, so the Product Owner can see the Product Goal and the next sprint together.
• Increments that are really done. Test runs record pass or fail per ticket, and clients can formally sign off delivered work in Livex Flow, which makes the Sprint Review concrete.
• Retrospective follow-through. Capture actions in the knowledge base and link pages to tickets both ways, so improvements become real work.