Question 1Skipped<\/p>\n
True or false? When multiple teams are working on the same product, their Sprints should start and end at the same time.<\/p>\n
TRUE<\/p>\n
Correct answer<\/p>\n
FALSE<\/p>\n
Overall explanation<\/p>\n
FALSE, it’s not mandatory to start and end the Sprints at the same time; e.g., most teams have four-week Sprints, but some of them have two-week Sprints.<\/p>\n
Question 2Skipped<\/p>\n
Which of the following apse might help the Product Owner minimize waste in developing and sustaining the Product Backlog? (choose the best two answers)<\/p>\n
Correct selection<\/p>\n
Only fully describe Product Backlog items when it seems likely they will be implemented.<\/p>\n
Correct selection<\/p>\n
Write every Product Backlog item clearly and with no ambiguity.<\/p>\n
Hand off ownership of the Product Backlog to someone else.<\/p>\n
Remove items from the Product Backlog that have not been addressed in a long time.<\/p>\n
Overall explanation<\/p>\n
Hand off ownership of the Product Backlog to someone else, Remove items from the Product Backlog that have not been addressed in a long time are simply not an option and incorrect in scrum framework.<\/p>\n
Question 3Skipped<\/p>\n
Every Scrum team must determine its own cadence for releasing features to customers. Some choose to release every sprint, while others after 2, 3 and even more Sprints. But who is responsible for planning releases?<\/p>\n
Choose only ONE best answer.<\/p>\n
Developer<\/p>\n
Scrum Master<\/p>\n
Correct answer<\/p>\n
Product Owner<\/p>\n
Project manager<\/p>\n
Overall explanation<\/p>\n
Release Planning is the Responsibility of the Product Owner.<\/p>\n
Question 4Skipped<\/p>\n
From the following answers choose one. In Scrum, by transparency we mean …….<\/p>\n
Choose only ONE best answer.<\/p>\n
The process should be visible and understood by each stakeholder<\/p>\n
The whole process should be visible to the Product Owner<\/p>\n
Correct answer<\/p>\n
Significant aspects of the process must be visible to those performing the work as well as those receiving the work<\/p>\n
The whole process should be visible to stakeholders.<\/p>\n
Overall explanation<\/p>\n
Transparency is about visibility and doesn\u2019t contain understanding; even though we\u2019d better try our best to create the right understanding too, but that\u2019s another story. The \u201cwhole process\u201d might be too much for some stakeholders; \u201csignificant aspects\u201d is enough, as we treat most things in Agile environments.<\/p>\n
Question 5Skipped<\/p>\n
The benefits of having a solid product vision are (choose 3 answers)<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
It gives an overall direction to the Sprints<\/p>\n
It helps identify the best time for releasing the product<\/p>\n
It\u2019s a traditional concept, and there are no benefits for it<\/p>\n
Correct selection<\/p>\n
It makes it easier to inspect the incremental progress of the product<\/p>\n
Correct selection<\/p>\n
It helps the team stay focused and make better decisions<\/p>\n
Overall explanation<\/p>\n
Product vision is not explained in the Scrum Guide and is not a mandatory part of the framework. However, it\u2019s recommended to have one, and use it to help align the decisions and development with the expected outcome of the project<\/p>\n
Question 6Skipped<\/p>\n
The Team may decrease the technical debt by ……<\/p>\n
Choose only ONE best answer.<\/p>\n
Hiring an external auditor<\/p>\n
Correct answer<\/p>\n
Improving the definition of \u201cDone\u201d<\/p>\n
Having hardening Sprints<\/p>\n
Hiring more Developers<\/p>\n
Overall explanation<\/p>\n
There\u2019s usually room for improving the definition of \u201cDone\u201d. A good definition will let less<\/p>\n
technical debt pass on to the next Sprints. Technical debt is minor shortcomings in the code<\/p>\n
that makes it less than \u201cgood enough\u201d, and therefore creates risks in the future. It usually<\/p>\n
decreases velocity in the future (because the team has to fix the shortcomings), and as some<\/p>\n
of the debt might remain in the final product, the maintenance cost will increase as well.<\/p>\n
Another Agile way of reducing technical debt is continuous refactoring.<\/p>\n
Question 7Skipped<\/p>\n
Which of the following is not a pillar of Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct selection<\/p>\n
Adaptation<\/p>\n
Correct selection<\/p>\n
Inspection<\/p>\n
Empiricism<\/p>\n
Correct selection<\/p>\n
Transparency<\/p>\n
Overall explanation<\/p>\n
Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.<\/p>\n
Question 8Skipped<\/p>\n
Choose one best answer. Scrum is<\/p>\n
Choose only ONE best answer.<\/p>\n
not founded on empiricism<\/p>\n
Correct answer<\/p>\n
not a software development process<\/p>\n
not founded on lean thinking<\/p>\n
not a framework<\/p>\n
Overall explanation<\/p>\n
Scrum is not a software development process<\/p>\n
Question 9Skipped<\/p>\n
Scrum is a software development methodology<\/p>\n
Choose only ONE best answer.<\/p>\n
True<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
Scrum is a process framework that has been used to manage work on complex products since the early 1990s. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.<\/p>\n
Question 10Skipped<\/p>\n
According to the Scrum Guide, the Scrum is based on\u00a0 \u00a0(Select all correct answers)<\/p>\n
Choose ALL answers that apply.<\/p>\n
Self-organizing<\/p>\n
Correct selection<\/p>\n
Lean thinking<\/p>\n
Transparent<\/p>\n
Correct selection<\/p>\n
Empirical<\/p>\n
Complex<\/p>\n
Overall explanation<\/p>\n
Scrum is founded on empirical process control theory or empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Lean thinking reduces waste and focuses on the essentials.<\/p>\n
Question 11Skipped<\/p>\n
After Scrum implementation, the Scrum Team ensures the exception of technical debt<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
True<\/p>\n
Overall explanation<\/p>\n
Scrum cannot ensure the exception of technical debt.<\/p>\n
Question 12Skipped<\/p>\n
From the following answers, choose one which is not a prioritization technique<\/p>\n
Choose only ONE best answer.<\/p>\n
Kano analysis<\/p>\n
Product Backlog ordering<\/p>\n
Correct answer<\/p>\n
Planning Poker<\/p>\n
User Story Mapping<\/p>\n
Overall explanation<\/p>\n
Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used to estimate the effort or relative size of development goals in software development. In planning poker, members of the group make estimates by placing numbered cards face-down on the table, instead of saying them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates. Planning Poker is not a prioritization technique<\/p>\n
Question 13Skipped<\/p>\n
Developers are free to change their engineering and testing practices whenever they want.<\/p>\n
Choose only ONE best answer.<\/p>\n
False<\/p>\n
Correct answer<\/p>\n
True<\/p>\n
Overall explanation<\/p>\n
Developers decide how to handle their development, and this decision can evolve during the project, as more is learned about the needs. This is about their development and doesn’t have to be constrained by the Sprints. The elements that shouldn’t be changed during the Sprint are those required for keeping them focused on their development.<\/p>\n
Question 14Skipped<\/p>\n
From the following answers, how should developers deal with system, security or non-functional features?<\/p>\n
Choose only ONE best answer.<\/p>\n
Incorporate them in the hardening Sprint<\/p>\n
Correct answer<\/p>\n
Incorporate them into every Increment<\/p>\n
Incorporate them before the release<\/p>\n
Incorporate them in the integration Sprint<\/p>\n
Overall explanation<\/p>\n
Non-functional features are usually part of the Definition of Done and should be considered for every Product Backlog item and every Increment. Sometimes, some non-functional features that address a very particular part of the software can be added as separate items in the Product Backlog. All Sprints are the same. There’s no Sprint zero, hardening Sprint, release Sprint, integration Sprint, etc.<\/p>\n
Question 15Skipped<\/p>\n
Which of the following, statements are correct about non-functional requirements?<\/p>\n
Correct selection<\/p>\n
They will be in the Sprint Backlog, but not the Product Backlog.<\/p>\n
Correct selection<\/p>\n
They should be incorporated into every increment.<\/p>\n
They will be considered in Integration Sprints.<\/p>\n
Correct selection<\/p>\n
Some of them can be added to the Definition of Done.<\/p>\n
They can be incorporated right before the release about functional requirements<\/p>\n
Overall explanation<\/p>\n
There is no separate Integration sprint in Scrum and functional requirements are not released separately.<\/p>\n
Question 16Skipped<\/p>\n
Who should know the most about the release and product requirements in Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
The Team Leader<\/p>\n
The Scrum Master<\/p>\n
Correct answer<\/p>\n
The Product Owner<\/p>\n
The Project Manager<\/p>\n
The Product Leader<\/p>\n
Overall explanation<\/p>\n
The Product Owner is responsible for the product, including decisions about release. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one can force Developers to work from a different set of requirements.<\/p>\n
Question 17Skipped<\/p>\n
The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.<\/p>\n
(Which one the following answers is FALSE?)<\/p>\n
The Developers may work with the Product Owner to remove or add work if it finds it has more or less capacity than it expected.<\/p>\n
As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.<\/p>\n
Correct answer<\/p>\n
The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.<\/p>\n
The Product Owner can help clarify or optimize the Sprint when asked by the Developers.<\/p>\n
Overall explanation<\/p>\n
The Sprint Backlog makes visible all of the work that the Developers identify as necessary to meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.<\/p>\n
Question 18Skipped<\/p>\n
When many Scrum Teams are working on a single product, what best describes the Definition of Done?<\/p>\n
(choose the best answer)<\/p>\n
It depends.<\/p>\n
Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.<\/p>\n
Correct answer<\/p>\n
All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.<\/p>\n
Overall explanation<\/p>\n
The Increment must be valuable and useful. This means that when many Scrum Teams are working on a single product, they are expected to adhere to a single Definition of Done for the Increment.<\/p>\n
Question 19Skipped<\/p>\n
Which statement best describes a Product Owner’s responsibility?<\/p>\n
(choose the best answer)<\/p>\n
Keep stakeholders from distracting the Developers.<\/p>\n
Correct answer<\/p>\n
Optimizing the value of the work the Scrum Team does.<\/p>\n
Managing the project and ensuring that the work meets the commitments to the stakeholders.<\/p>\n
Directing the Developers.<\/p>\n
Overall explanation<\/p>\n
The Product Owner is accountable for maximizing the value of the product and the work of the Scrum Team.<\/p>\n
Question 20Skipped<\/p>\n
What are the important characteristics of a good Product Backlog item which can be considered as "Ready" for Sprint Planning? (choose all options that apply).<\/p>\n
Correct selection<\/p>\n
Product Backlog items which are sufficiently refined & clearly expressed.<\/p>\n
Product Backlog item which can be developed within one Sprint even if tested in the another Sprint.<\/p>\n
Correct selection<\/p>\n
Product Backlog item which will be finished as per Definition of Done within one Sprint.<\/p>\n
Product Backlog item which are at or towards the bottom of the Product Backlog.<\/p>\n
Correct selection<\/p>\n
Product Backlog item which are at the top of the Product Backlog.<\/p>\n
Overall explanation<\/p>\n
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.<\/p>\n
Product Backlog items that will occupy developers for the upcoming Sprint are sufficiently refined so that any one item can reasonably be "Done" within the Sprint time-box. Product Backlog items that can be "Done" by developers within one Sprint are deemed "Ready" for selection in a Sprint Planning.<\/p>\n
Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail.<\/p>\n
Rest two options are incorrect as Product Backlog items that are at or towards the bottom of the Product Backlog are not clear enough to pick up in a sprint. Development & testing of the product is considered in the same sprint as the team has to deliver a working & usable increment which complies with Definition of Done. Without testing, the team can’t consider an increment as done.<\/p>\n
Question 21Skipped<\/p>\n
The Product Backlog is an emergent, ordered list of what is needed to improve the product. Which of the following statements are related to Product Backlog Refinement. (choose all options that apply).<\/p>\n
It guides the team on how & what work needs be to delivered to build a potential shippable Increment.<\/p>\n
Correct selection<\/p>\n
It is an ongoing process.<\/p>\n
Is time-boxed to a maximum of 4 hours for a 30 days sprint.<\/p>\n
Correct selection<\/p>\n
It adds details, estimates, and order as per product Owner prioritization to Product Backlog items.<\/p>\n
Correct selection<\/p>\n
Product Owner may delegate this responsibility to others but he\/she still remains accountable.<\/p>\n
It provides a formal description of the state of the Increment when it meets the quality measures required for the product.<\/p>\n
Overall explanation<\/p>\n
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Developers collaborate on the details of Product Backlog items. It includes<\/p>\n
\u2022 Developing and explicitly communicating the Product Goal; \u2022 Creating and clearly communicating Product Backlog items; \u2022 Ordering Product Backlog items; and, \u2022 Ensuring that the Product Backlog is transparent, visible, and understood. The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.<\/p>\n
Question 22Skipped<\/p>\n
Non-functional requirements of the product such as performance, security, etc., can be captured by (choose the best two options)<\/p>\n
Writing a separate document capturing the requirements and add as appendix to Product Backlog.<\/p>\n
Correct selection<\/p>\n
Adding them to Product Backlog with Product Owner’s consent and collaborate to estimate and order them.<\/p>\n
Correct selection<\/p>\n
Adding them to Definition of "Done" and make the Product Owner aware of them.<\/p>\n
Waiting until the decision of Product Owner to release the Increment. Then, build the non-functional requirements for stabilization.<\/p>\n
Overall explanation<\/p>\n
Adding them to Product Backlog with Product Owner’s consent and collaborate to estimate and order them & Adding them to Definition of "Done" and make the Product Owner aware of them.<\/p>\n
Question 23Skipped<\/p>\n
Which statement can be considered an Increment? (choose the best option)<\/p>\n
A UML diagram that describes the functionalities in the future Sprints.<\/p>\n
A user interface layout designed for the software.<\/p>\n
Correct answer<\/p>\n
The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints.<\/p>\n
The sum of all the Product Backlog items completed during the Sprint.<\/p>\n
Overall explanation<\/p>\n
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.<\/p>\n
The user interface layout\/UML diagram evolves throughout the project, as the database architecture and other similar things. They are all part of functional features, rather than separate ones. The increment is current and additive to all prior Increments.<\/p>\n
Question 24Skipped<\/p>\n
What is "Progressive Elaboration" (choose the best option)<\/p>\n
In the pre-project stage, it is the act of working to understand requirements of the product.<\/p>\n
The act of waiting for details to randomly emerge and completing the tasks once that occurs.<\/p>\n
Shu-Ha-Ri – it is in the Shu stage when one is just beginning to learn something new; over time they progressively learn and understand more.<\/p>\n
Correct answer<\/p>\n
As the project progresses, details will emerge in greater and greater clarity until they are able to be understood to a sufficient level to complete the needed work.<\/p>\n
Overall explanation<\/p>\n
As the project progresses, details will emerge in greater and greater clarity until they are able to be understood to a sufficient level to complete the needed work<\/p>\n
Question 25Skipped<\/p>\n
The Product Owner should communicate all of the marketplace knowledge & ever-changing landscape\/environment to the Scrum Team. Who should do the preliminary work of gathering the marketplace data for the Product Owner? (choose the best option).<\/p>\n
The Scrum Master.<\/p>\n
Correct answer<\/p>\n
It does not matter who does the preliminary work.<\/p>\n
The Key Stakeholders.<\/p>\n
The Product Owner.<\/p>\n
Overall explanation<\/p>\n
The Product Owner may or may not be the one doing the legwork of gathering the marketplace data, he\/she may delegate the responsibility to others but the Product Owner should definitely be aware of said data\/research.<\/p>\n
Question 26Skipped<\/p>\n
In the middle of the Sprint, Developers find that they have more room for additional work. They decide to change the Sprint Backlog by adding few more backlog items from the Product Backlog. Who should be present to decide the additional work and accordingly modify the Sprint Backlog? (choose the best two options)<\/p>\n
Senior members of developers.<\/p>\n
Scrum Master.<\/p>\n
Correct selection<\/p>\n
Developers.<\/p>\n
Correct selection<\/p>\n
Product Owner.<\/p>\n
Scrum Team.<\/p>\n
Overall explanation<\/p>\n
Nobody can change the Sprint Backlog other than developers. So Developers should be present. Product Owner is responsible for optimizing the value of developers’ work and is needed to explain the content of the Product Backlog, and give mutual consent on the next work. Product Owner is accountable for Product Backlog and prioritizing product backlog items. So the Product Owner also needs to be present.<\/p>\n
Question 27Skipped<\/p>\n
During the Daily Scrum, a team member says he does not know when his task will be complete (choose the best option)<\/p>\n
It is acceptable as the sprint review date is far away.<\/p>\n
Replace the team member with a new team member.<\/p>\n
Correct answer<\/p>\n
Developers should collaborate to plan alternative steps such as pairing with someone else, etc. to eliminate the risk of not meeting the Sprint Goal.<\/p>\n
Scrum Master should mentor the team member on how to est. the task.<\/p>\n
Overall explanation<\/p>\n
Scrum Teams are self-managing and cross-functional. Self-managing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. So dev team should collaborate to plan alternative steps such as pairing with someone else, etc. to eliminate the risk of not meeting the Sprint Goal.<\/p>\n
Question 28Skipped<\/p>\n
Who creates the Sprint Goal?<\/p>\n
Choose only ONE best answer.<\/p>\n
The Scrum Master<\/p>\n
Developers<\/p>\n
Correct answer<\/p>\n
The Scrum Team<\/p>\n
The Product Owner<\/p>\n
Overall explanation<\/p>\n
The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. The whole Scrum Team collaborates at Sprint Planning event to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders.<\/p>\n
Question 29Skipped<\/p>\n
Who is the chief product visionary?<\/p>\n
Choose only ONE best answer.<\/p>\n
The Scrum Master<\/p>\n
The Chief Executive Officer (CEO)<\/p>\n
The Chief Marketing Officer (CM0)<\/p>\n
Correct answer<\/p>\n
The Product Owner<\/p>\n
The manager of the team<\/p>\n
Overall explanation<\/p>\n
One of the product owner’s responsibilities is to have a vision of what he or she wishes to build and convey that vision to the scrum team. This is key to successfully starting any agile software development<\/p>\n
Question 30Skipped<\/p>\n
The Product Owner decides not to create a Product Goal. In this case (select all correct answers)<\/p>\n
Choose ALL answers that apply.<\/p>\n
It is up to the Product Owner<\/p>\n
Correct selection<\/p>\n
Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless<\/p>\n
Correct selection<\/p>\n
The Scrum Master is helping find techniques for effective Product Goal definition and Product Backlog management<\/p>\n
The Product Owner must discuss with Developers and if they are ok with it, then he or she may remove the Product Goal<\/p>\n
Overall explanation<\/p>\n
As we know from the Scrum Guide while implementing only parts of Scrum is possible (by removing the Product Goal), the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices. In this case, the best action from the Scrum Master to discuss it with the Product Owner and find techniques for effective Product Goal definition<\/p>\n
Question 31Skipped<\/p>\n
Upon what type of process control is Scrum based?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
Empirical<\/p>\n
Complex<\/p>\n
Hybrid<\/p>\n
Defined<\/p>\n
Overall explanation<\/p>\n
Scrum is founded on empirical process control theory. or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.<\/p>\n
Question 32Skipped<\/p>\n
The Product Owner ensures enough items are selected from the Product Backlog in the Sprint Planning meeting to satisfy the stakeholders.<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
True<\/p>\n
Overall explanation<\/p>\n
It’s only up to the developers to decide how many items they will select from the top of the Product Backlog. The Product Owner only orders the items.<\/p>\n
Question 33Skipped<\/p>\n
When does a Developer become the sole owner of an item or task on the Sprint Backlog?<\/p>\n
(choose the best answer)<\/p>\n
Whenever a team member can accommodate more work.<\/p>\n
During the Daily Scrum.<\/p>\n
At the Sprint Planning event.<\/p>\n
Correct answer<\/p>\n
Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team.<\/p>\n
Overall explanation<\/p>\n
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, and the set of Product Backlog items selected for the Sprint are collectively owned by the Developers. No individual Developer can claim ownership over an item as this would block communication and collaboration. The Sprint Backlog is updated by the Developers throughout the Sprint as more is learned.<\/p>\n
Question 34Skipped<\/p>\n
A Scrum Team consists of the following:<\/p>\n
(choose the best three answers)<\/p>\n
Customers<\/p>\n
Correct selection<\/p>\n
Developers<\/p>\n
Users<\/p>\n
Correct selection<\/p>\n
Scrum Master<\/p>\n
Correct selection<\/p>\n
Product Owner<\/p>\n
Overall explanation<\/p>\n
The Scrum Team consists of one Scrum Master, one Product Owner. and Developers.<\/p>\n
Question 35Skipped<\/p>\n
Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?<\/p>\n
(choose the best answer)<\/p>\n
The Developers<\/p>\n
Correct answer<\/p>\n
The Product Owner<\/p>\n
The Scrum Master<\/p>\n
The Project Manager<\/p>\n
Overall explanation<\/p>\n
The Product Owner is the sole person responsible for ordering the Product Backlog. Their responsibilities include making the Product Backlog visible, transparent, and clear to all.<\/p>\n
Question 36Skipped<\/p>\n
The Developers should have ail the skilis needed to:<\/p>\n
(choose the best answer)<\/p>\n
Do all of the development work, except for specialized testing that requires additional tools and environments.<\/p>\n
Correct answer<\/p>\n
Turn the Product Backlog items they select into an Increment of useful and valuable product functionality.<\/p>\n
Complete the project as estimated when the date and cost are committed to the Product Owner.<\/p>\n
Overall explanation<\/p>\n
The Developers are a group of professionals who do the work of delivering an Increment of done product at the end of each Sprint. As a team. Developers have all of the skills necessary to create a product Increment.<\/p>\n
Question 37Skipped<\/p>\n
When many Scrum Teams are working on a single product, what best describes the Definition of Done?<\/p>\n
(choose the best answer)<\/p>\n
It depends.<\/p>\n
Each Scrum Team uses its own, but must make their definition clear to all other teams sothe differences are known.<\/p>\n
Correct answer<\/p>\n
All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.<\/p>\n
Overall explanation<\/p>\n
The Increment must be valuable and useful. This means that when many Scrum Teams are working on a single product, they are expected to adhere to a single Definition of Done for the Increment.<\/p>\n
Question 38Skipped<\/p>\n
The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.<\/p>\n
(Which one the following answers is FALSE?)<\/p>\n
The Developers may work with the Product Owner to remove or add work if it finds it has more or less capacity than it expected.<\/p>\n
As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.<\/p>\n
Correct answer<\/p>\n
The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.<\/p>\n
The Product Owner can help clarify or optimize the Sprint when asked by the Developers.<\/p>\n
Overall explanation<\/p>\n
The Sprint Backlog makes visible all of the work that the Developers identify as necessary to meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.<\/p>\n
Question 39Skipped<\/p>\n
The Developers should have ail the skills needed to:<\/p>\n
(choose the best answer)<\/p>\n
Do all of the development work, except for specialized testing that requires additional tools and environments.<\/p>\n
Correct answer<\/p>\n
Turn the Product Backlog items they select into an Increment of useful and valuable product functionality.<\/p>\n
Complete the project as estimated when the date and cost are committed to the Product Owner.<\/p>\n
Overall explanation<\/p>\n
The Developers are a group of professionals who do the work of delivering an Increment of done product at the end of each Sprint. As a team. Developers have all of the skills necessary to create a product Increment.<\/p>\n
Question 40Skipped<\/p>\n
True or False: Scrum has a role called "project manager."<\/p>\n
True<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
A Scrum Team has a Scrum Master, a Product Owner and Developers. As a whole they have all controls needed.<\/p>\n
Question 41Skipped<\/p>\n
When should the Developers on a Scrum Team be replaced?<\/p>\n
(choose the best answer)<\/p>\n
Every Sprint to promote shared learning.<\/p>\n
As needed, with no special allowance for changes in productivity.<\/p>\n
Never, it reduces productivity.<\/p>\n
Correct answer<\/p>\n
As needed, while taking into account a short-term reduction in productivity.<\/p>\n
Overall explanation<\/p>\n
Scrum Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.<\/p>\n
Question 42Skipped<\/p>\n
What is the recommended size for a Scrum Team?<\/p>\n
(choose the best answer)<\/p>\n
Minimum of 7.<\/p>\n
7 plus or minus 2.<\/p>\n
Correct answer<\/p>\n
Typically 10 or fewer people.<\/p>\n
Overall explanation<\/p>\n
A Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. Generally smaller teams communicate better and are more productive<\/p>\n
Question 43Skipped<\/p>\n
The timebox for the Sprint Planning event is?<\/p>\n
(choose the best answer)<\/p>\n
Whenever it is done.<\/p>\n
4 hours.<\/p>\n
Monthly.<\/p>\n
Correct answer<\/p>\n
8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.<\/p>\n
Overall explanation<\/p>\n
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.<\/p>\n
Question 44Skipped<\/p>\n
The CEO asks the Developers to add a \u201cvery important\u201d item to a Sprint that is in progress.<\/p>\n
What should the Developers do?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
Inform the other members of the Scrum Team so the team can decide what to do.<\/p>\n
Add the item to the next Sprint.<\/p>\n
Add the item to the current Sprint and drop an item of equal size.<\/p>\n
Add the item to the current Sprint without any adjustments.<\/p>\n
Overall explanation<\/p>\n
The items selected for a Sprint have been selected as most valuable with the Product Owner. The items serve the Sprint’s goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Developers.<\/p>\n
Question 45Skipped<\/p>\n
The CEO asks the Developers to add a \u201cvery important\u201d item to a Sprint that is in progress.<\/p>\n
What should the Developers do?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
Inform the other members of the Scrum Team so the team can decide what to do.<\/p>\n
Add the item to the next Sprint.<\/p>\n
Add the item to the current Sprint and drop an item of equal size.<\/p>\n
Add the item to the current Sprint without any adjustments.<\/p>\n
Overall explanation<\/p>\n
The items selected for a Sprint have been selected as most valuable with the Product Owner. The items serve the Sprint’s goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Developers.<\/p>\n
Question 46Skipped<\/p>\n
How much work must the Developers complete for each Product Backlog item they select for a Sprint?<\/p>\n
(choose the best answer)<\/p>\n
All development work and at least some testing.<\/p>\n
Analysis, design, programming, testing and documentation.<\/p>\n
Correct answer<\/p>\n
Enough so that each Product Backlog item they select meets the Definition of Done.<\/p>\n
As much as it can fit into the Sprint.<\/p>\n
Overall explanation<\/p>\n
The purpose of each Sprint is to deliver useful and valuable Increments that adhere to the Scrum Team’s<\/p>\n
current Definition of Done.<\/p>\n
Question 47Skipped<\/p>\n
During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast. Who should be present to review and adjust the Product Backlog items selected?<\/p>\n
(choose the best answer)<\/p>\n
The Product Owner and all stakeholders.<\/p>\n
The Scrum Master, the project manager, and the Developers<\/p>\n
Correct answer<\/p>\n
The Product Owner and the Developers.<\/p>\n
The Developers.<\/p>\n
Overall explanation<\/p>\n
During the Sprint. scope may be clarified and re-negotiated between the Product Owner and the Developers as more is learned. It is important to be transparent when challenges arise since ultimately the entire Scrum Team is accountable for creating a valuable, useful Increment.<\/p>\n
Question 48Skipped<\/p>\n
What are two ways a Scrum Master serves to enable effective Scrum Teams?<\/p>\n
(choose the best two answers)<\/p>\n
Correct selection<\/p>\n
By removing impediments that hinder the Scrum Team.<\/p>\n
By keeping high value features high in the Product Backlog.<\/p>\n
By starting and ending the meetings at the proper time.<\/p>\n
Correct selection<\/p>\n
By facilitating Developer decision-making.<\/p>\n
Overall explanation<\/p>\n
The Scrum Master serves the Scrum Team in several ways. Facilitation and removing impediments are examples of ways a Scrum Master helps a team become more effective.<\/p>\n
Question 49Skipped<\/p>\n
Each Developer in Scrum Team must be cross-functional<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
True<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
According to the Scrum Guide, Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value for each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how. It means they must be cross-functional as a team, but not individually<\/p>\n
Question 50Skipped<\/p>\n
Who creates a Sprint Goal ?<\/p>\n
Scrum Master<\/p>\n
Developer<\/p>\n
Correct answer<\/p>\n
Scrum team<\/p>\n
Product Owner<\/p>\n
Overall explanation<\/p>\n
The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goat also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. The whole Scrum Team collaborates at Sprint Planning event to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders.<\/p>\n
Question 51Skipped<\/p>\n
How would the Product Backlog be impacted by the changes in<\/p>\n
the environment in which the product will be used?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
It evolves to reflect the changes<\/p>\n
The Product Backlog should be kept high-level enough to tolerate such changes.<\/p>\n
It is required to complete the old Product Backlog and create a new Product<\/p>\n
Backlog<\/p>\n
There\u2019s no effect on the Product Backlog.<\/p>\n
It is required to complete the old Product Backlog and create a new Product<\/p>\n
Backlog<\/p>\n
Overall explanation<\/p>\n
A Product Backlog is never complete. The earliest development of it lays out the initially<\/p>\n
known and best-understood requirements. The Product Backlog evolves as the product and<\/p>\n
the environment in which it will be used evolves<\/p>\n
Question 52Skipped<\/p>\n
A company has three products. Which two of the following are an<\/p>\n
acceptable way of forming Scrum teams?<\/p>\n
Choose ALL answers that apply.<\/p>\n
There must be one Product Owner for each product. It is not required to have one Product Owner for two and more teams.<\/p>\n
Correct selection<\/p>\n
There can be one Product Owner for each product<\/p>\n
Correct selection<\/p>\n
There can be a single Product Owner for all products<\/p>\n
There must be a single Product Owner for all products<\/p>\n
Overall explanation<\/p>\n
Maximum number of product owners for a team is 1. minimum number of product owner for all scrum team is also 1.<\/p>\n
Question 53Skipped<\/p>\n
According to the new version of the Scrum Guide, Scrum Teams are self-managing, meaning they internally decide who does what, when, and how. It means that Scrum Team are not self- organizing<\/p>\n
Choose only ONE best answer.<\/p>\n
True<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
Self-management is the minimum bar. Scrum Teams can still be self-organizing, self- designing, or even self-governing if the situation allows, and supporting such constructs can provide immense benefit. Remember, Scrum is a framework. It gives the scaffolding for people, teams, and organizations to generate value through adaptive solutions to complex problems. The Scrum Guide only states what is required for Scrum, and ideally, nothing else.<\/p>\n
Question 54Skipped<\/p>\n
Which Scrum event or artifact supports daily inspection and adaptation?<\/p>\n
Choose only ONE best answer.<\/p>\n
Sprint Backlog<\/p>\n
Correct answer<\/p>\n
Daily Scrum<\/p>\n
Sprint<\/p>\n
Product Backlog<\/p>\n
Overall explanation<\/p>\n
There is only one daily activity (event) is scrum: Daily Scrum<\/p>\n
Question 55Skipped<\/p>\n
The Increment is the summation of overall backlog items finished during the Sprint and also the previous completed Sprints. But when should the Increment be shipped?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
When it makes sense<\/p>\n
After each Sprint<\/p>\n
When the Increment is free of defects<\/p>\n
When the Increment is shippable<\/p>\n
Overall explanation<\/p>\n
All Increments should be potentially releasable (shippable), but we don’t have to release all of them. It depends on the project environment and the customer, and the Product Owner is supposed to decide on it<\/p>\n
Question 56Skipped<\/p>\n
Technical debt leads to<\/p>\n
Choose only ONE best answer.<\/p>\n
Projects that are over-budget<\/p>\n
Correct answer<\/p>\n
Products that are difficult to extend and maintain<\/p>\n
Processes that lack tools<\/p>\n
Overall explanation<\/p>\n
Technical debt refers to quality consequences by the poor technical choices made<\/p>\n
Question 57Skipped<\/p>\n
What does Burn-down Chart show?<\/p>\n
Choose only ONE best answer.<\/p>\n
The evolution of the amount of uncertainty during a project<\/p>\n
Correct answer<\/p>\n
How much work remains until the end of the Sprint<\/p>\n
Dependencies, start times and stop times for project tasks<\/p>\n
An overview of the release progress by plotting the remaining workload<\/p>\n
Overall explanation<\/p>\n
The burn-down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed. However burn-down charts are not mandatory in Scrum<\/p>\n
Question 58Skipped<\/p>\n
What is unrealized value in Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
The organization’s ability to quickly deliver new capabilities, services, or products<\/p>\n
The value that the product delivers<\/p>\n
Correct answer<\/p>\n
The potential future value that could be realized if the organization met the needs of all potential customers or users<\/p>\n
Overall explanation<\/p>\n
The potential future value that could be realized if the organization met the needs of all potential customers or users. Looking at Unrealized Value helps an organization to maximize the value that it realizes from a product or service over time. When customers, users, or clients experience a gap between their current experience and the experience that they would like to have, the difference between the two represents an opportunity; this opportunity is measured by Unrealized Value.<\/p>\n
Question 59Skipped<\/p>\n
Some of Sprint Backlog items were not completed and some were completed during the Sprint. What should happen with completed items when the Sprint is cancelled?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
Such items will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them.<\/p>\n
Such items should be moved back to the Product Backlog and would be taken care of in future Sprints.<\/p>\n
Such items should be moved to the next Sprint Backlog.<\/p>\n
Overall explanation<\/p>\n
When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. if part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The work done on them depreciates quickly and must be frequently re-estimated.<\/p>\n
Question 60Skipped<\/p>\n
From the following statements choose one or more correct answers about the Daily Scrum.<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
The Daily Scrum is time-boxed<\/p>\n
Correct selection<\/p>\n
Only Developers participate at this event<\/p>\n
The Product Owner must provide updates to Developers at the Daily Scrum<\/p>\n
The Scrum Master makes a report to the Product Owner<\/p>\n
Overall explanation<\/p>\n
The Daily Scrum is a 15-minute time-boxed event for Developers. The Daily Scrum is held every day of the Sprint. At this event, Developers plan activities for the next 24 hours.<\/p>\n
Question 61Skipped<\/p>\n
What should the Product Owner do during the Sprint zero?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
There’s no such event in Scrum as Sprint Zero<\/p>\n
Prepare the Product Backlog for the whole project<\/p>\n
Communicate with the customer and understand the requirements<\/p>\n
Prepare the Product Backlog for the next few Sprints<\/p>\n
Overall explanation<\/p>\n
There’s no such event in Scrum as Sprint Zero<\/p>\n
Question 62Skipped<\/p>\n
Which of the following are ways for stakeholders to interact with Developers? (select all correct answers)<\/p>\n
Choose ALL answers that apply.<\/p>\n
At the Sprint Planning<\/p>\n
Correct selection<\/p>\n
Via the Product Owner<\/p>\n
Correct selection<\/p>\n
At the Sprint Review<\/p>\n
At the Daily Scrums<\/p>\n
At the Sprint Retrospective<\/p>\n
Overall explanation<\/p>\n
The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint.<\/p>\n
Question 63Skipped<\/p>\n
A new Increment of working software must be available<\/p>\n
Choose only ONE best answer.<\/p>\n
Before each planned release<\/p>\n
Correct answer<\/p>\n
At the end of each Sprint<\/p>\n
Every 3 Sprints<\/p>\n
Whenever the user acceptance testing is done<\/p>\n
When the Product Owner asks for it<\/p>\n
Overall explanation<\/p>\n
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. At the end of a Sprint, the new Increment must be "Done," which means it must be in useable condition and meet the Scrum Team’s definition of "Done".<\/p>\n
Question 64Skipped<\/p>\n
How much of the Sprint Backlog should be defined during the Sprint Planning meeting?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
Just enough, so Developers can forecast what it can do, and start the first several days of the Sprint.<\/p>\n
Just enough to understand design and architecture.<\/p>\n
During the Sprint Planning event, the Scrum Team selects all of the potential work<\/p>\n
Just enough for the Scrum Master to be able to assign tasks to Developers The Product Owner decides it<\/p>\n
Overall explanation<\/p>\n
The Sprint Backlog includes the items selected from the Product Backlog and the tasks created by decomposing the items. The items are completely planned in the Sprint Planning, but not all tasks are created; just enough for the first few days of development. The rest of the tasks will be created during the Sprint<\/p>\n
Question 65Skipped<\/p>\n
Every Scrum team must determine its own cadence for releasing features to customers. Some choose to release every sprint, while others after 2, 3 and even more Sprints. But who is responsible for planning releases?<\/p>\n
Choose only ONE best answer.<\/p>\n
Developers<\/p>\n
Scrum Master<\/p>\n
Correct answer<\/p>\n
Product Owner<\/p>\n
Project manager<\/p>\n
Overall explanation<\/p>\n
Release Planning is the Responsibility of the PO.<\/p>\n
Question 66Skipped<\/p>\n
How much time should a Product Owner spend with Developers?<\/p>\n
Choose only ONE best answer.<\/p>\n
100% of the time<\/p>\n
As much as required by senior stakeholders<\/p>\n
The Scrum Master defines the required time for the Product Owner to spend with Developers<\/p>\n
Correct answer<\/p>\n
As much as needed to maximize the value of the product<\/p>\n
Overall explanation<\/p>\n
The Product Owner needs to spend as much time with Developers as needed to make an increment<\/p>\n
Question 67Skipped<\/p>\n
Which of the following are optional in Scrum? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Having potentially releasable Increments<\/p>\n
Correct selection<\/p>\n
Velocity<\/p>\n
Correct selection<\/p>\n
Release plan<\/p>\n
Product Goal<\/p>\n
Product Backlog<\/p>\n
Overall explanation<\/p>\n
Velocity and Release Plan are not mandatory in Scrum<\/p>\n
Question 68Skipped<\/p>\n
This Scrum event is for process improvement and the purpose of this event is to plan ways to increase quality and effectiveness.<\/p>\n
Choose only ONE best answer.<\/p>\n
Sprint Planning<\/p>\n
Correct answer<\/p>\n
Sprint Retrospective<\/p>\n
Daily Scrum<\/p>\n
Sprint Review<\/p>\n
Overall explanation<\/p>\n
The purpose of the Sprint Retrospective is to: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work.<\/p>\n
Question 69Skipped<\/p>\n
Which of the following is the single source of requirements for all changes to the product?<\/p>\n
Choose only ONE best answer.<\/p>\n
The Increment<\/p>\n
The Sprint Retrospective<\/p>\n
Correct answer<\/p>\n
The Product Backlog<\/p>\n
The Sprint Backlog<\/p>\n
The product vision<\/p>\n
Overall explanation<\/p>\n
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.<\/p>\n
Question 70Skipped<\/p>\n
The Scrum Team has just begun the Sprint Planning meeting. There are a lot of questions about the Product Backlog and in general, the Product Backlog is not clear. Due to this, what is the maximum duration of Sprint Planning?<\/p>\n
Choose only ONE best answer.<\/p>\n
12 hours<\/p>\n
2 hours<\/p>\n
Correct answer<\/p>\n
8 hours<\/p>\n
6 hours<\/p>\n
In this case, the duration can be even more than one day<\/p>\n
Overall explanation<\/p>\n
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.<\/p>\n
Question 71Skipped<\/p>\n
The Product Backlog Refinement is not a mandatory but very common and useful event in Scrum. When should the Product Backlog items be refined? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
In so-called Sprint zero<\/p>\n
Correct selection<\/p>\n
During the current Sprint, if they have not been refined in the previous Sprints<\/p>\n
Correct selection<\/p>\n
In one or two preceding Sprints<\/p>\n
Only in the time between the two Sprints<\/p>\n
Overall explanation<\/p>\n
There is no Sprint 0. Also, new Sprint starts immediately after the previous<\/p>\n
Question 72Skipped<\/p>\n
What are good ways for a Scrum Team to ensure security concerns are satisfied? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Add a Sprint to specifically resolve all security concerns<\/p>\n
Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items<\/p>\n
Delegate the work to the concerned department<\/p>\n
Correct selection<\/p>\n
Add security concerns to the definition of \u201cDone\u201d<\/p>\n
Correct selection<\/p>\n
Have the Scrum Team create Product Backlog items for each concern.<\/p>\n
Overall explanation<\/p>\n
Many of the security concerns are non-functional features and therefore will be added to the Definition of Done to be applied to all Product Backlog items. Some security concerns are specific and only about a certain part of the product and they can be items in the Product Backlog.<\/p>\n
Question 73Skipped<\/p>\n
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment in each Sprint. Which of the following answers are the responsibilities of Developers in Scrum? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
Pulling Product Backlog items for the upcoming Sprint<\/p>\n
Creating new Product Backlog items<\/p>\n
Correct selection<\/p>\n
Estimating Sprint Backlog items<\/p>\n
Correct selection<\/p>\n
Creating tasks for Sprint Backlog items<\/p>\n
Reordering the Product Backlog<\/p>\n
Overall explanation<\/p>\n
According to the Scrum Guide, the specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for: – Creating a plan for the Sprint, the Sprint Backlog; – instilling quality by adhering to a Definition of Done; – Adapting their plan each day toward the Sprint Goal; – Holding each other accountable as professionals.<\/p>\n
Question 74Skipped<\/p>\n
When does Cross-Team Refinement occur in Scaled Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
Before the Sprint Planning<\/p>\n
After the Scaled Scrum Sprint Review<\/p>\n
Correct answer<\/p>\n
There is no specific time during the Sprint for Cross-Team Refinement<\/p>\n
After the Scaled Scrum Sprint Planning<\/p>\n
Overall explanation<\/p>\n
There is no specific time during the Sprint when teams work on Refinement.<\/p>\n
Question 75Skipped<\/p>\n
What is the time box for the Cross-Team Refinement meeting in<\/p>\n
Scaled Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
max 4 hours<\/p>\n
max 8 hours<\/p>\n
max 6 hours<\/p>\n
Correct answer<\/p>\n
There is no specific Time Box<\/p>\n
Overall explanation<\/p>\n
There is no specific time box for Cross-Team Refinement, nor is there a specific time during the Sprint when teams work on Refinement.<\/p>\n
Question 76Skipped<\/p>\n
Representatives from the Scrum Teams meet once again to discuss common issues identified in the Scrum Team Retrospectives. They agree on how to visualize and track the identified actions that will enable Scaled Scrum to learn and adapt as a whole. What part of the Scaled Scrum Sprint Retrospective is it?<\/p>\n
Choose only ONE best answer.<\/p>\n
1<\/p>\n
2<\/p>\n
3<\/p>\n
Correct answer<\/p>\n
The process doesn’t relate to the Scaled Scrum Sprint Retrospective<\/p>\n
Overall explanation<\/p>\n
There are no mandatory requirements for teams in Scaled Scrum to divide Sprint Retrospective event into 2 or more parts. It is up to the Scaled Scrum Integration Team<\/p>\n
Question 77Skipped<\/p>\n
What is the maximum number of members in the Scaled Scrum Integration Team?<\/p>\n
Choose only ONE best answer.<\/p>\n
3 to 9<\/p>\n
15<\/p>\n
5 to 11<\/p>\n
Correct answer<\/p>\n
as many as required to develop and integrate the best solution for the product<\/p>\n
Overall explanation<\/p>\n
There is no direct restriction on a number of staff in the Scaled Scrum Integration Team. Usually, there are 5-8 members but it is not mandatory<\/p>\n
Question 78Skipped<\/p>\n
How many Product Backlogs are used in Scaled Scrum?<\/p>\n
Choose only ONE best answer.<\/p>\n
The number of Backlogs is equal to the number of Scrum Team in Scaled Scrum<\/p>\n
Correct answer<\/p>\n
One Product Backlog for the entire product<\/p>\n
2 Product Backlogs (one for Scaled Scrum Team and one for all other teams)<\/p>\n
Overall explanation<\/p>\n
There is a single Product Backlog for the entire Scaled Scrum and all of its Scrum Teams. The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering.<\/p>\n
Question 79Skipped<\/p>\n
Transitioning from Waterfall to Scrum is a very significant step for the organization. How will the organization measure the success of Scrum implementation? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
By reducing costs<\/p>\n
Correct selection<\/p>\n
By increasing customer satisfaction<\/p>\n
By delivering an increment every Sprint<\/p>\n
Correct selection<\/p>\n
Through frequent releases and meeting value metrics or KPIs<\/p>\n
By releasing new features after each Sprint<\/p>\n
Overall explanation<\/p>\n
Customer’s and end user’s satisfaction is important. It’s not an abstract measure like lines of code or velocity. There can be some KPIs for measuring the value of the releases, and when improved, will show our success. Increased velocity is desired, but it’s not directly connected to value and can be misleading. That’s the same with production cost. It’s mandatory to deliver an Increment every Sprint.<\/p>\n
Question 80Skipped<\/p>\n
As a Product Owner, you are responsible for stakeholder management. From the following answers choose the correct statement about the relationship between PO and the stakeholder<\/p>\n
Choose only ONE best answer.<\/p>\n
The stakeholder is a manager of the Product Owner and he or she creates task for the Product Backlog<\/p>\n
Stakeholders are always users of the product and they can’t advise anything to the PO<\/p>\n
Correct answer<\/p>\n
The Product Owner represents the stakeholders to the Scrum Team, which includes representing their desired requirements in the Product Backlog<\/p>\n
One of the stakeholders must be the Scrum Master<\/p>\n
Overall explanation<\/p>\n
The Product Owner is the bridge between the team and the stakeholders. The Product Owner actively asks for stakeholder expectations to process into the Product Backlog.<\/p>\n","protected":false},"excerpt":{"rendered":"
PSPO1 Practice Exam Set Two Question 1Skipped True or false? When multiple teams are working on the same product, their Sprints should start and end at the same time. TRUE Correct answer FALSE Overall explanation FALSE, it’s not mandatory to start and end the Sprints at the same time; e.g., most teams have four-week Sprints, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-210","post","type-post","status-publish","format-standard","hentry","category-pspo-i-exam-list"],"_links":{"self":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=210"}],"version-history":[{"count":1,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/210\/revisions"}],"predecessor-version":[{"id":211,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/210\/revisions\/211"}],"wp:attachment":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}