All About Real PSM-I Real Exam

NEW QUESTION 1
Who creates the Definition of Done? (choose the best answer)

• A. The Scrum Master
• B. The Product Owner
• C. The scrum Team
• D. The Developers

Answer: C

Explanation:
The correct answer is C. The Scrum Team creates the Definition of Done. According to the Scrum Guide1, “The Developers are required to conform to the Definition of Done, which is defined and evolves with the Scrum Team.” The Definition of Done is a commitment by the Developers for the Increment, but it is also a shared understanding within the whole Scrum Team, including the Product Owner and the Scrum Master2.
The Scrum Team collaborates to create and update the Definition of Done as needed, based on the product and organizational standards3. The Definition of Done is not imposed by any external authority or individual.

NEW QUESTION 2
When Goes a Developer become accountable for the value 01 a Product BacKlog item selected for the Sprint' (choose the best answer)

• A. Never The entire Scrum Team is accountable for creating value every Sprint.
• B. At the Sprint Planning Evented
• C. Whenever a team member can accommodate more worn.
• D. During the Daily scrum

Answer: B

Explanation:
According to the Scrum Guide, a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint at the Sprint Planning event. This is when the Developers select items from the Product Backlog that they can commit to complete within a Sprint. The Developers are then responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they either imply that Developers are not accountable for value (such as never or whenever), or that they become accountable at a different time (such as during the Daily Scrum).

NEW QUESTION 3
Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.
A good way to continue is:

• A. The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible.The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
• B. Add enough people to the Development Team for the deadline to be made.
• C. The opportunity to inspect and adapt is los
• D. Opaqueness has replaced transparenc
• E. Predictability has dropped below zer
• F. The produced software is not usabl
• G. As the rules of Scrum have not been respected, it is the Scrum Master’s duty to assess whether repair is possible, or a restart with a more reliable tea
• H. If not, the Scrum Master should cancel the project.
• I. The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.

Answer: A

Explanation:
According to the Scrum Guide1, each Increment is additive to all prior Increments and thoroughly verified,
ensuring that all Increments work together. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, a good way to continue is for the Development Team to make sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
References: Scrum Guide

NEW QUESTION 4
Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum?

• A. Lead the discussions of the Development Team.
• B. Make sure that all 3 questions have been answered by each member of the team.
• C. Keep track of whether each team member has a chance to speak.
• D. Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.
• E. All of the above.

Answer: D

Explanation:
The correct answer is D, because one of the services that a Scrum Master can provide in regard to the Daily Scrum is to teach the Development Team to keep the Daily Scrum within the 15 minute time-box. The Scrum Guide states that “the Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.”

NEW QUESTION 5
The time-box for a Daily Scrum?

• A. Two minutes per person.
• B. 15 minutes.
• C. 15 minutes for a 4 week sprin
• D. For shorter Sprints it is usually shorter.
• E. 4 hours.
• F. The same time of day every day.

Answer: B

Explanation:
The correct answer is B, because the time-box for a Daily Scrum is 15 minutes. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.”

NEW QUESTION 6
What is a Development Team responsible for? (Choose two.)

• A. Resolving internal team conflicts.
• B. Reporting productivity.
• C. Selecting the Product Owner.
• D. Organizing the work required to meet the Sprint Goal.

Answer: AD

Explanation:
The correct answers are A and D, because a Development Team is responsible for resolving internal team conflicts and organizing the work required to meet the Sprint Goal. 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, a Development Team should manage its own work and resolve its own issues.

NEW QUESTION 7
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 8
What are two responsibilities of testers in a Development Team? (Choose two.)

• A. Verifying the work of programmers.
• B. Everyone in the Development Team is responsible for quality.
• C. Tracking quality metrics.
• D. Finding bugs.
• E. Scrum has no “tester” role.

Answer: BE

Explanation:
The correct answers are B and E, because Scrum has no “tester” role and everyone in the Development Team is responsible for quality. The Scrum Guide states that “the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of ‘Done’ product at the end of each Sprint.
Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.”

NEW QUESTION 9
Which statement best describes the Sprint Review?

• A. It is used to congratulate the Development Team if it did what it forecast, or to punish the Development Team if it failed to meet its forecast.
• B. It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
• C. It is a mechanism to control the Development Team’s activities during a Sprint.
• D. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

Answer: D

Explanation:
The correct answer is D, because this statement best describes the Sprint Review. The Scrum Guide states that “a Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint.” Therefore, the Sprint Review is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

NEW QUESTION 10
Who owns the Sprint Backlog?

• A. The Scrum Team.
• B. The Product Owner.
• C. The Scrum Master.
• D. The Development Team.

Answer: D

Explanation:
Sprint Backlog is owned by the Development Team. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. … The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.”

NEW QUESTION 11
A Product Owner wants advice from the Scrum Master about estimating work in Scrum. Which of these is the guideline that a Scrum Master should give? (Choose the best answer.)

• A. Product Backlog items must be estimated in story points.
• B. Estimates are made by the people doing the work.
• C. Estimates must be in relative units.
• D. Scrum forbids estimating.
• E. Estimates are made by the Product Owner, but are best checked with the Development Team.

Answer: B

Explanation:
According to the Scrum Guide, estimates are made by the people doing the work, which is the Development Team. The Development Team is responsible for all estimates in the Product Backlog and the Sprint Backlog. The other options are not valid guidelines for estimating work in Scrum, as they are either too prescriptive (such as requiring story points or relative units), incorrect (such as forbidding estimating or having the Product Owner make estimates), or unnecessary (such as checking estimates with the Development Team).

NEW QUESTION 12
Which approach is best for Scrum Teams in order to produce valuable Increments? (Choose the best answer.)

• A. Each Developer works on the component where they feel that they can contribute.
• B. Each Scrum Team is accountable for developing functionality from beginning to end.
• C. Each Scrum Team works on an independent set of components.
• D. Each Scrum Member works only as an independent layer of the system.

Answer: A

Explanation:
According to the Scrum Guide, the best approach for Scrum Teams in order to produce valuable Increments is to have each Developer work on the component where they feel that they can contribute. This means that the Developers can self-organize and collaborate effectively to deliver a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid approaches, as they either imply that the Developers work in silos or rely on external people (such as developing functionality from beginning to end, working on an independent set of components, or working only as an independent layer of the system).

NEW QUESTION 13
Which two things should the Development Team do during the first Sprint? (Choose two.)

• A. Make up a plan for the rest of the project.
• B. Analyze, describe, and document the requirements for the subsequent Sprints.
• C. Develop at least one piece of functionality.
• D. Analyze, design, and describe the complete architecture and infrastructure.
• E. Create an increment of potentially releasable software.

Answer: CE

Explanation:
According to the Scrum Guide1, each Sprint is a project with no more than a one-month horizon. The Sprint Goal gives guidance to why the Scrum Team is building an Increment. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Therefore, in the first Sprint, as in any other Sprint, the Development Team should develop at least one piece of functionality and create an increment of potentially releasable software. The other options are not consistent with Scrum values and principles.
References: Scrum Guide

NEW QUESTION 14
A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take?

• A. Allow the Development Team to self-manage and determine for itself what to do.
• B. Set up the meeting and tell the Development Team that is how it will be done.
• C. Ask the Development Team members to alternate who is responsible for meeting setup.
• D. Inform management and ask them to solve it.

Answer: A

Explanation:
According to the Scrum Guide1, only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, the Scrum Master should allow the Development Team to self-manage and determine for itself what to do regarding the logistical challenges of meeting in different locations.
References: Scrum Guide

NEW QUESTION 15
How should a Development Team deal with non-functional requirements?

• A. Ensure every Increment meets them.
• B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
• C. Handle them during the Integration Sprint preceding the Release Sprint.
• D. Assign them to the lead developers on the team.

Answer: A

Explanation:
The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal description of the state of the Increment when it meets the quality measures required for the product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and ensure every Increment meets them.

NEW QUESTION 16
What are two ways that architecture and infrastructure are handled in Scrum? (Choose two.)

• A. They are discussed, determined, and documented before the actual feature development Sprints.
• B. They are implemented along with functional development of the product.
• C. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
• D. They are built by a separate team through the creation of an architectural runway.

Answer: BC

Explanation:
Architecture and infrastructure are handled in Scrum by implementing them along with functional development of the product, and by adding them to the Product Backlog and addressing them in early Sprints, while always requiring at least some business functionality, no matter how small, as stated in [2]: “Scrum does not distinguish between developing functionality or architecture. They are developed together, as they are both important and support each other. Architecture is not a separate phase; it is part of the product development. Architecture is added to the Product Backlog as any other feature or functionality.”

NEW QUESTION 17
When multiple Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint? (choose the best answer)

• A. Yes, but only for Scrum Teams whose work has dependencies.
• B. No, that is tar too nard and must be done in a hardening Sprint
• C. No, each Scrum Team stands alone.
• D. Yes, in order to accurately inspect what is done.

Answer: D

Explanation:
According to the Scrum Guide, when multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint, in order to accurately inspect what is done and ensure that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid, as they imply that integration can be skipped, delayed, or done only for some teams, which is not consistent with Scrum values and principles.

NEW QUESTION 18
You are the Scrum Master for four Scrum Teams working from the same Product Backlog. Several of the developers come to you complaining that work identified for the upcoming two Sprints will require full-time commitment from a technical specialist who is external to the teams. What are two key concerns for the Scrum Master to take into account in this situation? (Choose two.)

• A. The desire to maintain a stable velocity.
• B. The benefit of Development Teams figuring out a solution for themselves.
• C. The need to have enough work to keep all Development Team members busy.
• D. The ability of the Development Teams to produce integrated Increments.

Answer: BD

Explanation:
The Scrum Master should be concerned about the ability of the Development Teams to produce integrated Increments, as this is one of the goals of Scrum. The Scrum Master should also encourage the Development Teams to figure out a solution for themselves, as this fosters self-management and collaboration. The other options are not relevant or important for the Scrum Master in this situation.

NEW QUESTION 19
A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what “Done” means. (Choose two.)

• A. All work the Development Team is willing to do.
• B. Ready for integration.
• C. No work left from the definition of “Done”.
• D. Whatever the Product Owner defines as quality.
• E. All work to create software that is ready to be released to end users.

Answer: CE

Explanation:
The correct answers are C and E, because these statements explain what “Done” means. No work left from the definition of “Done” means that all Product Backlog items selected for a Sprint meet the quality criteria agreed upon by the Scrum Team. All work to create software that is ready to be released to end users means that the Increment is potentially releasable at any time during the Sprint.

NEW QUESTION 20
......