Answering: “Select two ways in which technical debt impacts transparency.” (SPS)

Select two ways in which technical debt impacts transparency.
(choose the best two answers)
A. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
B. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
C. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
D. It enhances transparency for the Product Owner as the Developers are not allowed to do additional feature development in a Sprint as long as there is technical debt.

Answering: “Select two ways in which technical debt impacts transparency.” (SPS) Read More »

Answering: “There are five Scrum Teams working on a Product. During the Nexus Sprint Review, the teams present the results of the Sprint. After introductions, each team takes time to present their work for inspection by individually showing the new features they have built. They are not using a shared environment. The stakeholders do not provide much feedback. The event ends and people filter out of the room. You overhear a few stakeholders talking about their concerns about the product after the Nexus Sprint Review. They didn’t find the review valuable. Why?”

[color=#6495ed]Scenario A: Nexus Sprint Review with Five Scrum Teams[/color]
There are five Scrum Teams working on a Product. During the Nexus Sprint Review, the teams present the results of the Sprint. After introductions, each team takes time to present their work for inspection by individually showing the new features they have built. They are not using a shared environment. The stakeholders do not provide much feedback. The event ends and people filter out of the room.
You overhear a few stakeholders talking about their concerns about the product after the Nexus Sprint Review. They didn’t find the review valuable. Why?
(choose the best answer)
A. The Nexus Sprint Review was not a review of the Integrated Increment and Nexus Sprint Goal, but rather a review of each team’s individual work.
B. The Nexus Sprint Review should have been longer. It failed to cover all completed work in detail.
C. The Stakeholders lack understanding of Scrum and coaching.
D. All of the above.

Answering: “There are five Scrum Teams working on a Product. During the Nexus Sprint Review, the teams present the results of the Sprint. After introductions, each team takes time to present their work for inspection by individually showing the new features they have built. They are not using a shared environment. The stakeholders do not provide much feedback. The event ends and people filter out of the room. You overhear a few stakeholders talking about their concerns about the product after the Nexus Sprint Review. They didn’t find the review valuable. Why?” Read More »

Answering: “Why is it important that there is only one Product Owner, who has the final say on the Product Backlog, for each product?”

Why is it important that there is only one Product Owner, who has the final say on the Product Backlog, for each product?
(choose the best three answers)
A. It is clear who is accountable for the ultimate success of the product.
B. The Scrum Team always knows who determines priorities.
C. It allows the Product Owner to control all decisions made about what the Developers work on during a Sprint.
D. It helps avoid barriers to effective communication and rapid decision-making.

Answering: “Why is it important that there is only one Product Owner, who has the final say on the Product Backlog, for each product?” Read More »

You cannot copy content of this page