[ { "title": "What are the requirements for developing a new Product when using Scrum?", "kind": "multiple-four", "resolution": [ 0, 1, 2, 3 ], "answers": [ { "content": "Developers for doing the development work.", "explanation": "" }, { "content": "A Scrum Master for managing the Scrum implementation.", "explanation": "" }, { "content": "A Product Owner with ideas who knows why the Product is needed.", "explanation": "A list of ideas lays the basis for the Product Backlog." }, { "content": "A Product Goal (often as a step toward a larger Product Vision).", "explanation": "" }, { "content": "Requirements document.", "explanation": "The Product Backlog holds all requirements." }, { "content": "A budget approved by the Stakeholders.", "explanation": "This is not a requirement from a Scrum perspective." }, { "content": "A complete Product Backlog that contains the requirements.", "explanation": "The Product Backlog is never complete and constantly changing." } ] }, { "title": "Scrum can be complemented with additional practices like burn-down charts to help forecast progress. In this situation, what does a burn-down chart show?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The remaining amount of work over time.", "explanation": "" }, { "content": "How the velocity evolved over multiple Sprints.", "explanation": "The velocity is measured when the Sprint ends and may change in the future. The past velocity is used to estimate when the work remaining will most likely be completed." }, { "content": "The total cost of the project at the forcasted completion date.", "explanation": "A burn-down chart is not used to determine the cost." }, { "content": "The exact number of Sprints needed to complete all work in the Product Backlog.", "explanation": "A forecast is never an exact date." } ] }, { "title": "Who should update the Sprint Backlog during the Sprint?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The Developers.", "explanation": "\"The Sprint Backlog is a plan by and for the Developers\". - Scrum Guide v2020. Although the Developers collaborate with the rest of the Scrum Team during the Sprint, they are responsible for managing the Sprint Backlog." }, { "content": "The Product Owner.", "explanation": "" }, { "content": "The Scrum Team.", "explanation": "" }, { "content": "The Scrum Master.", "explanation": "" } ] }, { "title": "What is expected from the Developers to deliver by the end of the Sprint to the Product Owner?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "At least one usable “done” Increment.", "explanation": "\"Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint\". - Scrum Guide v2020." }, { "content": "A list of done and incomplete items.", "explanation": "" }, { "content": "A full status report regarding the Sprint.", "explanation": "" }, { "content": "A working “done” Increment containing all the work selected for the Sprint.", "explanation": "The scope of the Sprint is negotiable. The focus is on reaching the Sprint Goal, not completing all the work in the Sprint Backlog." } ] }, { "title": "When using Scrum, it is possible to create multiple Product Increments during a single Sprint.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "\"Multiple Increments may be created within a Sprint\" - Scrum Guide." }, { "content": "False.", "explanation": "" } ] }, { "title": "If the Product Backlog is clear and refined, the Product Owner may choose not to attend the Sprint Planning meeting.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "The entire Scrum Team is required to attend. \"Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team\". - Scrum Guide v2020." }, { "content": "True.", "explanation": "" } ] }, { "title": "The Daily Scrum represents a formal opportunity for the Product Owner to inspect the Sprint progress and provide the Developers with the latest business updates.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "The Product Owner does not attend the Daily Scrum unless they are also doing work from the Sprint Backlog. The purpose of the Daily Scrum is to sync the development efforts and help reach the Sprint Goal. " }, { "content": "True.", "explanation": "" } ] }, { "title": "As soon as the Developers finish the work on a Product Backlog Item that meets the Definition of Done, a new Increment is born.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "\"The moment a Product Backlog item meets the Definition of Done, an Increment is born\". - Scrum Guide v2020." }, { "content": "False.", "explanation": "" } ] }, { "title": "Based on which criteria should the Product Owner order the items in the Product Backlog?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Whatever the Product Owner deems as relevant to optimize value.", "explanation": "The job of the Product Owner is to focus on delivering as much value as possible. The Product Owner does this by ordering the Product Backlog. How this is done is totally up to the Product Owner." }, { "content": "Risk.", "explanation": "" }, { "content": "Business value.", "explanation": "" }, { "content": "Urgency.", "explanation": "" }, { "content": "Effort.", "explanation": "" }, { "content": "Cost of implementation", "explanation": "" }, { "content": "The opinion of the key Stakeholders.", "explanation": "" }, { "content": "Potential revenue", "explanation": "" } ] }, { "title": "If the Product Owner is not sufficiently available for the Scrum Team, the Product Increment may not be what the Product Owner expected at the beginning of the Sprint.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "The main idea is that the Product Owner should be available to work with the Developers during the Sprint. This may include clarifying Product Backlog Items, answering questions, reviewing complete work, or refining the Product Backlog." }, { "content": "False.", "explanation": "" } ] }, { "title": "Why does the Scrum Team need a Product Goal?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The Product Goal helps guide the Scrum Team over multiple Sprints. Every Sprint Goal is a step toward reaching the Product Goal.", "explanation": "" }, { "content": "A Product Goal is optional if the Product Owner has already defined a Product Vision.", "explanation": "The Product Goal may be part of a broader Product Vision, but it remains a mandatory part of the Scrum framework." }, { "content": "A Product Goal is optional if the Product Backlog is complete, transparent, and ordered.", "explanation": "The Product Goal is not optional. The Product Backlog is never complete." } ] }, { "title": "When multiple Scrum Teams work on the same Product, they may have different Product Goals.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "\"If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner\". - Scrum Guide v2020." }, { "content": "True.", "explanation": "" } ] }, { "title": "The Scrum Team is accountable for creating at least one Product Increment with every Sprint. What does \"done\" mean in this context?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "\"Done\" work that is immediately releasable to customers.", "explanation": "" }, { "content": "The Product Owner decides when the Product Increment is \"done\".", "explanation": "The entire Scrum Team decides this based on the Definition of Done." }, { "content": "\"Done\" represents all the development work that is possible within the duration of the Sprint.", "explanation": "\"Done\" is related to the Definition of Done, not to the capacity of the Scrum Team or the amount of work they can handle." }, { "content": "The last Increment created in the Sprint must contain all the work selected during the Sprint Planning event.", "explanation": "The focus is on reaching the Sprint Goal, not completing all the work in the Sprint Backlog." } ] }, { "title": "The Scrum Team must release at least one Increment with every Sprint.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "While frequent releases are desirable, it is up to the Scrum Team to decide when this should happen. Don't confuse the term 'building' with 'releasing.' The Scrum Team can build an Increment according to the Definition of Done (meaning that the Increment is releasable) without actually releasing it." }, { "content": "True", "explanation": "" } ] }, { "title": "Which of the following are considered outputs of the Sprint Planning meeting?", "kind": "multiple", "resolution": [ 0, 1 ], "answers": [ { "content": "The Sprint Backlog.", "explanation": "" }, { "content": "The Sprint Goal.", "explanation": "" }, { "content": "The duration of the Sprint.", "explanation": "This is not a topic of discussion during the Sprint Planning event. The duration of the Sprints should remain constant throughout the development effort." }, { "content": "An updated Product Backlog.", "explanation": "Updating the Product Backlog may happen during the Sprint Review meeting, during a refinement session, or anytime else during the Sprint. The focus of the Sprint Planning meeting is not on the Product Backlog. Even if items are selected from the Product Backlog, this does not constitute an output." }, { "content": "An updated Product Goal.", "explanation": "This is not a topic of discussion during the Sprint Planning event." }, { "content": "An updated release plan.", "explanation": "This is not a topic of discussion during the Sprint Planning event." }, { "content": "An updated Definition of Done.", "explanation": "This is not a topic of discussion during the Sprint Planning event. The Scrum Team may use the Sprint Retrospective to adapt the Definition of Done." } ] }, { "title": "A Project Manager from the Project Management Office in the organization is a good fit for taking the Scrum Master responsibility.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "Typically this is not the case." }, { "content": "True.", "explanation": "" } ] }, { "title": "The Sprint Review is the only chance for the Stakeholders to provide feedback and bring new ideas for the Product Backlog.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "The Sprint Review is just a formal opportunity to do that, but they can collaborate with the Product Owner anytime during the Sprint. " }, { "content": "True.", "explanation": "" } ] }, { "title": "What is the recommended size of the Scrum Team?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "10 or fewer people.", "explanation": "\"The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people\". - Scrum Guide v2020." }, { "content": "At least 3 people but not more than 9.", "explanation": "" }, { "content": "At least two Developers, one Scrum Master and one Product Owner.", "explanation": "" }, { "content": "8 plus/minus 2", "explanation": "" } ] }, { "title": "External dependencies may influence the order of the Product Backlog.", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "External dependencies may influence the Product Owner when ordering the Product Backlog, but it is not the only factor that will be considered. This is not the same as saying the Product Backlog is ordered by dependencies." }, { "content": "False.", "explanation": "" } ] }, { "title": "The best way for the Product Owner to make sure the Product Backlog Items selected for the Sprint are clear is by attending the Daily Scrum and immediately clarifying any doubts.", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "The Product Owner does not attend the Daily Scrum. Details can be clarified anytime during the day." }, { "content": "True.", "explanation": "" } ] }, { "title": "How is the Scrum Master involved in the Sprint Retrospective event?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The Scrum Master participates as a Scrum Team member.", "explanation": "" }, { "content": "The Scrum Master should prepare the event but stay away from discussions.", "explanation": "" }, { "content": "The Scrum Master should take notes and document all decisions.", "explanation": "" }, { "content": "The Scrum Master should not attend so that the rest of the team can discuss freely.", "explanation": "" } ] }, { "title": "Which of the following Scrum events have a time-box?", "kind": "multiple", "resolution": [ 0 ], "answers": [ { "content": "Sprint Review.", "explanation": "" }, { "content": "Release planning.", "explanation": "This is not a Scrum event. Check the Scrum Guide." }, { "content": "Release Retrospective.", "explanation": "This is not a Scrum event. Check the Scrum Guide." }, { "content": "Scrum Retrospective.", "explanation": "This is not a Scrum event. Check the Scrum Guide." }, { "content": "Daily stand-up.", "explanation": "This is a trick answer, and most people get this wrong. Pay attention! While in practice, we often call this meeting Daily stand-up, this is not the official name mentioned by the Scrum Guide. The official name is Daily Scrum. Exam questions are based on the Scrum Guide, not on something else. " } ] }, { "title": "The Definition of Done is essentially the same thing as the acceptance criteria for a Product Backlog Item?", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "False.", "explanation": "Any acceptance criteria are defined to establish if the work performed meets the expectations often in terms of business functionality. The Definition of Done specifies the level of quality that the Product Increment should have." }, { "content": "True.", "explanation": "" } ] }, { "title": "What happens as soon as a Sprint ends?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "A new Sprint starts.", "explanation": "\"A new Sprint starts immediately after the conclusion of the previous Sprint\". - Scrum Guide v2020." }, { "content": "The testers verify the Increment.", "explanation": "" }, { "content": "The Scrum Team releases the Increment.", "explanation": "" }, { "content": "The Scrum Team uses the short pause to refine the Product Backlog.", "explanation": "There are no pauses between Sprints." }, { "content": "The Product Owner inspects the work and can accept or reject the Increment.", "explanation": "The Product Owner does not accept or reject work. The Product Owner does not need to wait for the Sprint to end to inspect the work. It is expected that the Product Owner and the rest of the Scrum Team collaborate throughout the Sprint." } ] }, { "title": "Scrum does not permit releasing during the Sprint. What is the reason for this?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There is no such requirement in Scrum. ", "explanation": "" }, { "content": "The Increment has not been demonstrated to the Stakeholders.", "explanation": "\" The Sprint Review should never be considered a gate to releasing value\". - Scrum Guide v2020." }, { "content": "The Increment has not been demonstrated to the Stakeholders and accepted by the Product Owner.", "explanation": "\" The Sprint Review should never be considered a gate to releasing value\". - Scrum Guide v2020." }, { "content": "Releasing would take the focus away from reaching the Sprint Goal.", "explanation": "While reaching the Sprint Goal is important, without releasing, the Increment does not reach the end-users." } ] }, { "title": "How does Scrum help mitigate risk?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Every Sprint must produce at least one working and potentially releasable Increment.", "explanation": "The best way to reduce risk is by building small Increments and releasing as often as possible to get feedback." }, { "content": "The Product Owner is responsible for making sure the Product is built on time and budget.", "explanation": "" }, { "content": "The Product Owner accurately measures the remaining risk, at least once per Sprint.", "explanation": "" }, { "content": "The Developers helps the Product Owner understand which releases are risky and plan a Release Sprint to account for any issues.", "explanation": "" } ] }, { "title": "Scrum is founded on ________________", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "Empiricism.", "explanation": "" }, { "content": "Lean thinking.", "explanation": "" }, { "content": "Intuition.", "explanation": "" }, { "content": "Best practices in product management.", "explanation": "" }, { "content": "Agile best practices.", "explanation": "" } ] }, { "title": "Which two of the following best describe a Product Backlog Item?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "Can be renegotiated during the Sprint.", "explanation": "" }, { "content": "Typically has attributes such as description and size.", "explanation": "" }, { "content": "It is a contract between the Product Owner and the Developers.", "explanation": "A Product Backlog Item is NOT a contract. The Product Owner and the Developers collaborate on what needs to be done during the Sprint." }, { "content": "Must have clear and immutable test criteria.", "explanation": "The Product Backlog Items can be modified during the Sprint." }, { "content": "The Product Owner determines the size.", "explanation": "The Developers are responsible for estimation." } ] }, { "title": "Empiricism is the same thing as _____", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "the empirical process control theory", "explanation": "Scrum is founded on empiricism or the empirical process control theory." }, { "content": "Scrum.", "explanation": "" }, { "content": "Agile.", "explanation": "" }, { "content": "the Cynefin framework.", "explanation": "" } ] }, { "title": "After how many Sprints does the Integration Sprint take place?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There are no Integration Sprints in Scrum.", "explanation": "" }, { "content": "When the Product Owner decides.", "explanation": "" }, { "content": "Before releasing.", "explanation": "" }, { "content": "Typically after two Sprints.", "explanation": "" } ] }, { "title": "Outputs and outcomes in Scrum are the same thing.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "Outputs and outcomes are not the same thing. You can generate more output in terms of functionality (outputs) but have unhappy customers (outcome). We prefer outcomes over outputs. " } ] }, { "title": "What happens if the Sprint time-box expires and the Sprint Goal is not reached?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "The Sprint ends as planned with the Sprint Review and the Sprint Retrospective.", "explanation": "Missing a Sprint Goal is a normal occurrence in the development process. The risk is limited to a Sprint. The Scrum Team used the Sprint Retrospective to inspect and adapt." }, { "content": "A new Sprint begins with the Sprint Planning meeting.", "explanation": "" }, { "content": "The Sprint continues until the Sprint Goal is reached.", "explanation": "The Sprint cannot be extended." }, { "content": "The Developers need to explain to the Product Owner what they did wrong.", "explanation": "The Developers don't need to report to the Product Owner. If the Sprint Goal has not been reached, this is a concern for the entire Scrum Team." }, { "content": "The next Sprint will have a longer time-box that allows for the Sprint Goal to be reached.", "explanation": "Sprints should have a consistent duration. Failing to reach the Sprint Goal cannot be attributed to the Sprint length." } ] }, { "title": "One of the outcomes of the Sprint Retrospective meeting is a clearly defined Sprint Goal for the Sprint.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "The Scrum Team defines the Sprint Goal during the Sprint Planning meeting." } ] }, { "title": "The Developers can change, add, or remove the Sprint Backlog Items after the Sprint Planning meeting has ended, often in consultation with the Product Owner.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "The Developers will modify the Sprint Backlog throughout the Sprint but will keep the Sprint Goal in mind. Typically, the Developers will collaborate with the Product Owner throughout the Sprint. The main idea is to allow some flexibility. As the Developers work on the Increment, they may discover new things, so the plan needs flexibility." }, { "content": "False.", "explanation": "" } ] }, { "title": "When is the Definition of Done created?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Before the development work of the first Sprint begins.", "explanation": "The Scrum Guide does not provide a meeting for creating the Definition of Done and only explains the need for the Definition of Done. The Definition of Done is required for the Sprint Planning meeting. The Scrum Team should define one before the development work begins." }, { "content": "During every Sprint Planning meeting.", "explanation": "There is no need to create a new Definition of Done for every Sprint." }, { "content": "During the Sprint Retrospective meeting.", "explanation": "The Definition of Done is often updated during the Sprint Retrospective meeting." }, { "content": "During Sprint 0.", "explanation": "" } ] }, { "title": "Which of the following are described in the Scrum Guide?", "kind": "multiple", "resolution": [ 0, 1, 2 ], "answers": [ { "content": "Scrum artifacts", "explanation": "" }, { "content": "Scrum values", "explanation": "" }, { "content": "Scrum Theory", "explanation": "The Scrum Theory section of the Scrum Guide explains the Scrum foundations." }, { "content": "Job titles", "explanation": "The Scrum Guide does not define any job titles." }, { "content": "Scrum roles", "explanation": "The Scrum Guide does not use the term \"roles\" anymore. With the release of the Scrum Guide v2020, we refer to the roles in a Scrum Team as accountabilities." }, { "content": "Reporting duties", "explanation": "The Scrum Guide does not mention any reporting duties but emphasizes the need for transparency." } ] }, { "title": "Which of the following statements are TRUE in regards to the Definition of Done?", "kind": "multiple-three", "resolution": [ 0, 1, 2 ], "answers": [ { "content": "The Increment must adhere to the Definition of Done.", "explanation": "The Definition of Done applies to individual Product Backlog Items and to the Increment." }, { "content": "Each Product Backlog Item completed during the Sprint must comply with the Definition of Done.", "explanation": "The Definition of Done applies to individual Product Backlog Items and to the Increment." }, { "content": "The development organization can define a Definition of Done that all Scrum Teams must follow as a minimum.", "explanation": "" }, { "content": "To increase transparency and reduce confusion, each User Story can have its own Definition of Done.", "explanation": "The Scrum Guide does not talk about User Stories. Every Product Backlog Item must respect the Definition of Done, which is a single one for the Product. If needed, a Product Backlog Item can have an additional characteristic, often called Acceptance Criteria which defines rules relevant only for the respective item." }, { "content": "The Scrum Master's role is to defend and enforce the Definition of Done.", "explanation": "The Scrum Master should coach the Scrum Team on the importance of having and adhering to their Definition of Done. The Scrum Master does not enforce the Scrum rules and punishes those who disobey." } ] }, { "title": "The Developers have been demonstrating completed features to the Product Owner throughout the Sprint. Is this an acceptable practice?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Yes, as it encourages quick feedback.", "explanation": "The Product Owner and the Developers collaborate throughout the Sprint." }, { "content": "No. The Developers need to wait for Sprint Review for any demos.", "explanation": "" }, { "content": "Yes, but only if the Stakeholders are involved.", "explanation": "" } ] }, { "title": "The technical debt in the Product has increased to high levels and is slowing down the development of new features. What should the Scrum Team do?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "Make the existing technical debt transparent.", "explanation": "Transparency is key to handling any problem." }, { "content": "Start working on reducing the technical debt with every Sprint but continue implementing new features.", "explanation": "" }, { "content": "Dedicate the next Sprint to eliminating the technical debt.", "explanation": "Every Sprint should produce some value for the end-users, no matter how small. It is doubtful that the Scrum Team will manage to eliminate the technical debt in the Product. Technical debt needs to be managed, but it is rarely eliminated." }, { "content": "Stop using Scrum. Kanban might be a better fit for this project.", "explanation": "" }, { "content": "Form a dedicated team to handle this problem.", "explanation": "" } ] }, { "title": "Which Scrum events must the Product Owner attend?", "kind": "multiple", "resolution": [ 0, 1 ], "answers": [ { "content": "Sprint Review.", "explanation": "" }, { "content": "Sprint Retrospective.", "explanation": "" }, { "content": "Daily meeting.", "explanation": "" }, { "content": "Refinement sessions.", "explanation": "Refinement is not a Scrum event." }, { "content": "Release Planning.", "explanation": "This is not a Scrum event." } ] }, { "title": "The Scrum Master needs to attend every Daily Scrum to ensure it does not go over the time-box.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "The Scrum Master does not attend the Daily Scrum. Should the Scrum Master notice that the Daily Scrum goes over the time-box, they will coach the Developers on how to keep it within the time-box." } ] }, { "title": "The Sprint Goal cannot be changed once the Sprint Planning meeting has concluded.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "Once the Sprint has started, the Scrum Team will try to reach the Sprint Goal. Since every Sprint is relatively short, it is implausible for the Sprint Goal to become obsolete. However, if this happens, the Product Owner could decide to cancel the Sprint." }, { "content": "False.", "explanation": "" } ] }, { "title": "The Developers think it is no longer possible to reach the Sprint Goal by the end of the Sprint. What should happen next?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The Scrum Team should try to reach the Sprint Goal until the last day of the Sprint.", "explanation": "" }, { "content": "The Sprint should be extended.", "explanation": "The Sprint can't go over the predefined length." }, { "content": "The Sprint should be canceled.", "explanation": "The Sprint can be canceled if the Sprint Goal is obsolete. There is no indication that this is the case." }, { "content": "The Sprint Goal should be changed to something achievable.", "explanation": "Once the Sprint Planning meeting has ended, it is not possible to change the Sprint Goal." } ] }, { "title": "When is the correct time to end the Sprint Review meeting?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There is no correct time to end a meeting.", "explanation": "There is no such thing as the \"correct\" time to start and especially end a meeting. Pay attention to the language used here. Every Sprint Review event should begin as scheduled. The event will end when the event's purpose has been reached before the time-box expires. If the meeting has achieved its objective, the event ends." }, { "content": "When the Scrum Master decides to end the meeting.", "explanation": "" }, { "content": "After 4-hours.", "explanation": "Don't confuse this answer with the event time-box. The Sprint Review can end sooner than 4-hours." }, { "content": "After the Scrum Team has demonstrated the Increment and gathered feedback.", "explanation": "" } ] }, { "title": "The Scrum Guide describes all the project stages and explains who should consult with whom to ensure the delivery is on time and within budget.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "Scrum is a framework, not a methodology that tells you what to do step by step." } ] }, { "title": "What is the aim of the Product Backlog refinement activity?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "To refine the Product Backlog Items for the upcoming Sprint.", "explanation": "" }, { "content": "To clarify and break down the Product Backlog Items for the current Sprint.", "explanation": "This activity has nothing to do with the current Sprint and focuses solely on preparing the upcoming Sprints. The work for the current Sprint is in the Sprint Backlog, not in the Product Backlog." }, { "content": "To refine the Sprint Goal and ensure it is reachable.", "explanation": "" } ] }, { "title": "The Product Owner does not have the authority to cancel the Sprint Review if no Increment is ready. Only the Scrum Master can decide this.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "Nobody can cancel Scrum events (with the exception of the Product Owner who can cancel the entire Sprint). Scrum events are an integral part of the Scrum framework and cannot be canceled or postponed. They must always take place." } ] }, { "title": "The Scrum Team can decide to release an Increment before the Sprint Review meeting.", "kind": "true-false", "resolution": [ 0 ], "answers": [ { "content": "True.", "explanation": "The Scrum Team can decide to release new features ANYTIME during the Sprint, as long as their work adheres to the Definition of Done." }, { "content": "False.", "explanation": "" } ] }, { "title": "A Scrum Team cannot produce a releasable Increment in every Sprint because the client handles all testing. What should the Scrum Master do in this situation?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "Make this impediment transparent and bring the Scrum Team and the client together to find a solution.", "explanation": "" }, { "content": "Coach the client that testing is still development work that needs to be done by the Scrum Team.", "explanation": "" }, { "content": "Modify the Definition of Done to exclude testing. ", "explanation": "" }, { "content": "Test the Increment before handing it over to the client.", "explanation": "" }, { "content": "Encourage the Scrum Team to release the Increment without testing.", "explanation": "" } ] }, { "title": "Why do the Developers have the Daily Scrum meeting?", "kind": "multiple", "resolution": [ 0, 1 ], "answers": [ { "content": "To inspect the work done since the last Daily Scrum.", "explanation": "During Daily Scrums, the Developers evaluate progress towards the Sprint Goal, identify impediments, and adjust their plan for the remaining work." }, { "content": "To adapt the Sprint Backlog.", "explanation": "The Sprint Backlog contains the plan for the Sprint. During Daily Scrums, the Developers evaluate progress towards the Sprint Goal, identify impediments, and adjust their plan for the remaining work." }, { "content": "To sync with the Product Owner.", "explanation": "The Product Owner does not attend the Daily Scrum." }, { "content": "To tell the Scrum Master which impediments need to be resolved.", "explanation": "The Developers can use the Daily Scrum to identify impediments, but these are communicated only after the meeting since the Scrum Master does not attend." }, { "content": "To inform the Stakeholders about the progress made.", "explanation": "The Developers don't need to inform the Stakeholders about their actions and decisions. Since the Sprint Backlog is transparent, the Stakeholders can inspect the progress made." } ] }, { "title": "One of the items in the Product Backlog has technical dependencies on other items in the Product Backlog. How can the Scrum Team ensure that this item won't be selected during a Sprint Planning event before the dependencies have been addressed?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "By making any dependencies transparent in the Product Backlog.", "explanation": "The team has Product Backlog refinement sessions. If there are dependencies, the Scrum Team identifies them and finds ways to make them transparent. Remember, the Product Backlog needs to be transparent. This means everyone has a shared understanding of the work, including any dependencies. Also, during Sprint Planning, the entire Scrum Team attends, so there is a low chance of picking something with dependencies." }, { "content": "By having the Lead Developer attend the Sprint Planning meeting.", "explanation": "There is no Lead Developer in Scrum." }, { "content": "By removing the item from the Product Backlog and putting it on a standby list.", "explanation": "The Product Backlog is the single source of requirements for the Product. The Scrum Team should not use other backlogs or lists." }, { "content": "By removing all dependencies that the item has. In Scrum, items must be independent.", "explanation": "While we try as much as possible to have independent items, this is not always possible and not a requirement in Scrum." } ] }, { "title": "Some key Stakeholders have more important meetings to attend and have made a habit of not attending the Sprint Review. Under which circumstances is this acceptable?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There is no reason for the Stakeholders not to attend.", "explanation": "Sprint Review is a mandatory meeting, and the relevant Stakeholders need to attend. If they don't, the feedback loop is not closed. From a Scrum perspective, there is nothing more important for the Stakeholders than the Sprint Review meeting. In practice, the Sprint Review date is known well in advance, and the Stakeholders can plan for attending this event." }, { "content": "When the Scrum Master organizes an additional Sprint Review at a different time, that works for the absent Stakeholders.", "explanation": "Mandatory Scrum events are not rescheduled or postponed. The need to take place as scheduled." }, { "content": "When the absent Stakeholders collaborate with the Scrum Team during the Sprint to provide feedback.", "explanation": "While there is nothing wrong with Stakeholders collaborating with the Scrum Team during the Sprint, holding a review during the development work undermines the importance of the Sprint Review. It also distracts the Developers from the current Sprint activities." }, { "content": "When the Product Owner collaborates with the Stakeholders after the Sprint Review and keeps them informed of the progress made.", "explanation": "There is no replacement for the Sprint Review meeting." } ] }, { "title": "During the Product Backlog refinement activity, the Developers typically decompose the work into smaller units of work, often called tasks.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "Tasks and items are different concepts. Product Backlog refinement happens in preparation for the upcoming Sprints. It is a refinement of the Product Backlog. This ongoing activity during the Sprint has nothing to do with the scope of the current Sprint. The Scrum Guide describes the refinement activity as follows: \"Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items.\". During refinement, larger items are refined into smaller items. Refining work is not the same as decomposing work. The decomposition of work, sometimes called task breakdown, happens at the beginning of each Sprint during the Sprint Planning meeting. Each Product Backlog Item in the Sprint Backlog is decomposed into smaller units of work, which we usually call tasks." } ] }, { "title": "One of the Developers on the Scrum Team has identified an issue with one of the items in the Sprint Backlog. When is the best time to clarify the requirements with the Product Owner?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "As soon as possible.", "explanation": "There is no need for a formal Scrum event for the Scrum Team to collaborate. Any issues in the Sprint Backlog can impact the Sprint Goal and should be dealt with as soon as possible." }, { "content": "During the next Daily Scrum.", "explanation": "The Product Owner does not attend the Daily Scrum." }, { "content": "This is decided by the Scrum Master and only after an impediment has been raised and documented in the project management software.", "explanation": "While the Scrum Master can facilitate finding a solution, they are not deciding when this should happen. Also, Scrum does not impose using software for managing work or impediments." }, { "content": "During the next Product Backlog refinement activity.", "explanation": "Product Backlog refinement happens in preparation for the upcoming Sprints. It is a refinement of the Product Backlog. This ongoing activity during the Sprint has nothing to do with the scope of the current Sprint as it refines the Product Backlog, not the Sprint Backlog, which already contains refined items." }, { "content": "During the Sprint Retrospective.", "explanation": "This would be too late as the Sprint would already be over." } ] }, { "title": "Two Scrum Teams within the same organization are developing two separate Products using Scrum. How many Definitions of Done are needed?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Two.", "explanation": "There are two Products, so we need two Definitions of Done, one for each Product. The Definition of Done is connected to the Product, not to how many teams work on that Product." }, { "content": "None.", "explanation": "" }, { "content": "One.", "explanation": "" }, { "content": "This is decided by the developing organization.", "explanation": "While the organization might have standards that need to be followed, this aspect does not dictate how many Definitions of Done are needed." } ] }, { "title": "A Scrum Team builds and releases multiple Product Increments in a Sprint. The Sprint Review meeting takes place every two weeks. Is this product development effort suitable for Scrum?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Yes. The Scrum Team can build and release multiple Increments in a Sprint.", "explanation": "Some organizations build and release software multiple times per day. In a Sprint, there can be 100 releases. Feedback comes in all the time. It is not limited to the Sprint Review. The Product Owner and Stakeholders collaborate all the time. The Sprint Review is just a prescribed opportunity to ensure this collaboration happens at least once per Sprint." }, { "content": "Yes. The Scrum Team can build and release multiple Increments in a Sprint, but the Stakeholders need to be involved in the process.", "explanation": "" }, { "content": "No. The Scrum Team can build as many Increments as they wish but need approval from the Stakeholders to release.", "explanation": "" }, { "content": "No. The Scrum Team can only release once per Sprint after the work has been signed off during Sprint Review.", "explanation": "" } ] }, { "title": "Which of the following are valid reasons for the Scrum Master to attend Daily Scrum?", "kind": "multiple", "resolution": [ 0 ], "answers": [ { "content": "The Scrum Master does not attend the Daily Scrum.", "explanation": "The Daily Scrum is a meeting for the Developers. The Scrum Master has no role in this meeting." }, { "content": "To learn about new impediments.", "explanation": "The Scrum Master can learn about new impediments immediately after the meeting. The Scrum Team does not need a Scrum event to collaborate and exchange information. This happens throughout the day." }, { "content": "To ask the Developers what they did yesterday and learn about their plans for today.", "explanation": "The Developers are self-managing and can decide on their own how to structure the meeting and which discussions to have." }, { "content": "To ensure the meeting remains within the timebox.", "explanation": "The Scrum Master does not need to attend the Daily Scrum. The Scrum Master can coach the Developers on techniques to help them keep the meeting within the timebox outside the Daily Scrum." }, { "content": "To ensure the meeting takes place.", "explanation": "The Scrum Master is not the Scrum police to verify what the Developers are doing. If the Developers don't have the Daily Scrum as prescribed, the Scrum Master will learn about this even if not present." } ] }, { "title": "Which of the following statements are true about commitment in Scrum?", "kind": "multiple-four", "resolution": [ 0, 1, 2, 3 ], "answers": [ { "content": "The Scrum Team collaborates and finds solutions to reach the Sprint Goal by the end of the Sprint.", "explanation": "" }, { "content": "The Product Goal is a commitment to the Product Backlog.", "explanation": "" }, { "content": "Each Scrum artifact contains a commitment.", "explanation": "" }, { "content": "The Scrum Team is committed to supporting each other.", "explanation": "" }, { "content": "The Definition of Done is a commitment for the Sprint Backlog.", "explanation": "The Definition of Done is a commitment for Increment." }, { "content": "The Developers are completing all the items in the Sprint Backlog by the end of the Sprint.", "explanation": "The Developers are not committed to completing all the work selected for the Sprint. It is possible to reach with Sprint Goal without completing all the items in the Sprint Backlog." }, { "content": "The Developers are committed to a stable and predictable velocity Sprint after Sprint.", "explanation": "Scrum does not have velocity goals." } ] }, { "title": "The Developers notice that some items in the Product Backlog require more time than the Sprint length. What should happen next?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "The Scrum Team should use the Product Backlog refinement activity to refine the items.", "explanation": "All work in the Product Backlog needs to be small enough to fit in one Sprint. Ideally, items in the Product Backlog should be as small as possible. This happens through the Product Backlog refinement activities." }, { "content": "The Scrum Team should discuss and increase the Sprint length.", "explanation": "The Sprint length is fixed. This is not a valid reason to change it." }, { "content": "The Developers should raise an impediment with the Scrum Master.", "explanation": "This is not an impediment as it is something that the Scrum Team can solve on its own." }, { "content": "The Product Owner should cancel the Sprint and organize a Product Backlog refinement meeting.", "explanation": "This is not a valid reason for canceling the Sprint." }, { "content": "The Developers should ask the Scrum Master to extend the Sprint length for this occasion.", "explanation": "The Scrum Master is there to educate the Scrum Team on how to use Scrum properly. The Scrum Master can't bend the Scrum rules." } ] }, { "title": "What are examples of activities the Scrum Master does for the Scrum Team?", "kind": "multiple-four", "resolution": [ 0, 1, 2, 3 ], "answers": [ { "content": "Facilitates the Sprint Review meetings to review the work completed during the Sprint and demonstrate the progress made to the Stakeholders.", "explanation": "The purpose of Sprint Review in Scrum is to evaluate progress and demonstrate completed work to stakeholders, receive feedback and ensure alignment with goals and vision." }, { "content": "Facilitates the Sprint Retrospective meetings to help the team reflect on the previous Sprint and identify areas for improvement.", "explanation": "" }, { "content": "Works with the Product Owner to help them understand and order the Product Backlog.", "explanation": "One of the ways that the Scrum Master serves the Product Owner is by assisting with techniques for defining an effective Product Goal and managing the Product Backlog." }, { "content": "Coaches the Scrum Team and the organization on the Scrum framework.", "explanation": "The Scrum Master plays a vital role in helping the Scrum Team and the organization adopt Scrum, including by providing leadership, training, and coaching." }, { "content": "Facilitates the Daily Stand-up meetings to ensure that the team stays on track and communicates any impediments that may arise.", "explanation": "Even if the term stand-up meeting or daily stand-up is widespread, the Scrum Guide refers to this meeting as Daily Scrum." }, { "content": "Facilitates the Sprint Planning meetings to help the team plan and commit to a fixed set of items for the upcoming Sprint.", "explanation": "The Scrum Team commits to reaching the Sprint Goal, not a fixed scope." }, { "content": "Protects the Scrum Team from external distractions and interruptions to help them stay focused on the work at hand.", "explanation": "The Scrum Guide does not mention any responsibilities the Scrum Master would have in this regard. Protecting the team is not part of the Scrum Master's accountability. The Scrum Master should coach the Scrum Team to self-manage and deal with distractions and interruptions themselves." } ] }, { "title": "What is a typical activity for the Scrum Team between the end of Sprint and the Sprint Planning event of the new Sprint?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There are no such activities.", "explanation": "The Sprint starts with Sprint Planning, so no activities are possible." }, { "content": "Product Backlog refinement.", "explanation": "" }, { "content": "Releasing the Increment.", "explanation": "" }, { "content": "Testing the Increment.", "explanation": "" }, { "content": "Getting feedback from the users of the Product.", "explanation": "" } ] }, { "title": "In the middle of the Sprint, the Developers realize that they can't build an Increment and that the Sprint Goal won't be reached. What should happen next?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "The Scrum Team self-manages and tries to find a way to reach the Sprint Goal.", "explanation": "The Scrum Team should try to build an Increment and reach the Sprint Goal until the last day of the Sprint." }, { "content": "The Scrum Team continues working on the Increment until Sprint timebox expires.", "explanation": "This situation is a normal occurance, and there is no reason to end the Sprint sooner. So the Sprint continues as planned." }, { "content": "The Sprint should be canceled as the Sprint Goal is obsolete.", "explanation": "Obsolete means that the Sprint Goal no longer makes sense. It does not mean that the Sprint Goal is no longer achievable." }, { "content": "The Scrum Team should revise the Sprint Goal to something achievable.", "explanation": "After the Sprint Planning meeting has ended, the Sprint Goal can't be changed." }, { "content": "The Scrum Team should adjust the Definition of Done to make it easier for them to build the Increment.", "explanation": "The Definition of Done should not be modified during the Sprint. During the Sprin the quality of the work does not decrease. The only opportunity to do so is at the end of the Sprint during the Sprint Retrospective." } ] }, { "title": "One of the developers is slacking and acting in a non-professional way and this has a negative impact on the Sprint outcome. Who is accountable for this situation?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "All Developers.", "explanation": "The Scrum Guide explains that the Developers are accountable for \"holding each other accountable as professionals.\" - Scrum Guide v2020." }, { "content": "Only the Developer who is acting non-professionally.", "explanation": "" }, { "content": "The Scrum Master for not removing the Developer from the team.", "explanation": "" }, { "content": "The Product Owner for not cancelling the Sprint in a timely manner.", "explanation": "" } ] }, { "title": "During the Daily Scrum, one of the questions Developers must address is what they've accomplished in the past 24 hours.", "kind": "true-false", "resolution": [ 1 ], "answers": [ { "content": "True.", "explanation": "" }, { "content": "False.", "explanation": "Earlier versions of the Scrum Guide provided example questions for Developers during the Daily Scrum. However, these were removed in the 2020 edition. Now, it's up to the Developers to determine how to conduct the Daily Scrum event. While such questions can be used, they aren't mandatory." } ] }, { "title": " From which of the following artifacts is transparency over the scope of the current Sprint primarily gained?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "Sprint Backlog", "explanation": "The Sprint Backlog is the artifact that provides transparency over the scope of the current Sprint. The Sprint Backlog includes a Sprint Goal, a set of Product Backlog items selected for the Sprint, plus a plan for delivering them. This makes it the primary source of information regarding what will be worked on during the Sprint, thus ensuring clarity and transparency about the scope and work to be done." }, { "content": "Product Backlog", "explanation": "" }, { "content": "Daily Scrum", "explanation": "This is a Scrum event, not an artifact." }, { "content": "Sprint Review", "explanation": "This is a Scrum event, not an artifact." } ] }, { "title": "What does the following statement mean: \"The Product Backlog is the single source of work undertaken by the Scrum Team.\"?", "kind": "multiple-two", "resolution": [ 0, 1 ], "answers": [ { "content": "New product requirements must go through the Product Backlog.", "explanation": "" }, { "content": "There are no other backlogs for capturing requirements (such as a separate technical Product Backlog).", "explanation": "" }, { "content": "Using the Sprint Backlog is optional.", "explanation": "" }, { "content": "The Developers can work on items not part of the Product Backlog if the Product Owner instructs them to do so.", "explanation": "" }, { "content": "Anyone can add items to the Product Backlog without consulting the Product Owner.", "explanation": "" }, { "content": "The Product Backlog is only for User Stories, while technical tasks are managed in a separate backlog.", "explanation": "" } ] }, { "title": "Which of the following concepts are described by the Scrum Guide?", "kind": "multiple", "resolution": [ 0, 1, 2 ], "answers": [ { "content": "Sprint Planning", "explanation": "" }, { "content": "Scrum Artifacts", "explanation": "" }, { "content": "Lean thinking", "explanation": "" }, { "content": "Scrum Goal", "explanation": "There is no Scrum Goal. Only a Product Goal and a Sprint Goal. Which one do you mean?" }, { "content": "Daily stand-up.", "explanation": "The Scrum Guide refers to this meeting as Daily Scrum." }, { "content": "Product Backlog grooming", "explanation": "The Scrum Guide refers to this activity as Product Backlog refinement." } ] }, { "title": "How is the Quality Assurance team involved in a Sprint?", "kind": "single", "resolution": [ 0 ], "answers": [ { "content": "There is no QA team in Scrum.", "explanation": " In Scrum, the is no QA team, only the Scrum Team which is also responsible for Quality Assurance (QA) or anything else that is needed. Testing is done throughout the Sprint." }, { "content": "They test new features immediately after they have been received from the Scrum Team.", "explanation": "" }, { "content": "They test new features at the end of the Sprint but before Sprint Review.", "explanation": "" }, { "content": "They test new features after the Sprint as ended but before they are released to the end-users.", "explanation": "" } ] } ]