vaayaa Inclusive Education

Micro Diploma in Scrum Framework Basics Course: Roles, Events and Artifacts

Updated October 2026 6 min read

Most people who work near software teams have heard the word sprint, but few know that Scrum was never meant to be a set of rules for building software at all. Its creators described it as a simple framework for solving complex problems, and it has only three roles, five events and three artifacts. That small size is the surprise. Almost everything teams argue about in Scrum comes from how people fill those few parts, not from the parts themselves. For a structured start, see our Micro Diploma in Scrum Framework Basics Course.

This subject is best learned in order, with the vocabulary first and the habits second. The Micro Diploma in Scrum Framework Basics Course covers the framework in a focused, text-first way, with worked examples and an assessment at the end. It is accredited under IOAC, and the certificate carries a QR code that anyone can check. You can read more about the course here: Micro Diploma in Scrum Framework Basics Course.

Part 1

What Scrum Is for and Where Teams Use It

Scrum is a way for a group to deliver work in short, repeated cycles and learn from each one. The team agrees on a goal, picks a slice of work they can finish in a few weeks or less, builds it, shows it to people who care about the result, and then looks at how they worked together. The cycle then starts again. The idea is that real progress shows up sooner when you ship small pieces and check them often.

Teams use Scrum most often for software, but you will also see it in hardware projects, marketing campaigns, training design and office operations. The common thread is work that is uncertain enough that a full plan written at the start would be wrong by the middle. There is a clear difference between a team that dips into Scrum words now and then and a team that runs the framework on purpose. The first group uses daily standups and calls everything a sprint. The second group keeps the events, honors the roles and measures whether the work is getting better.

Part 2

Roles, Events and Artifacts You Need to Know

The three roles are the Product Owner, who manages the list of wanted work and decides what matters most; the Scrum Master, who helps the team follow the framework and removes obstacles; and the Developers, the people who do the building, whatever their job title. Scrum deliberately keeps the team small and cross functional so that decisions do not wait in a queue.

The five events are the Sprint itself, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. The Sprint is a fixed time box, often two to four weeks, and nothing is added to it once it starts unless the goal is at risk. The three artifacts are the Product Backlog, the Sprint Backlog and the Increment. A good beginner habit is to ask of every meeting, what decision does this help us make, and of every artifact, who uses this and why.

Part 3

How a Sprint Moves from Planning to Review

A sprint starts with planning. The Product Owner brings the highest value items from the Product Backlog, and the Developers decide how much they can realistically finish. The result is a sprint goal and a Sprint Backlog that the team owns. Teams often make the mistake of loading too much, so experienced practitioners pay attention to past capacity rather than hope.

During the sprint, the Daily Scrum is a short planning check of about fifteen minutes, not a status report to a manager. Each day the team looks at progress toward the sprint goal and talks about any blocker. At the end, the Sprint Review shows stakeholders what is actually done and collects feedback that changes the backlog. The Retrospective then looks inward at the process, asking what to keep, what to change and what to try next. Each step feeds the next, and skipping the retrospective is the fastest way to stop learning. You can also look through the diploma course catalog before you decide.

The Scrum Cycle in Three Steps

  1. Plan the SprintThe team picks a sprint goal and the backlog items that support it.
  2. Build and InspectDaily check ins, the work itself and a review with stakeholders.
  3. Adapt the ProcessThe retrospective chooses one change that the next sprint will test.
Read the steps as a loop, not a line. Each sprint begins where the last retrospective ended, so the change chosen in step three shapes the planning in step one of the next cycle.
Part 4

Common Mistakes, Risks and Ways to Adapt

The most frequent error is treating Scrum as a way to speed up old habits. A team that still hands tasks down from a manager, hides work in progress and reports only at the end has not changed much, even with the right meeting names. Another common problem is a Product Owner who is unavailable or who keeps changing priorities mid sprint, which quietly breaks the goal. Scrum Masters sometimes become project managers in disguise, and then the team stops owning its own process.

Adapting the framework is allowed, but it helps to know which parts are fixed. Teams can change the length of a sprint, the format of a review or the tools they use. They should be more careful with the commitment to a sprint goal, the time box itself and the habit of inspecting and adapting. Working with a team that has regulatory or safety needs, or a team that is spread across time zones, usually means more written notes and clearer handoffs, not fewer. Responsible practice also means being honest in reviews about what is not finished.

Part 5

What You Should Be Able to Do After Learning Scrum

A useful learning outcome is being able to explain each role, event and artifact in plain words and say why it exists. You should also be able to read a backlog and order items by value, describe what a sprint goal is for, and run a short retrospective that produces one concrete change. Beginners usually grow from following the steps, to understanding the reasons behind them, to adjusting the framework for a real team without losing its purpose.

Assessment can be simple. Try writing a short sprint plan for a small real task, then explain how you would handle a blocked item on day three. Once the basics feel natural, the next steps include Product Owner and Scrum Master practice, agile estimation methods and, for people who want to keep building technical depth, more technical courses. A helpful way to choose is to see what the diploma course catalog offers for your next stage of study, and to compare it with more technical courses that match your current work. Related subjects are gathered in more technical courses.

Wrap up

Your Next Step

If you are new to Scrum, start with the framework itself rather than the tools that claim to run it. Work through the roles, events and artifacts until you can explain them to a colleague without notes. Then try a small sprint on something real, even a personal project, and review what happened. That habit of short cycles and honest reflection is the real skill this framework teaches.

Keep learning

Related Courses

Hourly Active: 45,668 Learners