Demystifying Scrum 1
Quiz by PlaysInBusiness
Feel free to use or edit a copy
includes Teacher and Student dashboards
Measure skillsfrom any curriculum
Tag the questions with any skills you have. Your dashboard will track each student's mastery of each skill.
- edit the questions
- save a copy for later
- start a class game
- automatically assign follow-up activities based on students’ scores
- assign as homework
- share a link with colleagues
- print as a bubble sheet
- Q1
What is the Purpose of Scrum?
It's about deliverying increments each sprint by upfront specifications. Scrum is a software delivery framework.
Teams create value by adapting solutions continously. Scrum is a discovery framework, not a delivery approach.
The main purpose is to deliver something new every Sprint. Scrum is about chopping work into smaller parts.
The main purpose is to ensure team capacity allocation best. Scrum is about working in small teams efficiently.
120s - Q2
What is the Scrum Team commitment?
During the Sprint, you can't stop or change the planned work. Be careful in piling the Sprint Backlog.
Sprint Backlog Items are the promise the team make to their stakeholders. They have to be fullfilled by all circumstances.
The Sprint Goal.During the Sprint the planned work can be skipped if better ways occur to achieve the Sprint Goal.120s - Q3
What is the Purpose of Scrum Events?
Planning and controling deliveries in detail to implement a product incrementally.
Monitoring capacity to work efficiently.
Not to plan the executing the next set of work items.Planning and creating value.120s - Q4
Does Scrum handle long-term thinking?
Scrum isn't suited for looking beyond 1 or 2 months due to the Sprint size limit < 4 weeks,
Product Goals are the long-term objectives in Scrum. They describe the future state of the product.There is no long-term development since you can change the implementation after each sprint
120s - Q5
How to assess Team Performance in Scrum?
By Teams' Productivity. Assess whether the team meet the sprint deadlines and the committed deliveries (Sprint Backlog Items).
By Teams' Productivity. Assess how many Story Points a team deliver.
By the Impact of the product. Questions like “Are customers happy with the product?” are key.By Teams' Goal Achievement (Product Goal and Sprint Goal) — Independent of amount of Story Points achieved.120s - Q6
If a Scrum Team achieves the Sprint Goal early, must they then continue the Sprint?
Team can commit to a new, additional Sprint Goal and start working to this without creating carry-overs to the next Sprint.They can shorten the Sprint and start the next one.
The Sprint ends when the time-box expires.120s - Q7
What can we do within a Sprint?
Hardening Sprint — An additional Sprint to finalize an item before it gets deployed.
Sprints for different phases — Sprints for Requirements Gathering, for Design, for Development, Testing, Deployment.
None of the mentioned.Sprint Zero — Sprint Zero entails everything that is deemed required to start a project or to start working on a feature.
120s - Q8
Do we need Estimates in a Complex Environment?
The more information the more precise are the estimations how long it takes to finish a feature.
Start the work with a rough estimate and adapt (re-estimate and re-work) if needed.Spending time on detailed estimates is a waste.Estimations are pointless.
120s - Q9
Who Should Lead the Scrum Team?
The Scrum Team knows three accountabilities: Product Owner, Scrum Master, and Developer. They are hierarchically equal. Together, they decide what to do and how to do the work.
Product Owners report to upper management or Product Department, Scrum Masters report to Product Owners how the team works, and the Developers report to Scrum Masters and Product Owners.
120s - Q10
In Scrum is no place for managers.
There is no place for managers in Scrum. The word “manager” shows up exactly zero times in the Scrum Guide.
The Scrum Guide doesn’t discuss managers. But indirectly they are mentioned. They are key stakeholders of the Scrum Teams.
120s