General
In this forum you can ask for clarification of the content and simulators.
To access these simulators is necessary to use the test users.
These sample tests show the final grade.
This is a free SCRUM simulator with 20 questions, you can make unlimited attempts.
Users: demo1, demo2 or demo3
Password: demo12345
To access these simulators is need to register in the system.
These show the correct answers.
This is a 20 questions SCRUM simulator , you can make unlimited attempts. (Registration required)
This is a 30 questions SCRUM simulator , you can make unlimited attempts. (Registration required)
This is a 40 questions SCRUM simulator , you can make unlimited attempts. (Registration required)
The fundamental unit of Scrum is a small team of people, a Scrum Team.
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
Sprints are the heartbeat of Scrum
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint.
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation.
The Product Backlog is an emergent, ordered list of what is needed to improve the product.
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
An Increment is a concrete stepping stone toward the Product Goal.
The definitions are taken from ‘The ScrumTM Guide’ © 2017 Ken Schwaber and Jeff Sutherland. These are subject to the Attribution Share-Alike license of Creative https://creativecommons.org/licenses/by-sa/4.0/legalcode