|
Scrum PSPO I Exam Page 16 (Dumps)
Question No:-76
|
The Scrum Master should not allow the Product Owner to attend the Sprint Planning if the PO is not ready with a Sprint Goal. Is this true or false?
(1) True
(2) False
|
Answer:-(2) False
For Note:-
False. The Scrum Team crafts a Sprint Goal during the Sprint Planning.
|
|
Question No:-77
|
All Development Teams working on the same Product should use the same Product Backlog.
(1) True
(2) False
|
Answer:-(1) True
For Note:-
Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.
|
|
Question No:-78
|
Select the three best options to finish the sentence below.
Technical debt …
(1) is a lack of technical supplies
(2) belongs entirely to the Development Team. No one else should know about it.
(3) reflects some extra development work
(4) compromises long-term quality of the Product
(5) is a real risk which can genuinely be incurred
|
Answer:-(3),(4) and (5)
For Note:-
Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution. In other words it can be defined as the longer term consequences of poor design decisions. Technical debt is a real risk which can genuinely be incurred. It compromises long-term quality of the Product.
One of the ways of handling technical debt is recording it on the Product Backlog. So, it becomes visible to the Scrum Team.
|
|
Question No:-79
|
Who identifies the Key Stakeholders for the Product?
(1) The Scrum Team
(2) The Product Owner
(3) The Upper Management
(4) The Development Team
(5) The Scrum Master
|
Answer:-(2) The Product Owner
For Note:-
In order to maximize value, the Product Owner should identify the Key Stakeholders for the Product, and involve them as necessary throughout the development effort.
|
|
Question No:-80
|
How frequently product releases should occur?
(1) Every 3 months
(2) By the end of Product development
(3) Every Sprint
(4) Frequently enough to eliminate the risk that the product’s value will get out of line with the marketplace
(5) At least every 6 months
|
Answer:-(4) Frequently enough to eliminate the risk that the product’s value will get out of line with the marketplace
For Note:-
While Scrum doesn’t require a release to occur every Sprint, it should be noted that the more elapsed time that accumulates since the last release, the higher the risk that the product’s value will get out of line with the marketplace. Product Owners should keep this risk in the forefront of their mind. Looking at it another way, the sooner you release, the sooner you can start capturing the value created by the product.
|
|
|