Our pass rate is high to 98.9% and the similarity percentage between our PSM-I study guide and real exam is 90% based on our seven-year educating experience. Do you want achievements in the Scrum PSM-I exam in just one try? I am currently studying for the Scrum PSM-I exam. Latest Scrum PSM-I Test exam practice questions and answers, Try Scrum PSM-I Brain Dumps First.
Also have PSM-I free dumps questions for you:
NEW QUESTION 1
What enhances the transparency of an increment?
- A. Doing all work needed to meet the definition of “Done”
- B. Reporting Sprint progress to the stakeholders daily
- C. Keeping track of and estimating all undone work to be completed in a separate Sprint.
- D. Updating Sprint tasks properly in the electronic tracking tool.
Answer: A
Explanation:
he correct answer is A, because doing all work needed to meet the definition of “Done” enhances the transparency of an increment. The Scrum Guide states that “when a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” Therefore, by meeting the definition of “Done”, an increment becomes transparent to all stakeholders and ready for release.
NEW QUESTION 2
The length of a Sprint should be:
- A. Short enough to keep the business risk acceptable to the Product Owner.
- B. Short enough to be able to synchronize the development work with other business events.
- C. No more than one calendar month.
- D. All of these answers are correct.
Answer: D
Explanation:
According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The length of a Sprint should be short enough to keep the business risk acceptable to the Product Owner, short enough to be able to synchronize the development work with other business events, and no more than one calendar month.
References: Scrum Guide
NEW QUESTION 3
Who has the final say on the order of the Product Backlog?
- A. The Development Team.
- B. The Product Owner.
- C. The Scrum Master.
- D. The Stakeholders.
- E. The CEO.
Answer: B
Explanation:
According to the Scrum Guide, the Product Owner has the final say on the order of the Product Backlog, as he or she is responsible for maximizing the value of the product and the work of the Development Team. The other roles do not have this authority, although they may provide input and suggestions to the Product Owner.
NEW QUESTION 4
During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate? (Choose the best answer.)
- A. The Scrum Team may add items to the Sprint Backlog for the next Sprint.
- B. The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog.
- C. The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly.
- D. The Scrum Master selects the most important process improvement and places it in the Sprint Backlog
Answer: A
Explanation:
During the Sprint Retrospective, the Scrum Team may add items to the Sprint Backlog for the next Sprint, as stated in [5]: “The purpose of each Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team plans ways to implement improvements identified during this meeting into its way of working. By doing this it reinforces empiricism throughout its work. Improvements may be implemented at any time during a Sprint or they may be planned for subsequent Sprints.”
NEW QUESTION 5
What are two ways that regulatory compliance issues are dealt with in Scrum? (choose the best two answers)
- A. They are addressed by a separate team who is responsible for compliance issues.
- B. They are addressed along with functional development of the product.
- C. They are discussed, determined, and documented before the actual feature development Sprints.
- D. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
Answer: BD
Explanation:
The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum’s values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.
A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.
C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.
NEW QUESTION 6
The CEO asks the Development Team to add a “very important” item to a Sprint that is in progress. What should the Development Team do?
- A. Add the item to the current Sprint and drop an item of equal size.
- B. Add the item to the current Sprint without any adjustments.
- C. Inform the Product Owner so he/she can work with the CEO.
- D. Add the item to the next Sprint.
Answer: C
Explanation:
The correct answer is C, because the Development Team should inform the Product Owner so he/she can work with the CEO. The Scrum Guide states that “only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.” Therefore, if the CEO wants to add a “very important” item to a Sprint that is in progress, he or she should communicate with the Product Owner, who can then decide whether to cancel or continue the current Sprint.
NEW QUESTION 7
At the end of a Sprint Product Backlog item worked on during the Sprint does not meet the definition of “Done”. What two things should happen with the undone Product Backlog item? (Choose two.)
- A. If the stakeholders agree, the Product Owner can accept it and release it to the users.
- B. Put it on the Product Backlog for the Product Owner to decide what to do with it.
- C. Review the item, add the “Done” part of the estimate to the velocity and create a Story for the remaining work.
- D. Do not include the item in the Increment this Sprint.
Answer: BD
Explanation:
According to the Scrum Guide1, the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, if a Product Backlog item worked on during the Sprint does not meet the definition of “Done”, two things that should happen with the undone Product Backlog item are:
Put it on the Product Backlog for the Product Owner to decide what to do with it, as they are accountable for effective Product Backlog management and ordering. Do not include the item in the Increment this Sprint, as it does not meet the quality standards and may compromise value.
The other options are not appropriate, as they may compromise transparency, inspection, or adaptation. References: Scrum Guide
NEW QUESTION 8
When does a Developer become accountable for an item in the sprint Backlog? (choose the best answer)
- A. During the Daily Scrum
- B. Never am Developers on the Scrum Team share accountability tor items in the
- C. As soon as a Developer on the Scrum Team can accommodate more work
- D. At Sprint Planning when all of the Sprint Backlog items are split evenly across the Developers
Answer: B
Explanation:
A Developer becomes accountable for an item in the Sprint Backlog never as Developers on the Scrum Team share accountability for items in the Sprint Backlog, as stated in the Scrum Guide: “The Developers can select whatever items they want as long as they feel they can complete the work by the end of the Sprint. The Scrum Team is responsible for all estimates. The Product Owner may influence the Developers by helping them understand and select trade-offs, but the people who will perform the work make the final estimate.”
NEW QUESTION 9
The Product Backlog is ordered by:
- A. The Product Owner with the most valuable items placed at the top.
- B. Risk, where safer items are at the top, and riskier items are at the bottom.
- C. Items are randomly arranged.
- D. Size, where small items ale at the top and large items are at the bottom.
Answer: A
Explanation:
The Product Backlog is ordered by the Product Owner with the most valuable items placed at the top, as stated in [6]: “The Product Owner is responsible for ordering items on their product backlog based on their value to customers and users. Value can be measured by various factors, such as business value, customer satisfaction, risk reduction, learning opportunities, etc. The most valuable items are placed at the top of the product backlog so that they can be delivered sooner by the development team.”
NEW QUESTION 10
For which is the Scrum Master responsible?
- A. Managing the performance of the Scrum Team.
- B. The meetings and the objectives that a Scrum Team sets for itself.
- C. The Scrum framework being adopted and used properly.
- D. Keeping track of resource allocation.
Answer: C
Explanation:
According to the Scrum Guide1, the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
NEW QUESTION 11
When should a Sprint Goal be created?
- A. It should have been created in the previous Sprint during Product Backlog refinement.
- B. It must be established before Sprint Planning in order to begin planning.
- C. A Sprint Goal is not mandatory in Scrum.
- D. At any time during the Sprint.
- E. During Sprint Planning.
Answer: E
Explanation:
According to the Scrum Guide1, one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they create a Sprint Goal every Sprint. The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is created during the Sprint Planning event.
References: Scrum Guide
NEW QUESTION 12
A new developer is having continuing conflicts with existing Development Team members and creating the hostile environment. If necessary, who is responsible for removing the team member?
- A. The hiring manager is responsible, because he/she hired the developer.
- B. The Scrum Manager is responsible, because he/she removes Impediments.
- C. The Development Team is responsible, and may need help from the Scrum Master.
- D. The Product Owner is responsible, because he/she controls the return on investment (ROI).
Answer: C
Explanation:
The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product
Backlog into Increments of potentially releasable functionality.” Therefore, the Development Team should
manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.
NEW QUESTION 13
Which topics should be discussed in the Sprint Review?
- A. The Scrum process, and how it was used during the Sprint.
- B. Coding and engineering practices.
- C. Sprint results.
- D. All of the above.
Answer: D
Explanation:
All of the above topics should be discussed in the Sprint Review, as stated in [4]: "The purpose of this meeting is to inspect what was delivered during this sprint and adapt what we want to deliver next. This means we will discuss three things:
What did we do this sprint? 
How did we do it? What do we want to do next?"
NEW QUESTION 14
The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.
- A. True
- B. False
Answer: B
Explanation:
The correct answer is B, because the Product Owner does not make sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Scrum Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team is responsible for choosing the scope of work for a Sprint.
NEW QUESTION 15
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?
- A. The Scrum Team.
- B. The Product Owner.
- C. The Developers.
- D. The Project Manager.
Answer: C
NEW QUESTION 16
What does it mean to say that an event has a time-box?
- A. The event must happen at a set time.
- B. The event must happen by a given time.
- C. The event must take at least a minimum amount of time.
- D. The event can take no more than a maximum amount of time.
Answer: D
Explanation:
According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
References: Scrum Guide
NEW QUESTION 17
Which two of the following are true about the Scrum Master role? (Choose two.)
- A. At the Sprint Review, the Scrum Master identifies what has been “done” and what has not been “done”.
- B. The Scrum Master teaches the Development Team to keep the Scrum meetings to their time-box.
- C. The Scrum Master helps those outside the team interact with the Scrum Team.
- D. The Scrum Master assigns tasks to Development Team members when they need work.
- E. The Scrum Master is responsible for updating the Sprint Burndown.
Answer: BC
Explanation:
According to the Scrum Guide1, the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master serves the Developers in several ways, including: Coaching them in self-management and cross-functionality; Helping them to create high-value products; Removing impediments to their progress; Facilitating Scrum events as requested or needed; and, Coaching them in organizational environments in which Scrum is not yet fully adopted and understood. The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Goal definition and Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; Helping establish empirical product planning for a complex environment; and, Facilitating stakeholder collaboration as requested or needed.
The Scrum Master serves the organization in several ways, including: Leading, training, and coaching the organization in its Scrum adoption; Planning and advising Scrum implementations within the organization; Helping employees and stakeholders understand and enact an empirical approach for complex work; and, Removing barriers between stakeholders and Scrum Teams.
Therefore, two things that are true about the Scrum Master role are: The Scrum Master teaches the Development Team to keep the Scrum meetings to their time-box, as they help everyone understand Scrum theory and practice. The Scrum Master helps those outside the team interact with the Scrum Team, as they serve both the Product Owner and the organization.
The other options are not true about the Scrum Master role, as they imply that they have authority or responsibility over things that are not within their accountability.
References: Scrum Guide
NEW QUESTION 18
When can a Development Team cancel a Sprint?
- A. It can’
- B. Only Product Owners can cancel Sprints.
- C. When functional expectations are not well understood.
- D. When the Product Owner is absent too often.
- E. When the selected Product Backlog items for the Sprint become unachievable.
- F. When a technical dependency cannot be resolved.
Answer: A
Explanation:
The correct answer is A, because the Scrum Guide states that “a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.” Therefore, a Development Team cannot cancel a Sprint by itself.
NEW QUESTION 19
Why does a Development Team need a Sprint Goal?
- A. A Sprint Goal only gives purpose to Sprint 0.
- B. Sprint Goals are not valuabl
- C. Everything is known from the Product Backlog.
- D. The Development Team is more focused with a common yet specific goal.
- E. A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.
Answer: C
Explanation:
According to the Scrum Guide, a Development Team needs a Sprint Goal because it provides guidance and focus for building an Increment that delivers value. The other options are not valid reasons for having a Sprint Goal, as they are either incorrect (such as giving purpose only to Sprint 0 or ensuring implementation of all Product Backlog items) or irrelevant (such as knowing everything from the Product Backlog).
NEW QUESTION 20
How do you know that a Scrum Team is cross-functional? (Choose the best answer.)
- A. Scrum Team has all the skills to create an increment by the end of every Sprint.
- B. A few of the Development Team members pair program and do Test Driven Development.
- C. There are no conflicts within the Scrum Team.
- D. Every member of the Scrum Team is able to perform every task.
Answer: A
NEW QUESTION 21
......
P.S. Easily pass PSM-I Exam with 197 Q&As Dumpscollection.com Dumps & pdf Version, Welcome to Download the Newest Dumpscollection.com PSM-I Dumps: https://www.dumpscollection.net/dumps/PSM-I/ (197 New Questions)
