2023 PSPO-I dumps review - Professional Quiz Study Materials [Q10-Q33] : IT Certification Exam Braindumps : http://blog.braindumpsit.com

NEW QUESTION 10
Which two of the following are not correct about non-functional requirements?

The Project Manager takes care of non-functional requirements.

Non-functional requirements can be added to the Product Backlog.

Non-functional requirements are reflected in the Sprint Goal.

Non-functional requirements can be added to the Definition of Done.

NEW QUESTION 11
The collaboration between the Developers and the Product owner is very important for the product .
Which of the following is the least productive way for the Scrum Master to improve this collaboration?

The Scrum Master should act as a go-between for them.

The Scrum Master should teach them techniques to improve it.

The Scrum Master should suggest new collaboration tools.

NEW QUESTION 12
Decisions about engineering and development methods are made by the Product Owner.

True

False

NEW QUESTION 13
For the Product Backlog the commitment is the Product Goal.

TRUE

FALSE

NEW QUESTION 14
The Product Backlog should have just enough detail.

False

True

NEW QUESTION 15
Which questions does the Sprint Planning answer?

What can be delivered in the Increment resulting from the upcoming Sprint?

Who will do which Sprint Backlog item?

How will the work needed to deliver the Increment be achieved?

NEW QUESTION 16
Which of the following best describes the Scrum Pillar “Transparency”?

The whole process should be visible to everyone.

The process should be visible to the key stakeholders.

Significant aspect of the process must be visible to those responsible for the outcome.

NEW QUESTION 17
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.

FALSE

TRUE

NEW QUESTION 18
What arethetwo responsibilities of testers in a Scrum Team?
(choose the best two answers)

Tracking quality metrics.

Scrum has no “tester” role.

Verifying the work of programmers.

The Developers are responsible for quality.

Finding bugs.

Explanation
* Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles
* or titles, such as “tester”, “analyst”, “designer”, or “architect”.
* The Developers are the people in the Scrum Team who are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
* The Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.
* The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.
* The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Quality: https://www.scrum.org/resources/blog/quality-scrum-value

NEW QUESTION 19
What is the time box for the Sprint Retrospective (one-month Sprint)?

Maximum 3 hours.

Maximum 4 hours.

Minimum 8 hours.

Minimum 4 hours.

NEW QUESTION 20
Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism.

FALSE

TRUE

NEW QUESTION 21
Sprints are fixed length events of one month or less to create consistency.

YES

NO

NEW QUESTION 22
Is it allowed to forcast the Sprint progress using burn-up charts, following Scrum?

NO

YES

NEW QUESTION 23
How much of the overall working time should the Product Owner spend with the Developers?

At least 15% of the time.

As much as required.

Min. 50% of the time.

NEW QUESTION 24
What happens usually between a Sprint Retrospective and the next Sprint Planning?

User Story “grooming”.

Nothing!

Product Backlog refinement.

NEW QUESTION 25
Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?
(choose the best two answers)

The Product Owner should not concern themselves with meeting the Definition of Done, it is the Developer’s responsibility.

To be able to punish the team when they do not meet their velocity goal for the Sprint.

To forecast the team’s productivity over time.

The Definition of Done can affect the product’s total cost of ownership.

To have complete transparency into what has been done at the end of each Sprint.

NEW QUESTION 26
The Product Backlog is baselined before the Sprint 0.

False

True

NEW QUESTION 27
Who “owns” the Product Backlog?

The Product Owner

The Developers

The Scrum Master

NEW QUESTION 28
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)

Whenever a team member can accommodate more work.

At the Sprint Planning Event.

During the Daily Scrum.

Never. The entire Scrum Team is accountable for creating value every Sprint.

Explanation
Answer D. Never. The entire Scrum Team is accountable for creating value every Sprint.
Explanation: According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product andthe work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team’s progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.
References:
* [Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
* Accountabilities in Scrum | Scrum.org: “Scrum has three accountabilities, each with a different focus :
Product Owner (green figure) The “What”. With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The “How”. Focus on building something that is Done – that the increment is useable and potentially releasable.”
* What is a Developer in Scrum? | Scrum.org: “The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal”

NEW QUESTION 29
As a Product Owner, which of the following tasks should you do?

Coaching the Scrum Team how to use Scrum.

Decomposing Product Backlog items.

Managing the Product Backlog.

Creating the Product Backlog items.

NEW QUESTION 30
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.

TRUE

FALSE

NEW QUESTION 31
As the Developers start work during the Sprint, they realize they have selected too much work to finish in the Sprint. What should they do?
(choose the best answer)

Find another Scrum Team to give the excess work to.

As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.

Inform the Product Owner at the Sprint Review, but prior to the demonstration.

Reduce the Definition of Done and get all of the Product Backlog items done by the new definition.

NEW QUESTION 32
If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.

TRUE

FALSE

NEW QUESTION 33
Which two statements about the Developers are correct?

The Developers decide when to do the next release.

The Developers are not allowed to help the Product Owner managing the Product Backlog.

The Developers own the Definition of Done.

The Developers are self-organized.