Home » Scrum » PSM II » What would be two valid actions for Steven, the Scrum Master, to take?
Peter, the Product Owner, has been giving positive recognition to individual Development Team members who have moved their work to ‘done’ during the Daily Scrum. Peter wants to ensure the team is adhering to the ideal guideline on the burndown chart.
What would be two valid actions for Steven, the Scrum Master, to take? (Choose two.)
A. Steven talks with Peter about concerns of how his behavior might impact the team members and request that he stop attending for now.
B. Steven coaches Peter on best practices for updating the burndown chart as it provides accurate information on how well the team is performing.
C. Nothing. Steven is optional at the Daily Scrum and it is the responsibility of the team to decide how to best run it.
D. Steven coaches the Scrum Team about the purpose of the Daily Scrum.
Correct Answer: AD
Explanation/Reference:
Explanation:
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps the Scrum Team understand which of their interactions are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
How To Pass PSM I Exam?
Scrum PSM I PDF dumps.
High quality PSM I PDF and software. VALID exam to help you pass.
|
|
How To Pass PSM II Exam?
Scrum PSM II PDF dumps.
High quality PSM II PDF and software. VALID exam to help you pass.
|
|
I don’t know why “AD” is the right answer. Any help? Thanks
Why D is correct:
The PO, Peter, should not actually be present at the Daily Scrum, otherwise it could degenerate into a status meeting as described to some extent in the scenario.
Why A is correct:
1) See “Why D is correct”.
2) Since the PO only praises the developers who show visible progress, the other developers may get the impression that only the “done” is appreciated. The other developers, who perhaps work on more difficult tasks, where the “dones” are not so quickly achievable, feel unnecessarily pressured.