Test your Scrum knowledge!

1. It is recommended that the Sprint Review be attended by the Dev Team, Product Owner, Scrum Master, as well as other stakeholders (like customers or end-users).
2. In Scrum, testing is mostly done in the final phase of the project, just before the release.
3. Product Backlog Items the Dev Team does not complete in a Sprint automatically get added to the next Sprint. 
4. In Scrum, the architecture of the system is finalized at the very beginning of the project.
5. All communication between the Dev Team and Product Owner is required to go through the Scrum Master.
6. After the Product Backlog has been created by the Product Owner at the beginning of a new project, items cannot be added, removed, or changed.
7. During the Sprint, Dev Team members can decide to switch tasks with each other. 
8. It is recommended that the Sprint Review be limited just to the Product Owner, Dev Team and Scrum Master.
9. The “Definition of Done” is decided solely by the Product Owner.
10. When a Dev Team sets a goal for a Sprint, they’re not making a promise about what they’ll complete – they’re making a commitment to do their best.
11. It is recommended that management attend the Daily Scrum Meeting.
12. In Scrum, the product must be of potentially shippable “doneness” and quality at the end of every Sprint, but it only ships when the Product Owner feels the timing is right and it is feature- complete enough to ship.
13.  In the Sprint Retrospective the Dev Team, Scrum Master and Product Owner discuss how to improve their practices and way of working.
14. Items at the top of the Product Backlog are usually sliced smaller and have more details than those at the bottom.
15. In Scrum, most of the testing is done during each Sprint, to ensure defects are found and fixed as early as possible.
16. Dev Team members are only required to go to the Daily Scrum Meeting if they have blocks to report.
17. The “Definition of Done” is different for every single Product Backlog Item.
18. Scrum recommends that no documentation be completed, because time spent on it is wasteful.
19. “Cross-functional” means everyone on the Dev Team is required to have all the skills – design, coding, testing, etc.
20. It is recommended that customers, end users, and other stakeholders be invited to the Sprint Review.

WhatsApp chat