{"id":16341,"date":"2026-09-19T06:52:46","date_gmt":"2026-09-19T06:52:46","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16341"},"modified":"2026-09-19T06:52:46","modified_gmt":"2026-09-19T06:52:46","slug":"scrum-psm-i-practice-test-questions-and-exam-dumps-part8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/scrum-psm-i-practice-test-questions-and-exam-dumps-part8-q141-160\/","title":{"rendered":"Scrum PSM I Practice Test Questions and Exam Dumps Part8 Q141-160"},"content":{"rendered":"

<\/h1>\n

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

 <\/p>\n

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

Who has authority to decide whether a Sprint should be cancelled?<\/b><\/p>\n

    \n
  1. Product Owner<\/span><\/li>\n
  2. Scrum Master<\/span><\/li>\n
  3. Developers<\/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. Cancellation is appropriate when the Sprint Goal becomes obsolete, meaning continuing the Sprint no longer makes sense from a product perspective. The Scrum Master can help the Product Owner and Scrum Team understand the implications of cancellation, while Developers and stakeholders may provide relevant information. However, they do not hold the accountability to cancel the Sprint. If a Sprint is cancelled, completed work is reviewed and potentially usable work may be accepted into the Increment if it satisfies the Definition of Done.<\/span><\/p>\n

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

    What does the Sprint Goal provide to Developers?<\/b><\/p>\n

      \n
    1. A detailed technical architecture<\/span><\/li>\n
    2. A single objective for the Sprint<\/span><\/li>\n
    3. A fixed list of future releases<\/span><\/li>\n
    4. A performance measurement system<\/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 and gives Developers flexibility regarding the exact work needed to achieve that objective. It creates coherence and focus rather than requiring every selected item to remain unchanged regardless of new information. Technical architecture is determined through the Developers’ technical work, while release planning and performance measurement are not the purpose of the Sprint Goal. During the Sprint, Developers can adapt the plan and negotiate scope with the Product Owner as long as the Sprint Goal remains intact.<\/span><\/p>\n

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

      Which principle makes Scrum especially useful for complex work?<\/b><\/p>\n

        \n
      1. Predicting every requirement beforehand<\/span><\/li>\n
      2. Eliminating all uncertainty<\/span><\/li>\n
      3. Empirical process control<\/span><\/li>\n
      4. Following a fixed sequential plan<\/span><\/li>\n<\/ol>\n

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

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

        Scrum is founded on empiricism, which means knowledge comes from experience and decisions are based on observation. Complex work often contains uncertainty that cannot be completely understood at the beginning. Instead of pretending that every requirement and outcome can be predicted accurately, Scrum creates frequent opportunities to inspect actual results and adapt. Empirical process control is supported by transparency, inspection, and adaptation. A fixed sequential plan or complete elimination of uncertainty is not realistic for complex product development. Scrum therefore uses short cycles and frequent feedback to improve decisions as knowledge increases.<\/span><\/p>\n

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

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

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

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

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

          A Sprint is a fixed-length event of one month or less. Keeping the Sprint within this limit creates a regular rhythm for inspection and adaptation. A team may choose a shorter Sprint depending on its product and environment, but it cannot define a Sprint longer than one month. The fixed maximum also helps limit risk because stakeholders and the Scrum Team have frequent opportunities to inspect results. Sprint length is not extended simply because the team expects more work to be difficult or because additional requirements appear during development.<\/span><\/p>\n

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

          What does the Scrum Master support when impediments affect progress?<\/b><\/p>\n

            \n
          1. Removal of barriers<\/span><\/li>\n
          2. Assignment of individual salaries<\/span><\/li>\n
          3. Selection of customer contracts<\/span><\/li>\n
          4. Ownership of source code<\/span><\/li>\n<\/ol>\n

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

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

            The Scrum Master helps cause the removal of impediments to the Scrum Team’s progress. An impediment can be anything that prevents the team from making effective progress toward its goals. Depending on the situation, the Scrum Master may coach the team, facilitate organizational conversations, or help people understand how a barrier can be addressed. This does not mean the Scrum Master personally performs every removal activity. Salary decisions, customer contracts, and source-code ownership are outside the Scrum Master’s Scrum accountability. The focus is enabling a more effective environment for Scrum.<\/span><\/p>\n

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

            Which artifact contains the commitment toward the Product Goal?<\/b><\/p>\n

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

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

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

              The Product Goal is the commitment associated with the Product Backlog. It describes a future state of the product that serves as a target for the Scrum Team. The Sprint Backlog has the Sprint Goal as its commitment, while the Increment has the Definition of Done as its quality commitment. Understanding these relationships helps distinguish the purposes of Scrum’s artifacts and commitments. The Product Backlog evolves toward achieving the Product Goal, while individual Sprints contribute increments of value that progressively move the product toward that desired future state.<\/span><\/p>\n

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

              What is the Scrum Master’s role regarding Scrum adoption?<\/b><\/p>\n

                \n
              1. Helping people understand Scrum<\/span><\/li>\n
              2. Assigning every backlog item<\/span><\/li>\n
              3. Approving all technical solutions<\/span><\/li>\n
              4. Writing every Sprint plan<\/span><\/li>\n<\/ol>\n

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

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

                The Scrum Master helps people within the organization understand Scrum and its empirical approach. This includes coaching the Scrum Team and stakeholders, helping establish Scrum, and supporting improvements in how Scrum is understood and practiced. The Scrum Master does not become the Product Owner or take over Developers’ responsibilities. Assigning every backlog item belongs to neither the Scrum Master nor the Scrum framework. Similarly, Developers create their own actionable plan and determine technical approaches. The Scrum Master’s influence comes through coaching, facilitation, teaching, and helping remove barriers to effective Scrum.<\/span><\/p>\n

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

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

                  \n
                1. Product pricing consistency<\/span><\/li>\n
                2. Employee attendance records<\/span><\/li>\n
                3. A shared quality standard<\/span><\/li>\n
                4. Marketing campaign schedules<\/span><\/li>\n<\/ol>\n

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

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

                  The Definition of Done establishes a shared understanding of the quality state required for work to be considered part of the Increment. It protects transparency by ensuring that everyone has the same baseline for completed work. Without a common Definition of Done, different people might interpret \u201cfinished\u201d differently, making inspection unreliable. Pricing, attendance, and marketing schedules may matter to an organization but are not the purpose of this Scrum artifact. The Definition of Done therefore provides a consistent quality threshold that supports trustworthy product inspection and decision-making.<\/span><\/p>\n

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

                  When is a Product Backlog item sufficiently refined for selection?<\/b><\/p>\n

                    \n
                  1. When it meets the team’s current understanding needs<\/span><\/li>\n
                  2. When every future detail is permanently known<\/span><\/li>\n
                  3. When stakeholders sign a legal approval<\/span><\/li>\n
                  4. When technical uncertainty has disappeared completely<\/span><\/li>\n<\/ol>\n

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

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

                    A Product Backlog item does not need every possible detail before it can be considered for selection. It should be sufficiently understood for the Scrum Team to make a useful decision based on its current knowledge. Refinement is an ongoing activity, and details can continue changing as more is learned. Requiring complete certainty would be impractical in complex product development. Technical uncertainty can remain even when an item is sufficiently understood for planning. The goal is useful clarity at the appropriate time, not exhaustive prediction of every future detail.<\/span><\/p>\n

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

                    What should happen when Sprint scope becomes clearer during development?<\/b><\/p>\n

                      \n
                    1. Developers must ignore the new information<\/span><\/li>\n
                    2. The Sprint Backlog may be adapted<\/span><\/li>\n
                    3. The Sprint must automatically restart<\/span><\/li>\n
                    4. The Product Goal must be replaced<\/span><\/li>\n<\/ol>\n

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

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

                      As Developers gain a better understanding of the work, they can adapt the Sprint Backlog. The Sprint Backlog is expected to evolve during the Sprint because the initial plan cannot anticipate every discovery. Developers remain focused on the Sprint Goal while updating their plan to reflect current knowledge. New information does not automatically require restarting the Sprint or replacing the Product Goal. The Product Owner and Developers can also collaborate on scope adjustments when necessary, provided the Sprint Goal remains protected. This flexibility supports empirical development without abandoning the Sprint’s objective.<\/span><\/p>\n

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

                      Which Scrum value emphasizes staying dedicated to agreed objectives?<\/b><\/p>\n

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

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

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

                        Commitment is one of Scrum’s five values and relates to the Scrum Team’s dedication to achieving its goals. Scrum Teams commit to goals such as the Product Goal, Sprint Goal, and quality represented by the Definition of Done. Focus, Openness, Respect, and Courage are also essential values, but each emphasizes a different behavior. Commitment does not mean blindly following an outdated plan. Instead, it means remaining dedicated to the goal while adapting the details of the work when new information becomes available. This distinction is important in complex product development.<\/span><\/p>\n

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

                        What does inspection require before adaptation can be meaningful?<\/b><\/p>\n

                          \n
                        1. Complete elimination of disagreement<\/span><\/li>\n
                        2. A transparent basis for observation<\/span><\/li>\n
                        3. Approval from every stakeholder<\/span><\/li>\n
                        4. A predetermined final solution<\/span><\/li>\n<\/ol>\n

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

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

                          Meaningful inspection depends on transparency. People need a sufficiently clear and shared view of the artifact, process, or outcome before they can identify meaningful differences and decide whether adaptation is necessary. Scrum therefore emphasizes transparency as one of its three pillars of empiricism. Complete agreement, unanimous stakeholder approval, or a predetermined solution is not required for inspection. In fact, inspection may reveal disagreement or unexpected information. The important point is that relevant information must be visible enough for people to evaluate the current situation and make an informed adaptation.<\/span><\/p>\n

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

                          Which event begins immediately after the previous Sprint ends?<\/b><\/p>\n

                            \n
                          1. Sprint Review<\/span><\/li>\n
                          2. Sprint Retrospective<\/span><\/li>\n
                          3. The next Sprint<\/span><\/li>\n
                          4. Product Backlog Refinement<\/span><\/li>\n<\/ol>\n

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

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

                            A new Sprint starts immediately after the conclusion of the previous Sprint. Scrum does not define a gap between Sprints for administrative preparation. Sprint Planning occurs within the new Sprint and establishes its objective and initial plan. The Sprint Review and Sprint Retrospective are events that occur during the current Sprint before it concludes. Product Backlog refinement is an ongoing activity rather than a formal event that separates one Sprint from another. Continuous Sprint cycles create a regular cadence for inspection, adaptation, and delivery of usable product increments.<\/span><\/p>\n

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

                            Who determines how selected work will be transformed into an Increment?<\/b><\/p>\n

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

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

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

                              Developers determine how selected Product Backlog items can be transformed into a usable Increment. They possess the professional skills needed to create the product and are accountable for managing their own work. The Product Owner provides product direction and value-related context, but does not prescribe every technical method. The Scrum Master supports Scrum effectiveness rather than directing implementation. An executive sponsor may influence organizational priorities but does not control the Developers’ technical approach. This separation supports self-management and allows technical decisions to be made by the people performing the work.<\/span><\/p>\n

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

                              What does the Sprint Review inspect besides the Increment?<\/b><\/p>\n

                                \n
                              1. Only individual Developer performance<\/span><\/li>\n
                              2. The broader environment and future options<\/span><\/li>\n
                              3. Employee compensation policies<\/span><\/li>\n
                              4. Internal payroll procedures<\/span><\/li>\n<\/ol>\n

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

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

                                The Sprint Review examines the Sprint outcome and considers changes in the broader environment that may influence what should happen next. The Scrum Team and stakeholders collaborate about future adaptations based on what they have learned. This can include changes in markets, customer needs, technology, regulations, or other relevant conditions. The event is not designed to evaluate individual employee performance or review payroll matters. Its focus remains the product and the decisions needed to maximize future value. This makes the Sprint Review a collaborative working session rather than merely a demonstration.<\/span><\/p>\n

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

                                Which condition allows work to contribute to the Increment?<\/b><\/p>\n

                                  \n
                                1. It has been discussed by stakeholders<\/span><\/li>\n
                                2. It appears on an old roadmap<\/span><\/li>\n
                                3. It satisfies the Definition of Done<\/span><\/li>\n
                                4. It has an estimated business cost<\/span><\/li>\n<\/ol>\n

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

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

                                  Work can be considered part of the Increment when it satisfies the Definition of Done. The Definition of Done establishes the quality criteria that must be met for completed work. Merely discussing an item, placing it on a roadmap, or assigning it an estimated cost does not make it part of a usable Increment. This distinction maintains transparency about the actual state of the product. If work remains unfinished according to the Definition of Done, it cannot be presented as completed product functionality simply because substantial effort has already been invested.<\/span><\/p>\n

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

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

                                    \n
                                  1. Members decide internally who does what, when, and how<\/span><\/li>\n
                                  2. The Scrum Master assigns every responsibility<\/span><\/li>\n
                                  3. Stakeholders control daily implementation<\/span><\/li>\n
                                  4. The Product Owner distributes technical tasks<\/span><\/li>\n<\/ol>\n

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

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

                                    A self-managing Scrum Team decides internally who does what, when, and how. This does not mean individuals work without accountability or coordination. Instead, the team collectively determines the best way to organize its work while pursuing the Sprint Goal and creating a usable Increment. The Scrum Master does not function as a task manager, and the Product Owner does not distribute technical assignments. Stakeholders can provide valuable feedback and information, but they do not control the team’s daily implementation. Self-management supports ownership, adaptability, and effective use of the team’s combined expertise.<\/span><\/p>\n

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

                                    What should stakeholders primarily contribute during product inspection?<\/b><\/p>\n

                                      \n
                                    1. Technical task assignments<\/span><\/li>\n
                                    2. Useful feedback and relevant information<\/span><\/li>\n
                                    3. Sprint Backlog ownership<\/span><\/li>\n
                                    4. Scrum Master responsibilities<\/span><\/li>\n<\/ol>\n

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

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

                                      Stakeholders can provide valuable feedback, domain knowledge, market information, and other relevant perspectives during product inspection. Their input helps the Scrum Team understand whether the product is addressing meaningful needs and what changes might be appropriate next. Stakeholders do not own the Sprint Backlog, assign Developers’ technical work, or assume the Scrum Master’s accountability. Their participation is particularly useful during the Sprint Review, where the Scrum Team and stakeholders collaborate about the product outcome and future direction. Their information can influence Product Backlog decisions through the Product Owner.<\/span><\/p>\n

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

                                      Which Scrum artifact represents the current plan for achieving the Sprint Goal?<\/b><\/p>\n

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

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

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

                                        The Sprint Backlog represents the current plan for achieving the Sprint Goal. It contains the Sprint Goal, selected Product Backlog items, and an actionable plan for delivering the Increment. Because Developers learn throughout the Sprint, the plan can change as understanding improves. The Product Backlog contains broader product work, the Product Goal describes a future state, and the Definition of Done establishes the quality standard. The Sprint Backlog therefore provides a current view of how Developers intend to accomplish the Sprint’s objective while allowing adaptation when circumstances change.<\/span><\/p>\n

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

                                        Why are short Sprints useful in complex product development?<\/b><\/p>\n

                                          \n
                                        1. They eliminate the need for stakeholders<\/span><\/li>\n
                                        2. They guarantee successful releases<\/span><\/li>\n
                                        3. They reduce opportunities for learning<\/span><\/li>\n
                                        4. They create frequent inspection and adaptation points<\/span><\/li>\n<\/ol>\n

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

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

                                          Short Sprints create frequent opportunities to inspect product results, progress, assumptions, and the surrounding environment. These regular inspection points allow the Scrum Team and stakeholders to learn sooner and adapt before incorrect assumptions become more costly. Short Sprints do not guarantee successful releases or eliminate the need for stakeholder involvement. They also do not reduce learning; their purpose is to make learning and adaptation more frequent. The fixed Sprint cadence helps manage complexity by limiting the period between opportunities to evaluate actual results and decide what should happen next.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Scrum PSM I Exam Dumps and Practice Test Dumps.   Question 141 Who has authority to decide whether a Sprint should be cancelled? Product Owner Scrum Master Developers Stakeholders Correct Answer: 1 Explanation: Only the Product Owner has the authority to cancel a Sprint. Cancellation is appropriate when the Sprint Goal becomes obsolete, […]<\/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\/16341"}],"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=16341"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16341\/revisions"}],"predecessor-version":[{"id":16409,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16341\/revisions\/16409"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}