Question 1Skipped<\/p>\n
User documentation is part of your definition of "Done." However, there aren’t enough technical writers for all teams. Your Development Team doesn’t have a technical writer. What should you do? (choose the best answer)<\/p>\n
Wait until you have a technical writer on your Development Team to take care of this.<\/p>\n
Correct answer<\/p>\n
Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.<\/p>\n
Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.<\/p>\n
Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.<\/p>\n
Overall explanation<\/p>\n
Waiting for a Technical writer can not be an option. Also, if we keep the documentation undone it will further delay the process. Only to prepare the documentation we cannot form a new team hence we are left with only one option Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.<\/p>\n
Question 2Skipped<\/p>\n
Which of the following are criteria to order Product Backlog items? (choose all that apply)<\/p>\n
Correct selection<\/p>\n
Dependencies between Product Backlog items.<\/p>\n
Dependencies to other products.<\/p>\n
Correct selection<\/p>\n
Value of Product Backlog items.<\/p>\n
The availability of the Scrum Master.<\/p>\n
All of the above.<\/p>\n
Overall explanation<\/p>\n
Dependencies to other products and availability of Scrum Master are not an criteria to order the items in the product backlog.<\/p>\n
Question 3Skipped<\/p>\n
In order to maximize the value of the product, a Product Owner needs awareness of the following: (choose the best answer)<\/p>\n
Correct answer<\/p>\n
Customer feedback.<\/p>\n
None of the above.<\/p>\n
Forecasting & feasibility.<\/p>\n
Product vision.<\/p>\n
Competitive research.<\/p>\n
All of the above<\/p>\n
Overall explanation<\/p>\n
Customer feedback is the main criteria for the Product Owner to judge over the product release and features.<\/p>\n
Question 4Skipped<\/p>\n
The "cone of uncertainty" can be used to do what? (choose the best answer)<\/p>\n
Project what will be completed by a given Sprint.<\/p>\n
Illustrate that, as a forecast lengthens, it is increasingly less certain.<\/p>\n
Correct answer<\/p>\n
Determine the cost of a project before it is begun.<\/p>\n
Determine whether to cut quality, similar to the "Iron Triangle" of project management.<\/p>\n
Overall explanation<\/p>\n
The cone of uncertainty is the unknown parameters of the project and it gets reduced as further we move towards the project end. Hence it is expected that we can use it to estimate the project cost initially.<\/p>\n
Question 5Skipped<\/p>\n
Which three of the following are feedback loops in Scrum? (choose the best three answers)<\/p>\n
Release Planning.<\/p>\n
Refinement Meeting.<\/p>\n
Correct selection<\/p>\n
Sprint Retrospective.<\/p>\n
Correct selection<\/p>\n
Sprint Review.<\/p>\n
Correct selection<\/p>\n
Daily Scrum.<\/p>\n
Overall explanation<\/p>\n
Release Planning, Refinement Meeting are not scrum events to get feedback.<\/p>\n
Question 6Skipped<\/p>\n
Which two things should the Development Team do during the first Sprint? (choose the best two answers)<\/p>\n
Correct selection<\/p>\n
Develop at least one piece of functionality.<\/p>\n
Analyze, design, and describe the complete architecture and infrastructure.<\/p>\n
Analyze, describe, and document the requirements for the subsequent Sprints.<\/p>\n
Correct selection<\/p>\n
Create an Increment of potentially releasable software.<\/p>\n
Make up a plan for the rest of the project.<\/p>\n
Overall explanation<\/p>\n
Develop at least one piece of functionality. Create an Increment of potentially releasable software. are the two things that can be done in the first sprint. For Agile project complete plan is never prepared at a go. Also, analyzing and creating complete architecture for subsequent sprint or for total project is not done in first sprint.<\/p>\n
Question 7Skipped<\/p>\n
Which does a self-organizing Development Team choose?<\/p>\n
(choose the best answer)<\/p>\n
Product Backlog ordering.<\/p>\n
When to release, based on its progress.<\/p>\n
Correct answer<\/p>\n
How to best accomplish its work.<\/p>\n
Sprint length.<\/p>\n
Stakeholders for the Sprint Review.<\/p>\n
Overall explanation<\/p>\n
How to best accomplish its work because they know the best way to do their job.<\/p>\n
Question 8Skipped<\/p>\n
The Scrum Master Observes the Product Owner struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take? (choose the best answer)<\/p>\n
Present the Product Owner with an ordered Product Backlog to use.<\/p>\n
Encourage the Product Owner to work with the Development Team to see which items technically are fastest to implement.<\/p>\n
Suggest the Product Owner extend the Sprint, so he can have more time to order the Product Backlog.<\/p>\n
Correct answer<\/p>\n
Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.<\/p>\n
Suggest that the Development Team does the ordering to be sure that it is a feasible ordering of work.<\/p>\n
Overall explanation<\/p>\n
Development Team cannot order the product backlog. Also, extending the sprint cannot be an option. Scrum master cannot prepare the entire Product backlog all by himself. And the objective should be to deliver the highest value item not the fastest one.<\/p>\n
Hence we are left with only one option. Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.<\/p>\n
Question 9Skipped<\/p>\n
What is a Product Owner responsibility that he\/she might delegate?<\/p>\n
Attending the Sprint Review<\/p>\n
Representing stakeholders to the Scrum team<\/p>\n
Correct answer<\/p>\n
Ordering the Product Backlog<\/p>\n
Writing User Stories<\/p>\n
Overall explanation<\/p>\n
The development team may need to order the product backlog as they would know the most about technical limitations, risks, or dependencies between Product Backlog Items. As User Stories is a localized practice, Scrum does not govern it or dictate the practice. How the team describes the items is up to them as long as it has enough information to be transparent and understood.<\/p>\n
Question 10Skipped<\/p>\n
Anew Product Owner is hired to work on an existing product that has ongoing for five Sprints. He\/she is unsure about all of the responsibilities of a Product Owner. Which of these Product Owner’s activities are defined in Scrum?<\/p>\n
Ensuring work is completed within scope and time.<\/p>\n
Describing features as Use Cases.<\/p>\n
Correct answer<\/p>\n
Interacting with stakeholders and ensuring that the most valuable functionality is always produced first.<\/p>\n
Writing User Stories.<\/p>\n
Overall explanation<\/p>\n
It is only the PO\u00a0responsibility to talk to stakeholders and ensure that the most valuable items are selected to deliver in sprint.<\/p>\n
Question 11Skipped<\/p>\n
Peter is a new Product Owner on a newly formed Scrum Team. Peter has Projected a product completion date based on an estimated velocity of 21 completed points per Sprint. After the first 3 Sprints, the team has determined that their maximum velocity is 15 point’s, and they are unable to create shippable increments at the end of each Sprint. What is the best way to proceed?<\/p>\n
Correct answer<\/p>\n
Inform Peter that the projected completion date is not correct. The Development team would estimate the remaining work to produce a shippable Increment and suggest making it \u201cDone\u201d before working on new features. Based on empirical data, Peter car\u2019 adjust the completion date and decide how to continue.<\/p>\n
The Sprints have failed to produce shippable Increments there for opportunities to inspect and adapt is lost. The Scrum Master would encourage the organization to add more team members in order to increase the team’s capacity.<\/p>\n
The Scrum Master would coach the team on improving their estimations and commitment to completing the Sprint Backlog.<\/p>\n
Extend the Sprint in order to complete the Sprint Backlog items.<\/p>\n
Overall explanation<\/p>\n
Inform Peter that the projected completion date is not correct. The Development team would estimate the remaining work to produce a shippable increment and suggest making it \u201cDone\u201d before working on new features. Based on empirical data, Peter can adjust the completion date and decide how to continue.<\/p>\n
Question 12Skipped<\/p>\n
Which of the following might the Scrum Team discuss during a Sprint Retrospective? (choose the best answer)<\/p>\n
Its definition of "Done."<\/p>\n
Skills needed to improve the Development Team’s ability to deliver.<\/p>\n
Methods of communication.<\/p>\n
The way the Scrum Team does Sprint Planning.<\/p>\n
Correct answer<\/p>\n
All of the above.<\/p>\n
Overall explanation<\/p>\n
All of the points are points to be discussed during Sprint Retrospective.<\/p>\n
Question 13Skipped<\/p>\n
Why would you expect a Product Owner to care about the Development Team adhering to its definition of "Done"? (choose the best two answers)<\/p>\n
To forecast the team\u2019s productivity over time.<\/p>\n
The Product Owner should not care about the definition of "Done", it is the Development Team’s responsibility.<\/p>\n
Correct selection<\/p>\n
To have complete transparency into what has been done at the end of each Sprint<\/p>\n
To be able to punish the team when they don’t meet their velocity goal for the Sprint.<\/p>\n
Correct selection<\/p>\n
The definition of "Done" can affect the product’s total cost of ownership.<\/p>\n
Overall explanation<\/p>\n
Teams productivity cannot be forecasted by PO, punishing is not a valid act in Scrum, being a member of Scrum PO must be cared about definition of done.<\/p>\n
Question 14Skipped<\/p>\n
Towards the end of the Sprint, the developers and yourself are debating if some of the Sprint Backlog Items where completed or not. The Scrum Master suggests to you and the developers to refer to the Definition of Done (DoD). Who should set up the DoD?<\/p>\n
Correct answer<\/p>\n
The Scrum Team unless the organization already has one. In that case, they should follow the Definition of Done as a minimum.<\/p>\n
The developers as they are the ones doing the actual work of converting the Sprint Backlog Items into an Increment.<\/p>\n
You as Product Owner as you have the authority to decide what is done and what is not.<\/p>\n
The Scrum Master as he\/she knows how Scrum works and what fit best in an Agile environment<\/p>\n
Overall explanation<\/p>\n
The Scrum Team unless the organization already has one. In that case, they should follow the Definition of Done as a minimum. DoD is a collective process.<\/p>\n
Question 15Skipped<\/p>\n
Which statements are correct about a Sprint Backlog item that was not finished until the end of the Sprint? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
It won’t be demonstrated at the Sprint Review meeting<\/p>\n
It must be completed in the next Sprint<\/p>\n
Correct selection<\/p>\n
It will be moved back to the Product Backlog<\/p>\n
It will be demonstrated to the stakeholders but pointed out that it’s not complete yet<\/p>\n
The Product Owner has to extend the Sprint until the item is done<\/p>\n
Overall explanation<\/p>\n
Only the 100% complete items are demonstrated, to avoid confusion. When something is not complete, it will be moved back to the Product Backlog. If it’s still on the top of the Product Backlog, development will continue in the next Sprint (if it will be required)<\/p>\n
Question 16Skipped<\/p>\n
The Product Backlog Refinement is not a mandatory event in Scrum. However, almost all Scrum Teams are holding this event. From the following answers select all correct benefits of the Product Backlog Refinement<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
Clarify Value<\/p>\n
Correct selection<\/p>\n
Reduce Dependencies<\/p>\n
Decrease velocity<\/p>\n
Improve relationship in the Scrum Team<\/p>\n
Correct selection<\/p>\n
Incorporate Learning<\/p>\n
Overall explanation<\/p>\n
In general there are 6 important benefits of the PBR. Here they are: – Increase transparency-Clarify value – Break things into consumable pieces – Reduce dependencies – Forecasting-Incorporate learning<\/p>\n
Question 17Skipped<\/p>\n
Who participates in the Sprint Review? (choose all options that apply).<\/p>\n
Correct selection<\/p>\n
The Product Owner.<\/p>\n
Correct selection<\/p>\n
The Developers.<\/p>\n
Correct selection<\/p>\n
The Scrum Master.<\/p>\n
Senior Management.<\/p>\n
The Application Manager.<\/p>\n
Correct selection<\/p>\n
The Key Stakeholders.<\/p>\n
Overall explanation<\/p>\n
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.<\/p>\n
The Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. It is not just a presentation rather it is a working session.<\/p>\n
Question 18Skipped<\/p>\n
Selena, a product owner for a scrum team, has refined the product backlog based on description, order, and size. John, a program manager with the PMO overseeing the group of projects Selena is working on & requested her to place a new item at the top of the product backlog. What should Selena do? (choose the best option)<\/p>\n
Selena should not be doing anything with the product backlog; this responsibility belongs to developers.<\/p>\n
Selena is accountable for the product backlog; so John doesn’t have authority to request any new item or change the order product backlog.<\/p>\n
Selena must do as John has asked as John is an important stakeholder (PMO).<\/p>\n
Correct answer<\/p>\n
Selena may consider the request of others, but the final say as to the order is hers and hers alone.<\/p>\n
Overall explanation<\/p>\n
The Product Owner is accountable for effective Product Backlog management but that doesn’t mean he\/she should not consider other’s opinions. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner. So Selena should consider John’s request but she has the final say to move or not the item to the top of the product backlog.<\/p>\n
Product Backlog management, which 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.<\/p>\n
Question 19Skipped<\/p>\n
The Product Owner should communicate all of the marketplace knowledge & ever-changing landscape, environment to the Scrum Team. What is the best way for a Product Owner to communicate this to the Scrum Team (choose all options that apply)?<\/p>\n
Correct selection<\/p>\n
During Product Backlog Refinement.<\/p>\n
During Sprint Retrospectives.<\/p>\n
During Daily Scrums.<\/p>\n
Correct selection<\/p>\n
During Sprint Review.<\/p>\n
Overall explanation<\/p>\n
The Product Owner communicates all of this marketplace knowledge to the Scrum Team through daily ad-hoc interactions as well as Product Backlog Refinement and in Sprint Reviews. During Product Backlog Refinement Product owner creates and clearly communicate Product Backlog items along with Product Goal. During Sprint review the Product Backlog may also be adjusted to meet new opportunities.<\/p>\n
Sprint Retrospective & Daily Scrum are not the right forum to discuss this as Daily Scrum is for Developers & Sprint Retrospective is for inspecting the scrum team and create a plan for improvements to be enacted during the next Sprint.<\/p>\n
Question 20Skipped<\/p>\n
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software is an Agile Principle. Which scrum practice helps the most in achieving this Agile objective? (choose the best option).<\/p>\n
Daily Scrum.<\/p>\n
Correct answer<\/p>\n
Sprint.<\/p>\n
Release Planning.<\/p>\n
Sprint Planning.<\/p>\n
Sprint Review.<\/p>\n
Overall explanation<\/p>\n
Sprint: Short Sprint Cycles. Having shorter sprints would enable teams to deliver early and the cycle of such deliveries would make it continuous delivery to the customer. Sprint planning is there irrespective of the sprint period.<\/p>\n
Question 21Skipped<\/p>\n
Mark is a product owner for a scrum team. He decides for each sprint what items will go into the sprint backlog during sprint planning. He is growing increasingly frustrated with developers not able to complete the task items he has chosen for the sprint. What should Mark do to help developers reach the sprint goal? (choose the best option)<\/p>\n
Mark should work with the scrum master to find a resolution to this issue.<\/p>\n
Mark should encourage developers to work more hours, spending weekends if necessary working towards completing the sprint goal.<\/p>\n
Correct answer<\/p>\n
Mark should work more closely with developers; items should not be added to the sprint backlog unless developers can commit to completing the items within the sprint.<\/p>\n
Mark should work to find more competent developers able to deliver what he decides for each sprint.<\/p>\n
Overall explanation<\/p>\n
During the Sprint no changes are made that would endanger the Sprint Goal. As developers works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements functionality and technology. If the work turns out to be different than developers expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint. So Mark should work more closely with developers; items should not be added to the sprint backlog unless developers can commit to completing the items within the sprint<\/p>\n
Question 22Skipped<\/p>\n
Scrum Teams are self-managed and cross-functional. How time-boxing promotes self-management? (choose all options that apply).<\/p>\n
Time-box does not allow enough time for stringent processes or meeting overhead.<\/p>\n
Time-box eliminates complexity due to organizational hierarchy.<\/p>\n
Time-box enables Scrum Team to determine the need for overtime as a percentage of the time-box.<\/p>\n
Correct selection<\/p>\n
Time-box helps everyone to focus on the same problem at the same time.<\/p>\n
Correct selection<\/p>\n
Time-box encourages team members who are closest to the problem to create the best possible solution in the time allotted.<\/p>\n
Overall explanation<\/p>\n
Time-boxes help everyone focus on the same problem at the same time. Also, it encourages the people who are closest to the problem to create the best possible result in the time allotted, given the current context.<\/p>\n
Question 23Skipped<\/p>\n
True or False, In large organizations multiple scrum teams work on the same product. In this scenario, Scrum Team should use a single Product Backlog?<\/p>\n
Correct answer<\/p>\n
True.<\/p>\n
False.<\/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
Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product i.e. it is a one to one relationship between Product and Product Backlog. In this scenario, they must mutually define and comply with the same Definition of Done.<\/p>\n
Question 24Skipped<\/p>\n
After Sprint Planning, Product Owner finds that it makes sense to develop a new functionality. (choose the best option)<\/p>\n
Developers will add that to the Sprint Backlog.<\/p>\n
Correct answer<\/p>\n
Developers can review that for selection in the next Sprint.<\/p>\n
Developers can swap existing functionality for the new functionality.<\/p>\n
Developers can create a technical spike & pull this to the current sprint.<\/p>\n
Overall explanation<\/p>\n
Product Owner can’t introduce new functionality in the middle of the Sprint unless developers get more capacity to work and they mutually agree to take this in. After the Product Owner adding the new functionality and ordering it to be on the top of the Product Backlog, developers can review that for selection in the next Sprint Planning.<\/p>\n
Question 25Skipped<\/p>\n
After Sprint Planning, Product Owner finds that it makes sense to develop a new functionality. (choose the best option)<\/p>\n
Developers will add that to the Sprint Backlog.<\/p>\n
Correct answer<\/p>\n
Developers can review that for selection in the next Sprint.<\/p>\n
Developers can swap existing functionality for the new functionality.<\/p>\n
Developers can create a technical spike & pull this to the current sprint.<\/p>\n
Overall explanation<\/p>\n
Product Owner can’t introduce new functionality in the middle of the Sprint unless developers get more capacity to work and they mutually agree to take this in. After the Product Owner adding the new functionality and ordering it to be on the top of the Product Backlog, developers can review that for selection in the next Sprint Planning.<\/p>\n
Question 26Skipped<\/p>\n
In a Retrospective, a Scrum Team decides to revise the Sprint length. Pick the statements which are correct about Sprint length. (choose the best three options)<\/p>\n
Sprint length can extend as long as required to complete all the work identified in Sprint Backlog.<\/p>\n
Correct selection<\/p>\n
It is better to have Sprints of consistent length through the Scrum journey.<\/p>\n
Correct selection<\/p>\n
The new Sprint length needs to be agreed by Product Owner.<\/p>\n
Correct selection<\/p>\n
Sprint can have a maximum duration of one month.<\/p>\n
Overall explanation<\/p>\n
The Product Owner needs to ensure that it is short enough to limit business risks and also short enough so the team can synchronize the development work with other business events. Please note that the finalized Sprint length cannot be longer than 1 calendar month.<\/p>\n
Question 27Skipped<\/p>\n
James is a product owner for a scrum team. The customer has expressed concerns about releasing new software after every sprint. What should James do? (choose the best option)<\/p>\n
An increment must be released after a sprint, James should insist on longer sprints to meet the customers longer release cycle.<\/p>\n
Correct answer<\/p>\n
An increment only needs to be potentially releasable, James may hold back several increments and work with the customer on a release schedule that fits their needs.<\/p>\n
James should ask the scrum master to put together a release planning meeting to help convince the customer of the value of incremental release.<\/p>\n
An increment must be released after a sprint, James should explain to the customer what scrum is and how scrum handles releases.<\/p>\n
Overall explanation<\/p>\n
The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. 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. The increment must be in useable condition regardless of whether the Product Owner decides to release it.<\/p>\n
Question 28Skipped<\/p>\n
Mark is a product owner for a scrum team. He wants to get some additional product backlog items added to the current sprint backlog. Sprint planning has already happened, what should Mark do? (choose the best option)<\/p>\n
Mark should bring it up at a daily scrum meeting and discuss it with developers; adding additional time to the daily scrum if needed.<\/p>\n
Correct answer<\/p>\n
Mark should hold a separate meeting with developers and discuss the options of adding some additional items; developers can consider the possibility and may be able to accommodate the additional work.<\/p>\n
Mark should just add the items to the sprint backlog, the self-managing Developers will figure out the best way to accommodate the additional work.<\/p>\n
Mark should consult with the scrum master; the scrum master will make the final call as to whether the work will be added to the current sprint.<\/p>\n
Overall explanation<\/p>\n
The Sprint Backlog makes visible all the work that developers identifies as necessary to meet the Sprint Goal. . Developers modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as developers works through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, developers adds it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only developers can change its Sprint Backlog during a Sprint. So Mark should discuss with Developers for the possibility of accommodating this additional work.<\/p>\n
Question 29Skipped<\/p>\n
Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. Who has the final deciding authority on whether to release it or not? (choose the best option).<\/p>\n
Developers.<\/p>\n
The Product Owner.<\/p>\n
The Scrum Master.<\/p>\n
Correct answer<\/p>\n
The Scrum Team.<\/p>\n
The stakeholders<\/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 Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. In the past, the Product Owner was the release decision-maker but now the release decision is on the whole scrum team.<\/p>\n
Question 30Skipped<\/p>\n
The Developers find out during the Sprint that they are not likely to build everything they forecast. What would you expect a Product Owner to do?<\/p>\n
(choose the best answer)<\/p>\n
Cancel the Sprint.<\/p>\n
Skip Product Backlog refinement activities.<\/p>\n
Change the Sprint Goal.<\/p>\n
Correct answer<\/p>\n
Re-negotiate the selected Product Backlog items with the Developers.<\/p>\n
Inform management that more resources are needed.<\/p>\n
Overall explanation<\/p>\n
During the Sprint. scope may be clarified and re-negotiated between the Product Owner and Developers as more is learned.<\/p>\n
Question 31Skipped<\/p>\n
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
Never. The entire Scrum Team is accountable for creating value every Sprint.<\/p>\n
During the Daily Scrum.<\/p>\n
Whenever a team member can accommodate more work.<\/p>\n
At the Sprint Planning Event.<\/p>\n
Overall explanation<\/p>\n
All members of the Scrum Team share in the accountability for creating value every Sprint.<\/p>\n
Question 32Skipped<\/p>\n
True or false? Our velocity was 250 at the end of the 6th Sprint. It has become 275 at the end of the 8th Sprint. Therefore, we’re creating more value now compared to before.<\/p>\n
Correct answer<\/p>\n
FALSE<\/p>\n
TRUE<\/p>\n
Overall explanation<\/p>\n
FALSE, There’s no direct relationship between velocity (speed) and value; e.g., maybe we’re working faster on less valuable items, in which case, velocity will be higher, but value may be the same, higher, or lower. Many people consider velocity as the most important criterion, but that’s not true — we should rather be focused on value, Sprint Goal, and Product Goal.<\/p>\n
Question 33Skipped<\/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 34Skipped<\/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 35Skipped<\/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\u2019s 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 36Skipped<\/p>\n
The Product Backlog is the single source of requirements for any changes to be made to the product. How should a Product Backlog item be refined when it is located at the top? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
It should be clear which developer is responsible for it.<\/p>\n
Correct selection<\/p>\n
In a way that it can be \u201cDone\u201d in the timeboxed duration of one Sprint<\/p>\n
Correct selection<\/p>\n
In a way that\u2019s clear enough for the developers.<\/p>\n
All the tasks required for completing it should be identified.<\/p>\n
Overall explanation<\/p>\n
Items at the top of the Product Backlog should be small enough to fit in one Sprint. They should also be clear and detailed enough; but not too detailed (e.g. not with all the tasks identified), as it would be upfront planning. Tasks are created gradually during the Sprint. Product Backlog items require multiple expertise and usually done by multiple developers. Therefore, they are not assigned. Tasks, however, are assigned to the individual developers, while everyone stays accountable.<\/p>\n
Question 37Skipped<\/p>\n
Why should there be only one Product Owner per product?<\/p>\n
Choose only ONE best answer.<\/p>\n
There should be one Product Owner for each team. If more than one team is working on the same product, multiple Product Owners might be needed.<\/p>\n
Correct answer<\/p>\n
Developers know who\u2019s responsible for prioritization<\/p>\n
One person is always enough for this role<\/p>\n
It becomes confusing when more than one Product Owner is managing the team.<\/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\u2019s priority must address the Product Owner. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner\u2019s 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 and developers know who\u2019s responsible for prioritization.<\/p>\n
Question 38Skipped<\/p>\n
This accountability in Scrum must know the most about the product and performance of the product<\/p>\n
Choose only ONE best answer.<\/p>\n
The Scrum Master<\/p>\n
The Scrum Team<\/p>\n
Correct answer<\/p>\n
The Product Owner<\/p>\n
The project manager<\/p>\n
The Product Master<\/p>\n
Overall explanation<\/p>\n
Measuring the release or product performance is the Product Owner’s responsibility. Measuring Sprint performance is the responsibility of Developers.<\/p>\n
Question 39Skipped<\/p>\n
Which statements are correct about a Sprint Backlog item that was not finished until the end of the Sprint? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
It won’t be demonstrated at the Sprint Review meeting<\/p>\n
It must be completed in the next Sprint<\/p>\n
Correct selection<\/p>\n
It will be moved back to the Product Backlog<\/p>\n
It will be demonstrated to the stakeholders but pointed out that it’s not complete yet<\/p>\n
The Product Owner has to extend the Sprint until the item is done<\/p>\n
Overall explanation<\/p>\n
Only the 100% complete items are demonstrated, to avoid confusion. When something is not complete, it will be moved back to the Product Backlog. If it’s still on the top of the Product Backlog, development will continue in the next Sprint (if it will be required)<\/p>\n
Question 40Skipped<\/p>\n
The main goal for the Product Owner is to maximize the value of the product. But how should the Product Owner forecast the completion date?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
By any method the PO finds appropriate<\/p>\n
By dividing the remaining amount of work in the Product Backlog to the latest calculated velocity<\/p>\n
By using a trend line in the burn-down chart<\/p>\n
It is not the responsibility of the Product Owner. The Scrum Master must forecast the completion date<\/p>\n
Overall explanation<\/p>\n
Using a trend line in the burn-down chart can help (if the team is using that chart), as well as simple or complex formulas such as the one mentioned above. But all of these are just guides for the Product Owner and she should consider all factors and come up with a reliable completion date forecast.<\/p>\n
Question 41Skipped<\/p>\n
In Scrum, when a Product Backlog item or an Increment is described as "Done", everyone in the team must understand what "Done" means. From the following answers, choose the LEAST accurate statement about the Definition of "Done"?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct selection<\/p>\n
The Product Owner creates it<\/p>\n
The Scrum Team may define it<\/p>\n
It may vary depending on the product<\/p>\n
It may evolve during the product life<\/p>\n
Overall explanation<\/p>\n
The DoD is not created by the Product Owner. If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriately for the product.<\/p>\n
Question 42Skipped<\/p>\n
The Product Owner should be expertly aware of the marketplace for the product.<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
True<\/p>\n
False<\/p>\n
It depends<\/p>\n
Overall explanation<\/p>\n
Product Owner should be expertly aware of the marketplace for the product. They should constantly be gathering and re-gathering information and data regarding the marketplace so that the product value is maximized. Getting out of touch with the marketplace can be a recipe for product disaster.<\/p>\n
Question 43Skipped<\/p>\n
The Product Owner is the sole person accountable for managing the Product Backlog.<\/p>\n
Choose only ONE best answer.<\/p>\n
False<\/p>\n
Correct answer<\/p>\n
True<\/p>\n
Overall explanation<\/p>\n
The Product Owner is accountable for effective Product Backlog management, which includes:<\/p>\n
Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood.<\/p>\n
Question 44Skipped<\/p>\n
Select 2 true statements about Scrum<\/p>\n
Choose ALL answers that apply.<\/p>\n
Scrum is a methodology for managing complex projects<\/p>\n
Scrum is a traditional process but with Sprints and related artefacts<\/p>\n
Correct selection<\/p>\n
Scrum is a framework for developing and maintaining complex products<\/p>\n
Correct selection<\/p>\n
Scrum is based on empirical process control theory<\/p>\n
Overall explanation<\/p>\n
Scrum is a framework, not a methodology or body of knowledge. Scrum is empirical, rather than theoretical. Scrum is more about project delivery rather than project management. Scrum is adaptive, rather than predictive (it’s more than just using Sprints and related artefacts). Scrum should be used entirely (we do not tailor it)<\/p>\n
Question 45Skipped<\/p>\n
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. The stakeholders are invited to the Sprint Review in order to:<\/p>\n
Choose only ONE best answer.<\/p>\n
Provide feedback on the team working style<\/p>\n
Provide feedback on Scrum implementation<\/p>\n
Correct answer<\/p>\n
Provide feedback on the Increment<\/p>\n
Provide feedback on design and architecture<\/p>\n
Overall explanation<\/p>\n
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.<\/p>\n
Question 46Skipped<\/p>\n
The Product Backlog Refinement is not a mandatory event in Scrum. However, almost all Scrum Teams are holding this event. From the following answers select all correct benefits of the Product Backlog Refinement<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
Clarify Value<\/p>\n
Correct selection<\/p>\n
Reduce Dependencies<\/p>\n
Decrease velocity<\/p>\n
Improve relationship in the Scrum Team<\/p>\n
Correct selection<\/p>\n
Incorporate Learning<\/p>\n
Overall explanation<\/p>\n
In general there are 6 important benefits of the PBR. Here they are: – Increase transparency-Clarify value – Break things into consumable pieces – Reduce dependencies – Forecasting – Incorporate learning<\/p>\n
Question 47Skipped<\/p>\n
A stakeholder is a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Who are the typical key stakeholders in Scrum? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
The people responsible for making the funding decisions for the product development effort<\/p>\n
The people responsible for product marketing<\/p>\n
Correct selection<\/p>\n
The people who actually use the product under development<\/p>\n
Correct selection<\/p>\n
The people responsible for paying to use the product<\/p>\n
The people responsible for product development<\/p>\n
The people from the security department<\/p>\n
Overall explanation<\/p>\n
Typical stakeholder is the man who is responsible for making the funding decisions for the product development effort, the user of the product, the man who is responsible for paying to use the product<\/p>\n
Question 48Skipped<\/p>\n
Which of the following is the LEAST productive way for the Scrum Master to improve communication between Developers and the Product Owner?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
Giving the order to all members of the team and act as a go-between for them<\/p>\n
Suggest effective communication tools and techniques to the Product Owner<\/p>\n
Monitor their communication performance<\/p>\n
Teach them how to communicate effectively<\/p>\n
Overall explanation<\/p>\n
Acting as a go-between weakens the team. Also, the Scrum Master is not the team leader (in people management), he or she can’t manage the team and give any order. But The Scrum Master is supposed to teach and coach and be the leader in serving the team.<\/p>\n
Question 49Skipped<\/p>\n
One of the most challenging activities in Scrum is Product Backlog Refinement (although the PBR is not an event in Scrum). How should a Product Backlog item be refined before its development begins? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
In a way that it’s clear enough for Developers<\/p>\n
It should be clear which member of the Scrum Team is responsible for it.<\/p>\n
Correct selection<\/p>\n
In a way that it can be "Done" in the time-boxed duration of one Sprint<\/p>\n
All the tasks required for completing it should be identified.<\/p>\n
Overall explanation<\/p>\n
A Product Backlog should be refined in a way that it’s clear enough for Developers and it can be "Done" in the time-boxed duration of one Sprint<\/p>\n
Question 50Skipped<\/p>\n
Which two statements are correct during the Sprint?<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
The scope may be clarified as more is learned<\/p>\n
Some Sprint Backlog items will be replaced with items from the Product Backlog if the priorities change<\/p>\n
Correct selection<\/p>\n
The scope may be re-negotiated as more is learned<\/p>\n
Some Sprint Backlog items would be moved back to the Product Backlog to be completed in future Sprints<\/p>\n
Overall explanation<\/p>\n
During the Sprint: No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product Owner and Developers as more is learned.<\/p>\n
Question 51Skipped<\/p>\n
The most important stakeholder wants a new feature to be added to the current Sprint. What is the best response for Developers in this situation?<\/p>\n
Choose only ONE best answer.<\/p>\n
Correct answer<\/p>\n
Ask the Product Owner to work with the customer<\/p>\n
Reject the request<\/p>\n
Add the item to the bottom of the Sprint Backlog<\/p>\n
Swap the item with one of the items in the Sprint Backlog<\/p>\n
Add the item to the Product Backlog<\/p>\n
Overall explanation<\/p>\n
No one can’t add additional items to Product Backlog (source for development work) except the Product Owner. First stakeholder has to discuss it with the Product Owner<\/p>\n
Question 52Skipped<\/p>\n
How many Product Goals can have a Scrum team at a moment?<\/p>\n
Choose only ONE best answer.<\/p>\n
No more than 3 Product Goals<\/p>\n
Correct answer<\/p>\n
No more than 1 Product Goal<\/p>\n
Unlimited numbers of Product Goals<\/p>\n
Overall explanation<\/p>\n
You can only have one Product Goal, so when the current Product Goal is achieved a new one would be created. If there is a significant change in context and the current Product Goal has not been achieved then the Scrum Team would replace the Product Goal with a more fitting one. If the Product is no longer relevant in the market (remember floppy disks, video cassettes, etc ), then the organization would either pivot or fold.<\/p>\n
Question 53Skipped<\/p>\n
A Definition of Done drives the quality of work and is used to assess when a task has been completed. But what are the benefits of having tests in the definition of \u201cDone\u201d? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
Increments would be closer to being potentially shippable<\/p>\n
Correct selection<\/p>\n
Increased transparency and the quality of the Increments<\/p>\n
Correct selection<\/p>\n
Increments would be more complete<\/p>\n
Reporting would be easier for the project manager<\/p>\n
Overall explanation<\/p>\n
Developers deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it. If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "Done" for an increment is not a convention of the development organization, Developers of the Scrum Team must define a definition of "Done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, Developers on all Scrum Teams must mutually define the definition of "Done". Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together. As Scrum Teams mature, it is expected that their definitions of "Done" will expand to include more stringent criteria for higher quality. New definitions, as used, may uncover work to be done in previously \u201cDone\u201d increments. An product or system should have a definition of "Done" that is a standard for any work done on it.<\/p>\n
Question 54Skipped<\/p>\n
The Scrum Team has just finished the Sprint Planning. According to this, choose all correct statements from the following answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
After the Sprint Planning, a Sprint cannot proceed without complete requirement specification<\/p>\n
Correct selection<\/p>\n
After the Sprint Planning, a Sprint cannot proceed without a Sprint Goal<\/p>\n
Correct selection<\/p>\n
After the Sprint Planning, a Sprint can proceed without complete Sprint Backlog<\/p>\n
After the Sprint Planning, a Sprint cannot proceed without complete design and BRD or FSD<\/p>\n
Overall explanation<\/p>\n
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to Developers on why they are building the increment. It is created during the Sprint Planning meeting. As new work is required, Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed.<\/p>\n
Question 55Skipped<\/p>\n
According to the Scrum Guide, that is the reason why the Daily Scrum should hold at the same time and the same place<\/p>\n
Choose only ONE best answer.<\/p>\n
It makes easier to book the rooms<\/p>\n
Because the place can be named<\/p>\n
Because the Product Owner requires it<\/p>\n
Correct answer<\/p>\n
To reduce complexity and overheat<\/p>\n
Overall explanation<\/p>\n
The Daily Scrum is held at the same time and place each day to reduce complexity.<\/p>\n
Question 56Skipped<\/p>\n
According to the Scrum Guide, Scrum is founded on empiricism and lean thinking. What else is true about Scrum? Select all correct answers<\/p>\n
Choose ALL answers that apply.<\/p>\n
Scrum is a methodology for managing complex projects<\/p>\n
Scrum is a traditional process but with Sprints and related artefacts<\/p>\n
Correct selection<\/p>\n
Scrum is a framework for developing and maintaining complex products<\/p>\n
Correct selection<\/p>\n
Scrum employs an iterative, incremental approach to optimize predictability and control risk.<\/p>\n
Overall explanation<\/p>\n
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Scrum engages groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.<\/p>\n
Question 57Skipped<\/p>\n
During a Sprint Review, stakeholders notice that the product development progress is not clearly visible and lacked transparency. Moreover, they are not able to understand the next steps. Who is responsible for this?<\/p>\n
Choose only ONE best answer.<\/p>\n
Developers<\/p>\n
Correct answer<\/p>\n
Product Owner<\/p>\n
Scrum Master<\/p>\n
Scrum Team<\/p>\n
Overall explanation<\/p>\n
The PO is ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next The Product Owner is the Lead Facilitator of Key Stakeholder Involvement. The PO is responsible for identifying the key stakeholders for the product and involving them as necessary throughout the development effort.<\/p>\n
Question 58Skipped<\/p>\n
The Scrum Team consists of the PO, SM and Developers. One of the responsibilities of Scrum Master is to find, track and help remove different obstacles. But who supports the Scrum Master in removing obstacles? Choose all correct answers from the<\/p>\n
following<\/p>\n
Choose ALL answers that apply.<\/p>\n
The Project Manager<\/p>\n
Correct selection<\/p>\n
The senior management<\/p>\n
The senior Developer<\/p>\n
Correct selection<\/p>\n
Developers<\/p>\n
Overall explanation<\/p>\n
Developers can help the Scrum Master because of their understanding of how the work is done. Some impediments are rooted in external causes, and that\u2019s why the Scrum Master might need to have the senior management’s support in removing them<\/p>\n
Question 59Skipped<\/p>\n
The Product Backlog is baselined at the beginning of the project.<\/p>\n
Choose only ONE best answer.<\/p>\n
True<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
There is no such action in Scrum as baselining the product backlog<\/p>\n
Question 60Skipped<\/p>\n
The role of Scrum Master in Sprint Retrospective is<\/p>\n
Choose only ONE best answer.<\/p>\n
Auditor<\/p>\n
Peer Team Member<\/p>\n
Correct answer<\/p>\n
None of the above<\/p>\n
Business analyst<\/p>\n
Overall explanation<\/p>\n
The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process, As a team member, the Scrum Master (tike any other member} identifies the most helpful changes to improve the effectiveness of the Scrum Team<\/p>\n
Question 61Skipped<\/p>\n
According to the Scrum Guide, the Product Owner can transfer some of his\/her accountability to Developers<\/p>\n
Choose only ONE best answer.<\/p>\n
True<\/p>\n
Correct answer<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is also accountable for effective Product Backlog management, which includes: – Developing and explicitly communicating the Product Goal; – Creating and clearly communicating Product Backlog items; – Ordering Product Backlog items; – 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 62Skipped<\/p>\n
The Product Owner has some problems with managing the Product Backlog. What is the right action from the Scrum Master in this situation?<\/p>\n
Choose only ONE best answer.<\/p>\n
Extend the Sprint, so that the Product Owner has more time to order items<\/p>\n
Correct answer<\/p>\n
Help the Product Owner to find techniques for effective Product Goal definition and Product Backlog management<\/p>\n
Ask Developers help the Product Owner understand the dependencies among items to be used in ordering them<\/p>\n
Ask the stakeholder to change the Product Owner<\/p>\n
Overall explanation<\/p>\n
The Scrum Master serves the Product Owner in several ways, including:<\/p>\n
Helping find techniques for effective Product Goal definition and Product Backlog management;<\/p>\n<\/li>\n
Helping the Scrum Team understand the need for clear and concise Product Backlog items;<\/p>\n<\/li>\n
Helping establish empirical product planning for a complex environment;<\/p>\n<\/li>\n
Facilitating stakeholder collaboration as requested or needed.<\/p>\n<\/li>\n<\/ul>\n
Question 63Skipped<\/p>\n
There are many responsibilities in Scrum for the Product Owner. From the following answers choose three of them<\/p>\n
Choose ALL answers that apply.<\/p>\n
Correct selection<\/p>\n
Break down epic items into smaller ones<\/p>\n
Correct selection<\/p>\n
Create user stories (if the Scrum Team uses user story format as a task)<\/p>\n
Correct selection<\/p>\n
Prioritize the Product Backlog<\/p>\n
Design Software<\/p>\n
Facilitate meetings<\/p>\n
Provide estimates<\/p>\n
Make technical decisions<\/p>\n
Overall explanation<\/p>\n
Designing the software is part of the development and should be done by the developers. They make technical decisions, and volunteer for tasks (assign them to themselves). Estimation is the responsibility of the developers because they are the people who will develop the item. The rest (from the following) are done by the Product Owner.<\/p>\n
Question 64Skipped<\/p>\n
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. The stakeholders are invited to the Sprint Review in order to:<\/p>\n
Choose only ONE best answer.<\/p>\n
Provide feedback on the team working style<\/p>\n
Provide feedback on Scrum implementation<\/p>\n
Correct answer<\/p>\n
Provide feedback on the Increment<\/p>\n
Provide feedback on design and architecture<\/p>\n
Overall explanation<\/p>\n
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.<\/p>\n
Question 65Skipped<\/p>\n
Who is required to attend the Daily Scrum?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
The Developers.<\/p>\n
The Developers and Product Owner.<\/p>\n
The Scrum Team.<\/p>\n
The Scrum Master and Product Owner.<\/p>\n
The Developers and Scrum Master.<\/p>\n
Overall explanation<\/p>\n
Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog. they participate as Developers, they will need to be at the Daily Scrum.<\/p>\n
Question 66Skipped<\/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) in Scrum: Daily Scrum<\/p>\n
Question 67Skipped<\/p>\n
Which statement best describes Scrum?<\/p>\n
(choose the best answer)<\/p>\n
A cookbook that defines best practices for software development.<\/p>\n
A defined and predictive process that conforms to the principles of Scientific Management.<\/p>\n
Correct answer<\/p>\n
A framework for creating complex products in complex environments.<\/p>\n
A complete methodology that defines how to develop software.<\/p>\n
Overall explanation<\/p>\n
Scrum is a lightweight framework that helps people. teams and organizations generate value through adaptive solutions for complex problems.<\/p>\n
Question 68Skipped<\/p>\n
How do timeboxes help the Product Owner and the other members of the Scrum Team validate assumptions, adapt, and maximize the value of their product?<\/p>\n
(choose the best answer)<\/p>\n
Timeboxes help by making sure a Sprint does not stop until all testing is done, and the work is verified by the Product Owner<\/p>\n
Timeboxes assure the Product Owner that the Developers will finish all work on the Sprint Backlog by the end of the Sprint.<\/p>\n
At the end of each Sprint when the timebox expires a detailed report with all test cases and test results is available.<\/p>\n
Correct answer<\/p>\n
Timeboxes help minimize risk by creating the opportunity to validate assumptions using feedback from users and the market; allowing Scrum Teams to inspect progress toward the Product Goal and decide whether to pivot or persevere.<\/p>\n
Overall explanation<\/p>\n
The Product Owner manages the Product Backlog against the assumption that value will be generated. This assumption remains invalidated when not checked against users and the market. When a Sprints horizon is too long. you increase the risk that what is being developed may no longer be desired. Sprints limit risk to one calendar month or less of work.<\/p>\n
Question 69Skipped<\/p>\n
True or False: A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place.<\/p>\n
Correct answer<\/p>\n
True<\/p>\n
False<\/p>\n
Overall explanation<\/p>\n
A first Sprint requires no more than a Scrum Team and enough ideas to potentially complete a full Sprint.<\/p>\n
Question 70Skipped<\/p>\n
To what extent does technical debt limit the value a Product Owner can get from a product?<\/p>\n
(choose the best two answers)<\/p>\n
Correct selection<\/p>\n
Technical debt causes a greater percentage of the products budget to be spent on maintenance of the product.<\/p>\n
Correct selection<\/p>\n
The velocity at which new functionality can be created is reduced when you have technical debt.<\/p>\n
Technical debt is not a Product Owner concern, technical debt is only an issue for the Developers.<\/p>\n
Technical debt does not influence the delivery of value.<\/p>\n
Overall explanation<\/p>\n
Technical debt does influence and it is a concern of the PO.<\/p>\n
Question 71Skipped<\/p>\n
Adaptation requires regular inspection. In what ways does the Product Owner contribute to the results achieved by inspection ?<\/p>\n
(choose the best two answers)<\/p>\n
The Product Owner inspects the Sprint burn-down at the Daily Scrum for progress towards a complete Increment and re-planning the team’s work.<\/p>\n
Correct selection<\/p>\n
The Product Owner invites stakeholders to the Sprint Review to learn how the current state of the marketplace influences what is the most valuable thing to do next.<\/p>\n
The Product Owner verifies the Sprint Backlog for completeness at the end of Sprint Planning in order to allow the Sprint to start.<\/p>\n
Correct selection<\/p>\n
The Product Owner shares the current state of Product Backlog at the Sprint Review, which, combined with the inspection of the Increment, leads to an updated Product Backlog.<\/p>\n
Overall explanation<\/p>\n
Scrum users must frequently inspect Scrum artifacts and progress to detect undesirable variances. The primary tool for the Product Owner to uphold transparency is the Product Backlog. Product Backlog is a living artifact that is actively maintained and updated to reflect reality. At the Sprint Review, attendees collaborate on the next things that could be done to optimize value. which is processed into an updated Product Backlog.<\/p>\n
Question 72Skipped<\/p>\n
What best describes the relationship of the Product Owner and the stakeholders?<\/p>\n
(choose the best answer)<\/p>\n
The Product Owner writes the User Stories as provided by the stakeholders.<\/p>\n
The Product Owner provides the stakeholders with acceptance forms at the Sprint Review to record their formal agreement over the delivered software.<\/p>\n
The Product Owner has the final call over the requirements and should involve the stakeholders as little as possible.<\/p>\n
Correct answer<\/p>\n
The Product Owner actively asks for stakeholder input and expectations to incorporate into the Product Backlog.<\/p>\n
Overall explanation<\/p>\n
The Product Owner represents the stakeholders to the Scrum Team. which includes representing their desired requirements in the Product Backlog. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is also accountable for effective Product Backlog management.<\/p>\n
Question 73Skipped<\/p>\n
What are typical activities for a Product Owner in a Sprint?<\/p>\n
(choose the best two answers)<\/p>\n
Create financial reporting upon the spent hours reported by the Scrum Team.<\/p>\n
Correct selection<\/p>\n
Collaborate with stakeholders, user communities, and subject matter experts.<\/p>\n
Update the work plan for the Developers on a daily basis.<\/p>\n
Correct selection<\/p>\n
Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items.<\/p>\n
Overall explanation<\/p>\n
The Product Owner represents the needs of many stakeholders in the Product Backlog. This typically requires active interaction in order to be able to represent stakeholders and their needs. Product Backlog refinement is an ongoing process in which the Product Owner and the Developers may collaborate on the details of Product Backlog items.<\/p>\n
Question 74Skipped<\/p>\n
How does an organization know that a product built using Scrum is successful?<\/p>\n
(choose the best answer)<\/p>\n
Correct answer<\/p>\n
By releasing frequently, and measuring the value customers\/users experience.<\/p>\n
By measuring that velocity has increased since the last release.<\/p>\n
By measuring the actual time spent on development versus the time estimated for development.<\/p>\n
By the Product Owner and stakeholders accepting the Increment at the Sprint Review.<\/p>\n
Overall explanation<\/p>\n
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. If a product is not released. the opportunity to capture user and market feedback is lost.<\/p>\n
Question 75Skipped<\/p>\n
What is the principal value of releasing an Increment?<\/p>\n
(choose the best answer)<\/p>\n
To learn about the Scrum Team’s productivity.<\/p>\n
Correct answer<\/p>\n
To validate assumptions made when developing the product.<\/p>\n
To learn about the forecast of functionality that was developed.<\/p>\n
Overall explanation<\/p>\n
Releasing the Increment to customers\/users is the only way to validate assumptions about value.<\/p>\n
Question 76Skipped<\/p>\n
The Product Owner’s authority to change and update the Product Backlog is unlimited, except for:<\/p>\n
(choose the best answer)<\/p>\n
Decisions by the chief program manager.<\/p>\n
Technical and architectural work that needs to be done first, as indicated by the chief enterprise architect.<\/p>\n
Decisions by the CFO, the CEO or the board of directors.<\/p>\n
Correct answer<\/p>\n
There are no exceptions; the entire organization must respect a Product Owner’s decisions.<\/p>\n
High impact changes that have not been approved by the change request board.<\/p>\n
Items the Scrum Master has identified as impediments.<\/p>\n
Overall explanation<\/p>\n
Everyone in the Team and in the organization must respect PO decision.<\/p>\n
Question 77Skipped<\/p>\n
Which two statements explain why the Definition of Done is important to the Product Owner?<\/p>\n
(choose the best two answers)<\/p>\n
It identifies undone work that can be addressed in a separate Sprint.<\/p>\n
Correct selection<\/p>\n
It creates transparency regarding progress within the Scrum Team.<\/p>\n
It helps the Product Owner track the open work during a Sprint.<\/p>\n
Correct selection<\/p>\n
It establishes the expected quality of the Increment reviewed at the Sprint Review.<\/p>\n
Overall explanation<\/p>\n
All Scrum Team members must have a shared understanding of what it means for work to be complete. to ensure transparency. This is the Definition of Done for the Scrum Team and is used to assess when work is complete on the product Increment. The Increment reviewed at the Sprint Review must meet the Definition of Done.<\/p>\n
Question 78Skipped<\/p>\n
When can the Product Backlog be updated?<\/p>\n
(choose the best answer)<\/p>\n
Never, unless agreed to by the change request.<\/p>\n
Only after a Sprint Review if agreed to by the stakeholders.<\/p>\n
Correct answer<\/p>\n
At any time when done by the Product Owner or a delegate.<\/p>\n
Only during Product Backlog refinement sessions if the Product Owner is present.<\/p>\n
Overall explanation<\/p>\n
The Product Backlog is dynamic: it constantly changes to identify what the product needs in order to be appropriate, competitive, and useful. Product Backlog items can be updated at any time by the Product Owner or a delegate. Even if the responsibility is delegated the Product Owner remains accountable for the Product Backlog.<\/p>\n
Question 79Skipped<\/p>\n
How important is it for a Product Owner to order Product Backlog items by using value points?<\/p>\n
(choose the best answer)<\/p>\n
Using value points is the ultimate way for a Product Owner to predict the value that the product will provide.<\/p>\n
Calculating value points is a predictive approach that conflicts with the empiricism of Scrum, and is therefore not acceptable.<\/p>\n
Correct answer<\/p>\n
The Product Owner may order the Product Backlog by using value points or select another technique, the decision is up to them.<\/p>\n
Overall explanation<\/p>\n
The Product Owner is accountable for ordering the Product backlog, regardless of the techniques they may utilize to define that order. Indications of value on Product Backlog items may be useful but are only a prediction until validated by users and the market.<\/p>\n
Question 80Skipped<\/p>\n
Which of the following are needed in order to allow Sprint Planning to begin?<\/p>\n
(choose the best two answers)<\/p>\n
A fully refined Product Backlog.<\/p>\n
A clear cadence of when the Daily Scrum will take place.<\/p>\n
Correct selection<\/p>\n
A Product Backlog with the most important items ready for discussion.<\/p>\n
Formal budget approval to conduct another Sprint.<\/p>\n
Correct selection<\/p>\n
A Product Goal communicated by the Product Owner<\/p>\n
A clear and non-negotiable Sprint Goal.<\/p>\n
Overall explanation<\/p>\n
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. The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal.<\/p>\n","protected":false},"excerpt":{"rendered":"
PSPO1 Practice Exam Set One – Question 1Skipped User documentation is part of your definition of "Done." However, there aren’t enough technical writers for all teams. Your Development Team doesn’t have a technical writer. What should you do? (choose the best answer) Wait until you have a technical writer on your Development Team to take […]<\/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-212","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\/212","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=212"}],"version-history":[{"count":1,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/212\/revisions"}],"predecessor-version":[{"id":213,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=\/wp\/v2\/posts\/212\/revisions\/213"}],"wp:attachment":[{"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/exam.kimson.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}