{"id":16347,"date":"2026-09-19T06:50:43","date_gmt":"2026-09-19T06:50:43","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16347"},"modified":"2026-09-19T06:50:43","modified_gmt":"2026-09-19T06:50:43","slug":"scrum-psm-i-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/scrum-psm-i-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Scrum PSM I Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"

<\/h1>\n

View Full <\/b>Scrum PSM I Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

Question 261<\/b><\/h2>\n

What is the Scrum Team accountable for creating each Sprint?<\/b><\/p>\n

    \n
  1. A usable Increment<\/span><\/li>\n
  2. A detailed project schedule<\/span><\/li>\n
  3. A stakeholder contract<\/span><\/li>\n
  4. A finalized annual roadmap<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    The Scrum Team is accountable for creating a usable Increment during each Sprint. The Increment must meet the Definition of Done so that it represents a usable and valuable step toward the Product Goal. Scrum does not require the team to create a traditional project schedule or guarantee completion of every selected Product Backlog item. Instead, Developers inspect and adapt their plan while working toward the Sprint Goal. The Product Owner focuses on maximizing product value, while the Scrum Master supports effective Scrum. The shared responsibility of the Scrum Team centers on producing valuable product results.<\/span><\/p>\n

    Question 262<\/b><\/h2>\n

    Who is responsible for ordering the Product Backlog?<\/b><\/p>\n

      \n
    1. Scrum Master<\/span><\/li>\n
    2. Product Owner<\/span><\/li>\n
    3. Developers<\/span><\/li>\n
    4. External stakeholders<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      The Product Owner is accountable for ordering the Product Backlog. Ordering helps communicate which work is relatively more important for achieving product objectives and maximizing value. The Product Owner considers factors such as value, dependencies, risks, and available information when making ordering decisions. Developers can provide technical and delivery insights, while stakeholders can contribute useful feedback, but these contributions do not transfer the Product Owner’s accountability. Product Backlog ordering is also not necessarily permanent. As new information becomes available, the Product Owner can reorder items to reflect the current understanding of what should be pursued.<\/span><\/p>\n

      Question 263<\/b><\/h2>\n

      What does the Definition of Done primarily establish?<\/b><\/p>\n

        \n
      1. The team’s preferred meeting schedule<\/span><\/li>\n
      2. The Product Owner’s backlog order<\/span><\/li>\n
      3. The quality state required for an Increment<\/span><\/li>\n
      4. The number of Developers needed<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        The Definition of Done establishes the formal description of the state an Increment must reach when it meets the required quality measures. It creates a shared understanding of what completed work means within the Scrum Team. An Increment that does not satisfy the Definition of Done cannot be considered part of the Increment and should not be represented as completed. The Definition of Done therefore supports transparency and quality. It does not determine meeting schedules, Product Backlog ordering, or team size. These concerns belong to different aspects of Scrum and should not be confused with completion criteria.<\/span><\/p>\n

        Question 264<\/b><\/h2>\n

        Which event begins the planning work for a new Sprint?<\/b><\/p>\n

          \n
        1. Sprint Review<\/span><\/li>\n
        2. Daily Scrum<\/span><\/li>\n
        3. Sprint Retrospective<\/span><\/li>\n
        4. Sprint Planning<\/span><\/li>\n<\/ol>\n

          Correct Answer: 4<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          Sprint Planning initiates the new Sprint by establishing the foundation for the work ahead. During Sprint Planning, the Scrum Team collaborates on why the Sprint is valuable, what can be accomplished, and how the chosen work will be done. The resulting Sprint Goal becomes the commitment for the Sprint Backlog. Developers then create an actionable plan for delivering the Increment. Sprint Planning does not create a rigid promise that cannot change. The Sprint Backlog can be adapted as Developers learn more during the Sprint, while the Sprint Goal provides the central objective.<\/span><\/p>\n

          Question 265<\/b><\/h2>\n

          Which Scrum value supports being honest about difficult work?<\/b><\/p>\n

            \n
          1. Courage<\/span><\/li>\n
          2. Focus<\/span><\/li>\n
          3. Respect<\/span><\/li>\n
          4. Commitment<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            Courage is a Scrum value that supports team members doing the right thing and addressing difficult problems. Product development often involves uncertainty, technical challenges, conflicting information, or uncomfortable decisions. Scrum encourages people to raise concerns rather than hiding problems that could affect the product or Sprint Goal. Courage works together with the other Scrum values. For example, Openness supports transparency, while Respect enables productive collaboration. Courage does not mean taking unnecessary risks. It means being willing to address important issues and make appropriate decisions even when those decisions may be difficult.<\/span><\/p>\n

            Question 266<\/b><\/h2>\n

            What is the primary purpose of a Sprint Goal?<\/b><\/p>\n

              \n
            1. To document every technical task<\/span><\/li>\n
            2. To provide a single objective for the Sprint<\/span><\/li>\n
            3. To replace the Product Goal<\/span><\/li>\n
            4. To measure individual Developer performance<\/span><\/li>\n<\/ol>\n

              Correct Answer: 2<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              The Sprint Goal provides a single objective for the Sprint. It gives the Scrum Team a shared purpose and allows Developers some flexibility in determining the exact work needed to achieve that objective. The Sprint Goal is part of the Sprint Backlog and acts as a commitment for the Sprint. It does not replace the Product Goal, which represents a longer-term product objective. It also is not intended to evaluate individual Developer performance. As more is learned, Developers may adapt the Sprint Backlog while continuing to pursue the Sprint Goal, provided that the goal remains valuable.<\/span><\/p>\n

              Question 267<\/b><\/h2>\n

              Which artifact contains selected work for the current Sprint?<\/b><\/p>\n

                \n
              1. Product Backlog<\/span><\/li>\n
              2. Increment<\/span><\/li>\n
              3. Sprint Backlog<\/span><\/li>\n
              4. Product Goal<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                The Sprint Backlog contains the work selected for the current Sprint together with the Sprint Goal and an actionable plan for delivering the Increment. It represents the current plan maintained by the Developers. Unlike the Product Backlog, which contains the broader ordered work for the product, the Sprint Backlog focuses specifically on the current Sprint. Developers can update it as they gain knowledge or encounter new work needed to achieve the Sprint Goal. This makes the Sprint Backlog an evolving planning artifact rather than a fixed document that must remain unchanged throughout the Sprint.<\/span><\/p>\n

                Question 268<\/b><\/h2>\n

                What does the Sprint Retrospective inspect most directly?<\/b><\/p>\n

                  \n
                1. The Product Owner’s authority<\/span><\/li>\n
                2. The market price of the product<\/span><\/li>\n
                3. The customer’s contract terms<\/span><\/li>\n
                4. How the team worked during the Sprint<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  The Sprint Retrospective focuses on how the Scrum Team worked during the Sprint and how its effectiveness can be improved. The team considers individuals, interactions, processes, tools, and the Definition of Done. It then identifies useful improvements that can increase quality and effectiveness. The Retrospective is not primarily a commercial review or an evaluation of an individual’s authority. Its purpose is continuous improvement of the team’s way of working. The Scrum Team can select the most valuable improvements and address them as soon as possible, including during the next Sprint.<\/span><\/p>\n

                  Question 269<\/b><\/h2>\n

                  What does the Product Owner primarily seek to maximize?<\/b><\/p>\n

                    \n
                  1. Product value<\/span><\/li>\n
                  2. Developer workload<\/span><\/li>\n
                  3. Meeting frequency<\/span><\/li>\n
                  4. Documentation volume<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Product value can be influenced by customer needs, business opportunities, risks, market information, and many other factors. The Product Owner uses the Product Backlog to help communicate and order the work needed to pursue product objectives. Maximizing value does not simply mean delivering the greatest number of features. The Product Owner must consider what outcomes are valuable and make informed ordering decisions. Developers and stakeholders contribute important information, but product-value accountability remains with the Product Owner.<\/span><\/p>\n

                    Question 270<\/b><\/h2>\n

                    What happens when inspection identifies an unacceptable deviation?<\/b><\/p>\n

                      \n
                    1. The Scrum Team ignores it until Sprint completion<\/span><\/li>\n
                    2. The team adapts its approach when appropriate<\/span><\/li>\n
                    3. The Product Backlog is permanently frozen<\/span><\/li>\n
                    4. The Sprint automatically becomes longer<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 2<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      When inspection reveals that a process or resulting product is deviating in an unacceptable way, adaptation should occur as soon as possible. Scrum relies on frequent inspection so problems are identified early rather than being hidden until the end of development. Adaptation may involve changing the plan, adjusting practices, clarifying work, or taking another appropriate action. The exact response depends on what inspection reveals. Scrum does not automatically extend Sprints or freeze the Product Backlog. The combination of transparency, inspection, and adaptation enables the Scrum Team to respond effectively to changing information.<\/span><\/p>\n

                      Question 271<\/b><\/h2>\n

                      Which Scrum artifact is an emergent, ordered list of product work?<\/b><\/p>\n

                        \n
                      1. Sprint Backlog<\/span><\/li>\n
                      2. Increment<\/span><\/li>\n
                      3. Product Backlog<\/span><\/li>\n
                      4. Definition of Done<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        The Product Backlog is an emergent, ordered list of what is needed to improve the product. It evolves as the Scrum Team and stakeholders learn more about the product, users, technology, and environment. Items can be refined with additional detail and reordered as circumstances change. The Product Owner is accountable for effective Product Backlog management, including ordering and communication. The Sprint Backlog instead represents the current Sprint plan, while the Increment is the usable product result. The Definition of Done describes the quality state required for completed work and is not a list of product work.<\/span><\/p>\n

                        Question 272<\/b><\/h2>\n

                        Who creates and adapts the Sprint Backlog plan?<\/b><\/p>\n

                          \n
                        1. Product Owner<\/span><\/li>\n
                        2. Developers<\/span><\/li>\n
                        3. Scrum Master<\/span><\/li>\n
                        4. Customers<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 2<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          Developers create and adapt the plan contained in the Sprint Backlog. They determine how the selected work can be transformed into a usable Increment and update their plan as they learn more during the Sprint. This responsibility supports self-management because Developers decide how the work will be accomplished rather than receiving detailed technical instructions from outside the team. The Product Owner remains accountable for Product Backlog management and product value, while the Scrum Master supports effective Scrum. Customers and stakeholders can provide valuable information but do not manage the Developers’ Sprint plan.<\/span><\/p>\n

                          Question 273<\/b><\/h2>\n

                          What is the maximum Sprint length allowed by Scrum?<\/b><\/p>\n

                            \n
                          1. Two months<\/span><\/li>\n
                          2. Six weeks<\/span><\/li>\n
                          3. One month<\/span><\/li>\n
                          4. Three months<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            A Sprint has a fixed length of one month or less. Keeping Sprints within this maximum duration creates regular opportunities for inspection and adaptation. Shorter Sprints may reduce risk by allowing the Scrum Team to obtain feedback and respond to changing circumstances more frequently. The Sprint length itself does not change during an ongoing Sprint. Every new Sprint begins immediately after the previous Sprint ends. Scrum does not define a Sprint as a two-month, six-week, or three-month container. The fixed timebox supports a consistent rhythm for producing usable Increments and learning from results.<\/span><\/p>\n

                            Question 274<\/b><\/h2>\n

                            What is the main benefit of making Scrum artifacts transparent?<\/b><\/p>\n

                              \n
                            1. It eliminates all uncertainty<\/span><\/li>\n
                            2. It guarantees every item will be completed<\/span><\/li>\n
                            3. It prevents Product Backlog changes<\/span><\/li>\n
                            4. It enables meaningful inspection<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 4<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              Transparency enables meaningful inspection because people need a shared and understandable view of important information before they can evaluate it effectively. Scrum artifacts and their commitments are designed to make relevant information visible and understood. For example, the Product Backlog communicates product work and ordering, while the Sprint Backlog shows the current Sprint plan. The Definition of Done establishes a shared understanding of completed quality. Transparency does not eliminate uncertainty or prevent changes. Instead, it gives the Scrum Team a reliable basis for inspecting reality and deciding whether adaptation is necessary.<\/span><\/p>\n

                              Question 275<\/b><\/h2>\n

                              Who may cancel a Sprint when its goal becomes obsolete?<\/b><\/p>\n

                                \n
                              1. Product Owner<\/span><\/li>\n
                              2. Scrum Master<\/span><\/li>\n
                              3. Developers collectively<\/span><\/li>\n
                              4. Stakeholders<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                Only the Product Owner has the authority to cancel a Sprint. This may happen when the Sprint Goal becomes obsolete because continuing toward that objective no longer makes sense. Sprint cancellation is possible but should not be confused with ordinary adaptation of the Sprint Backlog. Developers can adapt their plan and negotiate scope while pursuing a valuable Sprint Goal. The Scrum Master does not independently cancel Sprints, and stakeholders do not possess this authority. If a Sprint is cancelled, completed work is reviewed and unfinished work is re-estimated before being considered for future Product Backlog work.<\/span><\/p>\n

                                Question 276<\/b><\/h2>\n

                                Which activity helps make future Product Backlog items better understood?<\/b><\/p>\n

                                  \n
                                1. Sprint cancellation<\/span><\/li>\n
                                2. Product Backlog refinement<\/span><\/li>\n
                                3. Individual performance appraisal<\/span><\/li>\n
                                4. Sprint extension<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  Product Backlog refinement helps the Scrum Team improve its understanding of future work. During refinement, Product Backlog items may receive additional description, ordering, and sizing information. The team can discuss assumptions, dependencies, technical considerations, and expected outcomes. Refinement is an ongoing activity rather than a formal Scrum event with a required timebox or fixed schedule. Its purpose is to make future work sufficiently understood for effective planning. Refinement does not guarantee that an item will eventually be selected for a Sprint because Product Backlog ordering can change as new information becomes available.<\/span><\/p>\n

                                  Question 277<\/b><\/h2>\n

                                  What does the Increment represent in Scrum?<\/b><\/p>\n

                                    \n
                                  1. A management approval document<\/span><\/li>\n
                                  2. A collection of unfinished tasks<\/span><\/li>\n
                                  3. A usable stepping stone toward the Product Goal<\/span><\/li>\n
                                  4. A forecast of future requirements<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 3<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    The Increment is a concrete stepping stone toward the Product Goal. It must be usable and meet the Definition of Done. A Scrum Team may create multiple Increments during a single Sprint, and an Increment may be delivered before the Sprint ends. Each Increment adds to previous Increments and must work with them. The Increment is therefore an actual product result rather than a forecast, administrative document, or collection of unfinished tasks. Stakeholders can inspect usable Increments to gain information that supports decisions about the product’s future direction and potential adaptations.<\/span><\/p>\n

                                    Question 278<\/b><\/h2>\n

                                    Why are Sprints fixed in length?<\/b><\/p>\n

                                      \n
                                    1. To create a consistent cadence for inspection and adaptation<\/span><\/li>\n
                                    2. To prevent all Product Backlog changes<\/span><\/li>\n
                                    3. To guarantee identical work every Sprint<\/span><\/li>\n
                                    4. To eliminate stakeholder involvement<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      Fixed-length Sprints create a consistent cadence for inspection and adaptation. By working within a predictable timebox, the Scrum Team regularly produces opportunities to inspect product results, learn from experience, and adjust future work. The fixed length does not mean the work itself must remain identical or that the Product Backlog cannot change. Instead, it provides a stable rhythm within which the team can respond to uncertainty. Regular inspection points can also reduce the risk of continuing for too long without meaningful feedback. This cadence is one reason Scrum uses repeated Sprints.<\/span><\/p>\n

                                      Question 279<\/b><\/h2>\n

                                      What does self-management mean for Scrum Developers?<\/b><\/p>\n

                                        \n
                                      1. Managers assign each technical activity<\/span><\/li>\n
                                      2. Developers determine internally who does what, when, and how<\/span><\/li>\n
                                      3. Stakeholders approve every implementation decision<\/span><\/li>\n
                                      4. The Product Owner controls daily technical execution<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        Self-management means that Developers internally decide who does what, when, and how. Scrum Teams are structured without sub-teams or hierarchies, allowing the people doing the work to organize themselves around the Sprint Goal. This does not mean Developers operate without accountability or direction. The Sprint Goal, Product Goal, Scrum accountabilities, and Definition of Done provide important boundaries. The Product Owner remains accountable for product value and Product Backlog management, while the Scrum Master supports effective Scrum. Self-management enables Developers to use their expertise and adapt their work without requiring constant task assignment.<\/span><\/p>\n

                                        Question 280<\/b><\/h2>\n

                                        What does the Sprint Review help the Scrum Team determine?<\/b><\/p>\n

                                          \n
                                        1. Individual salary adjustments<\/span><\/li>\n
                                        2. Permanent staffing levels<\/span><\/li>\n
                                        3. Which technical tasks must never change<\/span><\/li>\n
                                        4. What to consider doing next<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          The Sprint Review provides an opportunity to inspect the Sprint outcome and collaborate on what to consider doing next. The Scrum Team and stakeholders review the usable results and consider relevant information about the product and its environment. This information can influence future Product Backlog ordering and other product decisions. The event is therefore a working session focused on inspection and adaptation rather than an employee appraisal or rigid technical planning meeting. Because the product environment can change, the Sprint Review helps everyone develop a shared understanding of the current situation and discuss sensible next steps.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Scrum PSM I Exam Dumps and Practice Test Dumps.   Question 261 What is the Scrum Team accountable for creating each Sprint? A usable Increment A detailed project schedule A stakeholder contract A finalized annual roadmap Correct Answer: 1 Explanation: The Scrum Team is accountable for creating a usable Increment during each Sprint. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16347"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=16347"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16347\/revisions"}],"predecessor-version":[{"id":16403,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16347\/revisions\/16403"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}