QUESTION: After the Product Backlog hasbeen created by the Product Owner at the beginning of a project, items cannot be added to it or removed from it ANSWER: False EXPLANATION: The Product Owner can change the Product Backlog at any time. (What they cannot add to is the Team’s target in the current Sprint.) QUESTION: All communication between the Team and Product Owner is required to go through the ScrumMaster ANSWER: False EXPLANATION: Direct, open communication between the Team and the Product Owner is encouraged, as long as it doesn’t disrupt the Team QUESTION: Product Backlog Items the Team does not complete in a Sprint automatically get added into the next Sprint ANSWER: False EXPLANATION: Product Backlog Items the Team does not complete in a Sprint automatically get put back to the Product Backlog, and prioritized by the Product Owner QUESTION: During the Sprint, Team members are permitted to switch tasks with each other ANSWER: True EXPLANATION: The Team is free to organize the work of the Sprint in any way it chooses. QUESTION: Every single person on the Team is required to have all the development skills necessary to produce “done” Product Backlog Items – design, coding, testing, etc. ANSWER: False EXPLANATION: The Team as a whole must have those skills, but each individual member is not required to have all of them. QUESTION: The Sprint Review should be attended by the Team, Product Owner, ScrumMaster, as well as other stakeholders (like customers or end users) ANSWER: True EXPLANATION: The Sprint Review should be attended by anyone whose opinion or input would be useful to the Product Owner in the inspection of what’s been produced, or the adaptation of the Product Backlog. QUESTION: In Scrum, most of the testing is completed at the end of the project, just before the release ANSWER: False EXPLANATION: Leaving important testing until the end of a project creates significant risk. In Scrum, we do as much testing as possible each Sprint, in order to minimize or eliminate the testing that is left until the end of the project. QUESTION: In Scrum, as much testing as possible is done during each Sprint, to ensure that defects are found and fixed as early as possible ANSWER: True EXPLANATION: In Scrum, we try to do as much testing as possible each Sprint, in order to minimize the testing that is left until the end of the project QUESTION: In Scrum, the system architecture is finalized at the beginning of the project ANSWER: False EXPLANATION: In Scrum, the system architecture is started at the beginning of a project, but it continues to evolve during the project, as new requirements emerge, and as the Team discovers improvements QUESTION: In the Sprint Planning meeting, the Product Owner tells the Team how much they need to target in the Sprint ANSWER: False EXPLANATION: In the Sprint Planning meeting, the Team decides how much they can target in the Sprint, free of pressure from the Product Owner. QUESTION: In the Sprint Retrospective the Team, ScrumMaster and Product Owner discuss how to improve their process, practices and way of working ANSWER: True EXPLANATION: The purpose of the Sprint Retrospective is for the Team, ScrumMaster and Product Owner to collaborate and find ways to improve their process, practices, and way of working, within the Scrum framework. QUESTION: It is recommended that customers, end users, and other stakeholders be invited to the Sprint Review ANSWER: True EXPLANATION: The purpose of the Sprint Review is to inspect and adapt the product that’s being built, and inviting customers, end users, and other stakeholders to join will give more and better insights. QUESTION: It is recommended that management should attend the Daily Scrum Meeting ANSWER: False EXPLANATION: The purpose of the Daily Scrum Meeting is for the Team to update each other on progress, and make blocks visible to everyone, inside a 15-minute timebox. If management attends, it may disrupt this. QUESTION: Items at the top of the Product Backlog are typically smaller in size and have more detail than those at the bottom ANSWER: True EXPLANATION: On a regular basis, the Product Owner and Team collaborate to groom the Product Backlog. Product Backlog Grooming involves looking at the next 2-3 Sprints’ worth of Product Backlog, breaking the larger Product Backlog Items into smaller pieces, and getting a more detailed understanding of the requirements. QUESTION: Scrum recommends that no documentation should be completed, because time spent on it is waste ANSWER: False EXPLANATION: Scrum leaves it to the Product Owner, Team, and organization to define how much documentation is required. QUESTION: It is recommended that the Sprint Review be limited just to the Product Owner, Team and ScrumMaster ANSWER: False EXPLANATION: The purpose of the Sprint Review is to inspect and adapt the product that’s being built, and inviting customers, end users, and other stakeholders to participate will give more and better insights QUESTION: The “Definition of Done” is different for every single Product Backlog Item. ANSWER: False EXPLANATION: The “Definition of Done” should be relevant to most of the items on the Product Backlog. (There may however be a small number of Product Backlog Items which because of their unique characteristics require a “one-off ” Definition of Done.) QUESTION: The “Definition of Done” is decided solely by the Product Owner. ANSWER: False EXPLANATION: The Definition of Done is decided by the Team in collaboration with the Product Owner, based on the needs of the release, and the capabilities of the Team. QUESTION: Team members are only required to go to the Daily Scrum Meeting if they have blocks to report ANSWER: False EXPLANATION: The Daily Scrum Meeting is mandatory for all members of the Team who are not on leave that day. QUESTION: The purpose of the Sprint Review is to see working product, find improvements to make to the product, and know where we are relative to the goals of the release ANSWER: True EXPLANATION: The main purpose of the Sprint Review is to see working product, find improvements to make to the product, and know where we are relative to the goals of the release QUESTION: The Product Backlog is a list of tasks to be completed in the current Sprint ANSWER: False EXPLANATION: The list of tasks to be completed in the current Sprint is the Sprint Backlog. The Product Backlog is an ordered list of features, functionality, and other work that needs to be completed in the future. QUESTION: The Product Owner can change the future Product Backlog based on what they observe or feedback they receive in the Sprint Review ANSWER: True EXPLANATION: The Product Owner can change the future Product Backlog at any time. What they cannot change is the Team’s target in the current Sprint QUESTION: The Product Owner decides the Product Backlog content and prioritization, and the Team decides how much to target in the Sprint ANSWER: True EXPLANATION: The Product Owner decides the Product Backlog content and prioritization, and the Team decides how much to target in the Sprint. The Team should provide input to the Product Owner on the content and prioritization of the Product Backlog QUESTION: The Product Owner is allowed to make a change to the target of the Sprint, but only if the Team agrees ANSWER: False EXPLANATION: The Product Owner is not allowed to change the target of the Sprint; their only options are to terminate the current Sprint and start a new one, or wait until the next Sprint QUESTION: The Product Owner must remain completely silent in the Sprint Planning Meeting ANSWER: False EXPLANATION: The Product Owner is allowed to speak freely during the Sprint Planning Meeting (unless they are doing so in a way that is harmful or disruptive.) QUESTION: Product Backlog Grooming is for getting a better understanding of features in the current Sprint ANSWER: False EXPLANATION: Product Backlog Grooming involves looking ahead to the next 2-3 Sprints’ worth of Product Backlog, breaking the larger Product Backlog Items into smaller pieces, and getting a more details understanding of the requirements. QUESTION: The Product Owner should create the Product Backlog with input from any and all of the following: customers, end users, stakeholders, and the Team ANSWER: True EXPLANATION: To create and prioritize the Product Backlog effectively, the Product Owner will need lots of input and advice from customers and end users, stakeholders, and especially from the Team. A great ScrumMaster will help facilitate this. QUESTION: The purpose of the Daily Scrum Meeting is for the Team to update the Product Owner and Management on progress and blocks ANSWER: False EXPLANATION: The purpose of the Daily Scrum Meeting is for the Team to update each other on progress and blocks. After the meeting, the ScrumMaster will help with removing the blocks. QUESTION: The purpose of the Sprint Backlog and Burndown Chart is to enable the ScrumMaster to monitor the Team ANSWER: False EXPLANATION: The Team is responsible for self-organizing to achieve the target they set for the Sprint, and the purpose of the Sprint Backlog and Burndown Chart is to enable the Team to self-organize and give them continuous visibility during the Sprint. QUESTION: The ScrumMaster offers their assistance only when a Team member asks for help. ANSWER: False EXPLANATION: The ScrumMaster should offer assistance any time they see an opportunity to serve the Team QUESTION: The Team works together in the Sprint Planning Meeting to decide how much to target in the Sprint ANSWER: True EXPLANATION: The Team works together in the Sprint Planning Meeting to decide how much to target in the Sprint, and that target is shared among the members of the Team. QUESTION: The ScrumMaster is responsible for assigning tasks to the Team ANSWER: False EXPLANATION: The Team is responsible for self-organizing, and this includes together deciding who should work on which tasks during the Sprint QUESTION: The Product Backlog is an ordered list of features, functionality, and other work that needs to be completed in the future ANSWER: True EXPLANATION: The Product Backlog is an ordered list of features, functionality, and other work that needs to be completed in the future, to maximize ROI QUESTION: The ScrumMaster is responsible for making sure everyone knows and follows the practices of Scrum ANSWER: True EXPLANATION: One of the first things a ScrumMaster will do is teach Scrum to the Team, Product Owner, and stakeholders. Everyone needs to understand the principles and practices of Scrum, for it to be successful. QUESTION: The ScrumMaster is responsible for managing the Team to hit its target at the end of the Sprint ANSWER: False EXPLANATION: The ScrumMaster does not manage the Team – the Team is responsible for self-organizing during the Sprint. If they fail to do this effectively, it will be visible, and the ScrumMaster should help them learn how. QUESTION: The ScrumMaster is responsible for protecting the Team from outside distractions, disruption, or interference ANSWER: True EXPLANATION: The ScrumMaster is responsible for serving as a “bodyguard” for the Team, protecting them from outside distractions, disruption, or interference QUESTION: The Sprint Backlog tracks how long each Team member has spent so far on each task ANSWER: False EXPLANATION: The Sprint Backlog tracks how much work remains for each task being worked on or planned for in the Sprint. QUESTION: The Sprint Planning Meeting is timeboxed to 8 hours for a 1 month Sprint, and 4 hours for a 2 week Sprint ANSWER: True EXPLANATION: The Sprint Planning Meeting is timeboxed to these lengths to ensure that planning is completed in a reasonable amount of time, and to help the Team learn to do this. QUESTION: The Sprint Retrospective is only required if the Team is having difficulties; otherwise, it is optional ANSWER: False EXPLANATION: No Sprint is perfect, and a Sprint Retrospective is mandatory for every Sprint, to enable the Team, Product Owner, and ScrumMaster to identify improvements to our way of working in future Sprints.