Scrum Framework — Self-Study Unit
Self-study course
Scrum Framework
A self-study course on the Scrum framework — from empiricism and values through accountabilities, events and artefacts to product ownership and team effectiveness in practice. Every lesson ends with exam questions, every section with a final test.
A note on your progressThis browser does not allow storage for files opened locally. The course works in full, but ticks and test results are lost when you close it. Remedy: open the files from a network drive or a web server, or allow website data to be stored for this page in your browser settings.
How the course is built
The order is recommended, but individual sections also work on their ownTwelve sections, ten shared and two by focus
The order is recommended; individual sections also work on their own
The twelve sections
The bar on each tile shows your own progress-
1
Agile foundations and empirical work
Why planning everything up front fails for complex products, what empiricism means and how iterative differs from incremental.
-
2
The framework at a glance
The definition in one sentence, the three accountabilities, five events, three artefacts and three commitments — and why the framework is immutable.
-
3
The five values
Commitment, Focus, Openness, Respect and Courage — how the values shape behaviour and how you spot it when they are broken.
-
4
The Scrum Team
One unit with no sub-teams and no hierarchies, ten people or fewer, cross-functional and self-managing — and what the Developers are accountable for.
-
5
Product Owner — accountable for the value
One person, not a committee: Product Backlog management, binding decisions, transparency of the backlog and the relationship with the stakeholders.
-
6
Scrum Master — leadership that serves
Accountable for the effectiveness of the team: service to the team, to the Product Owner and to the organisation — and the four modes of support.
-
7
The Sprint
The container for everything else: fixed length, one month at most, negotiable scope at unchanged quality — and who may cancel a Sprint.
-
8
Sprint Planning and Daily Scrum
Why, What and How in Planning, how the Sprint Goal comes about, and the Daily Scrum as an adjustment of the plan — not as a status report.
-
9
Sprint Review and Sprint Retrospective
The Review as a working session to inspect the outcome, not as an approval gate — and the Retrospective as the close of the Sprint.
-
10
Artefacts and commitments
Product Backlog with the Product Goal, Sprint Backlog with the Sprint Goal, Increment with the Definition of Done — and what “done” dependably means.
-
11
Product ownership in practice
Product role block: vision and strategy, product boundaries, value measurement, stakeholder involvement, backlog techniques and forecasting.
-
12
Team effectiveness and organisational change
Facilitation role block: leading discussions to a decision, conflict, flow metrics, technical debt, several teams and change.
How to work with this course
Read and tick off
Every lesson opens with a diagram, then come the core statement, the key points with their source and a practical example. The tick on the left marks the lesson as done.
Check straight away
Two questions per lesson in three formats: single choice with four options, multiple response with the number of correct answers stated, and true/false. After checking, every option carries a label.
Finish the section
Every section ends with a final test of nine to eleven questions across the material. From 85 percent it counts as passed — with ten questions that means: one mistake at most.
Use the sources
Every key point carries a tag. It names the section of the reference document the statement comes from — or Practice, where it is common working practice and not a requirement.
Key terms
The terms of the framework are kept in their English form, because exam questions use them that way- Scrum
- A lightweight framework that helps people generate value through adaptive solutions for complex problems. Immutable: only as a whole is it Scrum.
- Empiricism
- Knowledge comes from experience and observation, not from prediction. In the framework it carries the three pillars transparency, inspection and adaptation. Alongside it stands Lean Thinking: reduce waste, focus on the essentials.
- Transparency
- Work and artefacts are visible to those performing the work and those receiving it. The precondition for any meaningful inspection; inspection without it is misleading.
- Inspection
- Artefacts and progress are inspected frequently and diligently. The events are the built-in opportunities for that — four within the Sprint, five counting the Sprint itself.
- Adaptation
- If anything deviates outside acceptable limits, the approach or the outcome is corrected as soon as possible. Inspection without adaptation has no effect.
- Scrum Team
- The fundamental unit: one Product Owner, one Scrum Master and Developers. Typically ten people or fewer — a guide, not a limit. Cross-functional, self-managing, with no sub-teams and no hierarchies.
- Product Owner
- Accountable for maximising the value of the product and for effective Product Backlog management. One person, not a committee.
- Scrum Master
- Accountable for the effectiveness of the Scrum Team and for establishing the framework. Serves the team, the Product Owner and the organisation; causes impediments to be removed.
- Developers
- The people in the Scrum Team who create every aspect of a usable Increment in each Sprint. They plan the Sprint, instil quality through the Definition of Done and adapt their plan each day.
- Sprint
- The container for all other events and for all the work. Fixed length, one month or less; the next one starts immediately after the previous one ends.
- Sprint Planning
- Opens the Sprint and covers Why, What and How. Eight hours at most for a one-month Sprint, usually shorter for shorter Sprints. Its outcome is the Sprint Backlog.
- Daily Scrum
- Fifteen minutes on every working day, for the Developers. The timebox is fixed and is not shortened for shorter Sprints. Inspects progress towards the Sprint Goal. No prescribed format.
- Sprint Review
- Inspects the outcome of the Sprint with the key stakeholders and determines future adaptations. Four hours at most for a one-month Sprint. A working session, not an approval gate.
- Sprint Retrospective
- Plans ways to increase quality and effectiveness and concludes the Sprint. Three hours at most for a one-month Sprint.
- Product Backlog
- An emergent, ordered list of what is needed to improve the product. The single source of work for the Scrum Team. It carries the Product Goal.
- Sprint Backlog
- The Sprint Goal, the selected items and an actionable plan for delivering them — Why, What and How. A plan by the Developers and for the Developers. It carries the Sprint Goal.
- Increment
- A concrete stepping stone towards the Product Goal, additive to all prior ones and thoroughly verified. Usable, so that it delivers value. Several per Sprint are possible. It carries the Definition of Done.
- Product Goal
- Describes a future state of the product and serves as the target for planning. Contained in the Product Backlog; one at a time — it is fulfilled or abandoned before the next is taken on.
- Sprint Goal
- The single objective of the Sprint and a commitment by the Developers, worked out by the whole Scrum Team in Sprint Planning. Scope remains negotiable without touching the goal.
- Definition of Done
- A formal description of the state in which the Increment meets the quality measures for the product. Without an organisational standard the Scrum Team creates it; a standard counts as a minimum. With several teams on the same product it is shared.
- Refinement
- The ongoing breaking down and sharpening of Product Backlog items. Not an event, with no timebox. Size is decided by the Developers who do the work.
- Stakeholder
- People with an interest in the product who are not part of the Scrum Team. The Sprint Review is the built-in place to collaborate with them; they too are expected to be open.
- Self-management
- The team decides internally who does what, when and how it is carried out. Not the content and order of the Product Backlog, and not an organisational minimum standard.
- Cross-functional
- Between them the members have every skill needed to create value in each Sprint — without a permanent hand-off to the outside. The German edition of the reference document calls this “interdisziplinär”.
- Accountability
- To be accountable is to answer for the outcome, and it cannot be handed over. It is separate from being responsible for the work itself — that can be delegated.
- Timebox
- The duration an event is limited to at most. It is not exceeded. For the Daily Scrum it is fixed; for the other events the stated figure applies to a one-month Sprint and is usually shorter for shorter Sprints.
- Velocity
- A widespread practice for gauging how much is delivered per Sprint. Not part of the framework, and not comparable between teams.
- German terms
- This course uses the English core terms. The German edition of the reference document writes, among others, Produkt-Ziel for Product Goal, Developer:innen, Product Owner:in, Scrum Master:in and Stakeholder:innen. The same thing is meant in each case.
Scope and limits
Terms and formsThis course uses the English core terms: Product Goal, Sprint Backlog, Definition of Done, Developers, Product Owner, Scrum Master, Stakeholder. The German edition of the reference document translates some of them and writes, among others, Produkt-Ziel, Developer:innen, Product Owner:in, Scrum Master:in, Stakeholder:innen as well as interdisziplinär for cross-functional. The same thing is meant in each case. Since exam questions on this subject are asked predominantly in English, the English forms take precedence here.
What is evidenced
Key points carrying a tag such as Framework: Sprint name the section of the reference document the statement rests on. The tag Agile Manifesto refers to the four value pairs and twelve principles, Lean to the Lean Thinking named in the framework.
What is practice
About a third of the key points carry the tag Practice. Behind it stands common working practice that the framework does not prescribe — estimation techniques, flow metrics, forecasting, forms of contract. The distinction is itself exam material.
Progress and data protection
Your ticks are saved to your Zertio account, so your progress is still there on another device. Answers, test results and the choice between light and dark live solely in your browser's local storage; signed out, that applies to the whole record. The Reset button clears the whole record — in the browser as well as in your account.