{"id":16335,"date":"2026-09-19T06:55:15","date_gmt":"2026-09-19T06:55:15","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16335"},"modified":"2026-09-19T06:55:15","modified_gmt":"2026-09-19T06:55:15","slug":"scrum-psm-i-practice-test-questions-and-exam-dumps-part2-q21-40","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/scrum-psm-i-practice-test-questions-and-exam-dumps-part2-q21-40\/","title":{"rendered":"Scrum PSM I Practice Test Questions and Exam Dumps Part2 Q21-40"},"content":{"rendered":"

<\/h1>\n

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

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

Who orders items within the Product Backlog?<\/b><\/p>\n

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

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

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

    The Product Owner is accountable for effective Product Backlog management, which includes developing and 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. Ordering is important because it communicates which work is considered more valuable or appropriate to address sooner. Developers provide valuable technical and delivery insights, while stakeholders and users can contribute information. However, accountability for ordering remains with the Product Owner. The Product Owner may delegate actual work, but accountability cannot be transferred.<\/span><\/p>\n

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

    Which Scrum value emphasizes honoring commitments?<\/b><\/p>\n

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

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

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

      Commitment is one of the five Scrum values. The Scrum Team commits to achieving its goals and supporting one another as professionals. Commitment helps establish a shared sense of purpose around the Product Goal, Sprint Goal, and Definition of Done. Focus directs attention toward the work of the Sprint and its goals. Openness encourages transparency about work and challenges, while Courage supports difficult decisions and actions. Respect is another Scrum value that recognizes people as capable, independent individuals. Together, these values provide a foundation for effective Scrum behavior rather than functioning as procedural steps.<\/span><\/p>\n

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

      What does the Product Goal describe?<\/b><\/p>\n

        \n
      1. The exact tasks for tomorrow<\/span><\/li>\n
      2. The team’s meeting schedule<\/span><\/li>\n
      3. A future state of the product<\/span><\/li>\n
      4. Individual Developer responsibilities<\/span><\/li>\n<\/ol>\n

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

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

        The Product Goal describes a future state of the product that serves as a target for the Scrum Team’s planning. It provides a longer-term objective toward which the team works. The Product Backlog emerges around the Product Goal, and the team should fulfill or abandon one Product Goal before taking on the next. The Product Goal is different from the Sprint Goal, which describes the objective of a particular Sprint. It also differs from individual task assignments because Scrum Teams are self-managing. The Product Goal therefore gives product development a coherent direction beyond one Sprint.<\/span><\/p>\n

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

        Who can cancel a Sprint?<\/b><\/p>\n

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

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

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

          The Product Owner has the authority to cancel a Sprint when the Sprint Goal becomes obsolete. This authority follows the Product Owner’s accountability for maximizing product value and maintaining product direction. Cancellation is not an ordinary response to minor changes or difficulties during a Sprint. The Scrum Master may help the team understand the implications and facilitate appropriate communication, while Developers continue managing their work. Stakeholders can provide information that may influence product decisions but do not possess the authority to cancel the Sprint. A cancellation decision should therefore come from the Product Owner.<\/span><\/p>\n

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

          What does transparency enable in Scrum?<\/b><\/p>\n

            \n
          1. Meaningful inspection<\/span><\/li>\n
          2. Hidden decision-making<\/span><\/li>\n
          3. Delayed feedback<\/span><\/li>\n
          4. Independent reporting<\/span><\/li>\n<\/ol>\n

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

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

            Transparency makes important aspects of the process and resulting work visible to those performing the work and those receiving it. Without transparency, inspection becomes unreliable because people cannot accurately understand the current state of artifacts or progress. Scrum relies on transparency, inspection, and adaptation as connected elements of empiricism. When information is visible and understood, the Scrum Team and relevant stakeholders can make better-informed decisions. Transparency does not mean every piece of information must be exposed indiscriminately; rather, the important aspects of the process must be sufficiently visible to support meaningful inspection.<\/span><\/p>\n

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

            Which role owns the Product Backlog accountability?<\/b><\/p>\n

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

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

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

              The Product Owner is accountable for effective Product Backlog management. This includes ensuring that the backlog is transparent, visible, and understood, as well as ordering its items and communicating the Product Goal. Other people may assist with Product Backlog activities, but the accountability remains with the Product Owner. Developers contribute technical understanding and estimates, while the Scrum Master helps establish Scrum and improve effectiveness. An organizational manager does not automatically assume Product Backlog accountability merely because the team operates within that organization. Scrum clearly assigns this accountability to the Product Owner.<\/span><\/p>\n

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

              What is the purpose of inspecting the Increment?<\/b><\/p>\n

                \n
              1. To determine employee salaries<\/span><\/li>\n
              2. To assign future job titles<\/span><\/li>\n
              3. To support informed adaptation<\/span><\/li>\n
              4. To eliminate stakeholder participation<\/span><\/li>\n<\/ol>\n

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

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

                Inspection of the Increment provides information that can support informed adaptation. The Scrum Team and stakeholders can examine what has actually been produced and use that knowledge when considering what should happen next. This is especially important in complex environments where conditions and understanding can change. Inspection is not designed to determine compensation, establish organizational titles, or remove stakeholder involvement. Instead, it helps connect actual product results with future decisions. Scrum’s empirical approach depends on examining real outcomes rather than relying entirely on assumptions made before development begins.<\/span><\/p>\n

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

                What is an essential property of a Product Backlog?<\/b><\/p>\n

                  \n
                1. It remains unchanged after approval<\/span><\/li>\n
                2. It contains only technical defects<\/span><\/li>\n
                3. It belongs to the Developers<\/span><\/li>\n
                4. It is emergent<\/span><\/li>\n<\/ol>\n

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

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

                  The Product Backlog is emergent, meaning it evolves as more is learned about the product, its users, the market, technology, and other relevant conditions. It is not intended to remain permanently fixed after an initial approval. New information can lead to new items, changes in ordering, refinement of existing items, or removal of work that is no longer useful. The Product Backlog contains work needed to improve the product rather than only technical defects. Although Developers contribute valuable information, the Product Owner remains accountable for effective Product Backlog management.<\/span><\/p>\n

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

                  Who participates in the Sprint Review?<\/b><\/p>\n

                    \n
                  1. Scrum Team and relevant stakeholders<\/span><\/li>\n
                  2. Developers and auditors exclusively<\/span><\/li>\n
                  3. Product Owner and finance staff only<\/span><\/li>\n
                  4. Scrum Master and executives alone<\/span><\/li>\n<\/ol>\n

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

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

                    The Sprint Review is a working session involving the Scrum Team and key stakeholders. Together they inspect the outcome of the Sprint and discuss progress toward the Product Goal. The event provides an opportunity to consider changes in the environment and adapt the Product Backlog accordingly. It is not restricted to a particular department or management level. Relevant stakeholders can contribute important information about product expectations, market conditions, and emerging needs. The collaborative nature of the event helps ensure that future product decisions are based on the latest available evidence.<\/span><\/p>\n

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

                    Which artifact represents the current Sprint’s planned work?<\/b><\/p>\n

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

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

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

                      The Sprint Backlog represents the current Sprint’s planned work. It consists of the Sprint Goal, the Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment. The Sprint Backlog is owned by and managed by the Developers, and it evolves throughout the Sprint as more is learned. The Product Backlog covers broader product work, while the Product Goal describes a future state of the product. The Definition of Done describes the quality state required for completed work. These artifacts serve different purposes within Scrum.<\/span><\/p>\n

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

                      What happens when a Product Backlog item fails the Definition of Done?<\/b><\/p>\n

                        \n
                      1. It automatically becomes an Increment<\/span><\/li>\n
                      2. It is presented as completed<\/span><\/li>\n
                      3. It does not belong to the Increment<\/span><\/li>\n
                      4. It must be released immediately<\/span><\/li>\n<\/ol>\n

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

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

                        A Product Backlog item that does not satisfy the Definition of Done cannot be considered part of the Increment. The Definition of Done establishes the required quality state for completed work. Unfinished work may return to the Product Backlog for future consideration, depending on the circumstances and decisions of the Product Owner and Developers. It should not be represented as completed merely because development activity occurred. This rule preserves transparency about what has actually been delivered. Stakeholders can therefore inspect the Increment knowing that included work meets the agreed Definition of Done.<\/span><\/p>\n

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

                        Which Scrum value supports speaking openly about problems?<\/b><\/p>\n

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

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

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

                          Openness is a Scrum value that encourages the Scrum Team and stakeholders to be open about the work, challenges, and progress involved in product development. Complex work can expose uncertainty, mistakes, dependencies, and changing conditions. Concealing such information makes effective inspection and adaptation more difficult. Openness helps create the transparency necessary for empirical decision-making. Respect, Focus, Commitment, and Courage are also Scrum values, but each emphasizes a different behavioral quality. Openness specifically supports candid communication about work and difficulties, allowing the team to respond to reality rather than hidden assumptions.<\/span><\/p>\n

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

                          Who is accountable for establishing Scrum effectively?<\/b><\/p>\n

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

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

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

                            The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. This includes helping people understand Scrum theory and practice, coaching the Scrum Team, supporting the organization in adopting Scrum, and helping remove barriers to effective Scrum use. The Scrum Master does not function as a traditional project manager who assigns tasks or directs Developers. The Product Owner remains accountable for product value and Product Backlog management, while Developers create the Increment. The Scrum Master’s accountability centers on enabling Scrum’s effectiveness rather than controlling the team’s work.<\/span><\/p>\n

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

                            What does inspection require regarding Scrum artifacts?<\/b><\/p>\n

                              \n
                            1. They must remain confidential<\/span><\/li>\n
                            2. They should be examined frequently<\/span><\/li>\n
                            3. They require executive approval<\/span><\/li>\n
                            4. They can be ignored during adaptation<\/span><\/li>\n<\/ol>\n

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

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

                              Scrum artifacts should be inspected frequently enough to detect potentially undesirable variances or problems. Inspection works together with transparency and adaptation within Scrum’s empirical approach. If artifacts are rarely examined, important changes may remain unnoticed for too long, reducing the opportunity to respond effectively. Inspection does not mean that every person must continuously review every artifact or that executive approval is required. Instead, the relevant people inspect the appropriate artifacts at useful points. Frequent inspection helps Scrum Teams respond to what is actually happening rather than relying solely on earlier assumptions.<\/span><\/p>\n

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

                              How should Scrum Teams handle complex product uncertainty?<\/b><\/p>\n

                                \n
                              1. Use empiricism<\/span><\/li>\n
                              2. Avoid stakeholder feedback<\/span><\/li>\n
                              3. Freeze all requirements<\/span><\/li>\n
                              4. Depend entirely on prediction<\/span><\/li>\n<\/ol>\n

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

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

                                Scrum addresses complex work through empiricism, using transparency, inspection, and adaptation. In uncertain environments, it is difficult to predict every requirement, technical challenge, or market response accurately in advance. Scrum therefore encourages teams to create valuable outcomes, inspect what happens, and adapt based on what is learned. Freezing all requirements can prevent useful responses to new information, while avoiding stakeholder feedback removes an important source of learning. Prediction can still be useful, but Scrum does not depend exclusively on it. Empirical learning is central to managing complexity.<\/span><\/p>\n

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

                                Which accountability focuses directly on product value?<\/b><\/p>\n

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

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

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

                                  The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team’s work. This accountability includes effective Product Backlog management and maintaining a clear Product Goal. Developers are accountable for creating usable Increments that meet the Definition of Done, while the Scrum Master is accountable for establishing Scrum and supporting effectiveness. A project coordinator is not one of the three Scrum accountabilities. Although many people can influence product value through feedback and expertise, Scrum assigns direct accountability for maximizing product value to the Product Owner.<\/span><\/p>\n

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

                                  What should guide Developers during the Sprint?<\/b><\/p>\n

                                    \n
                                  1. Individual performance rankings<\/span><\/li>\n
                                  2. Sprint Goal<\/span><\/li>\n
                                  3. Annual department targets<\/span><\/li>\n
                                  4. Customer complaint volume<\/span><\/li>\n<\/ol>\n

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

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

                                    The Sprint Goal provides Developers with the primary objective for the Sprint. It gives the team flexibility regarding the exact work required while maintaining a shared purpose. Developers use the Sprint Goal when adapting their Sprint Backlog and deciding how to respond to newly discovered information. Other organizational or customer information may be relevant, but those sources do not replace the Sprint Goal. A strong Sprint Goal helps Developers maintain coherence when details change. It also provides a basis for inspection during the Daily Scrum and broader discussion during the Sprint Review.<\/span><\/p>\n

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

                                    Which statement best describes Scrum Team structure?<\/b><\/p>\n

                                      \n
                                    1. It has separate functional departments<\/span><\/li>\n
                                    2. It requires a project manager<\/span><\/li>\n
                                    3. It consists of self-managing professionals<\/span><\/li>\n
                                    4. It uses permanent command hierarchy<\/span><\/li>\n<\/ol>\n

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

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

                                      A Scrum Team is a cohesive group of professionals focused on one Product Goal. The team is self-managing, meaning its members internally decide who does what, when, and how. Scrum does not require a project manager or a permanent command hierarchy within the Scrum Team. Developers have the skills needed to create value, while the Product Owner and Scrum Master have their defined accountabilities. Self-management does not mean the team operates without accountability; instead, the team takes responsibility for organizing its work within Scrum’s framework and toward the Product Goal.<\/span><\/p>\n

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

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

                                        \n
                                      1. To create a shared objective<\/span><\/li>\n
                                      2. To guarantee every selected item finishes<\/span><\/li>\n
                                      3. To replace the Product Goal<\/span><\/li>\n
                                      4. To define employee evaluations<\/span><\/li>\n<\/ol>\n

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

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

                                        The Sprint Goal creates a shared objective for the Sprint and gives the team a coherent reason for undertaking the selected work. It provides flexibility because Developers can adjust the exact scope of work while preserving the Sprint’s purpose. The Sprint Goal does not guarantee that every selected Product Backlog item will be completed, nor does it replace the longer-term Product Goal. Employee evaluations are also outside its purpose. A useful Sprint Goal helps Developers make decisions when circumstances change and provides stakeholders with a clear understanding of the intended value of the Sprint.<\/span><\/p>\n

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

                                        Which Scrum value encourages difficult but necessary action?<\/b><\/p>\n

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

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

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

                                          Courage is one of the Scrum values and supports people in doing the right thing when facing difficult challenges. Scrum Teams may need to address uncomfortable problems, expose uncertainty, challenge assumptions, or make difficult product and technical decisions. Courage works together with the other Scrum values rather than replacing them. Respect supports people and their capabilities, Openness promotes transparency, Focus directs attention toward important goals, and Commitment reinforces dedication to objectives. Courage helps the team confront reality honestly and act constructively when difficult circumstances arise.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Scrum PSM I Exam Dumps and Practice Test Dumps. Question 21 Who orders items within the Product Backlog? Product Owner Developers Scrum Master Product users Correct Answer: 1 Explanation: The Product Owner is accountable for effective Product Backlog management, which includes developing and communicating the Product Goal, creating and clearly communicating Product Backlog […]<\/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\/16335"}],"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=16335"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16335\/revisions"}],"predecessor-version":[{"id":16414,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16335\/revisions\/16414"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}