C. Encourage the team to more frequently interact with all stakeholders
Frequent interaction with stakeholders can help the team better understand the priorities, expectations, and feedback, which can improve their ability to take ownership of the delivery and keep up with sprint commitments. This approach fosters collaboration and ensures that the team is aligned with stakeholder needs, helping them to meet their goals more effectively.
I think it's very unclear how any of the given options would directly affect the Team's ability to complete their Sprints and meet their commitments. The Team is overestimating and overloading the Sprints.
For C., I do not see how interacting with stakeholders would help the Team complete their committed work.
For A., this is an option, still not quite to the point but with expectation setting the Team could move into greater alignment.
Honestly, the problem set and answers are too broad.
I don't think the issue is a lack of stakeholder engagement. As I see it, the Team is unable to keep up with delivery and commitments. Therefore, expectations would need to be set.
I vote for A.
There lack of sense - who is struggling to whom?
If the issue is:
- sponsor's resistance - the correct answer would be A
- team collaboration with the sponsor - the correct answer would be C
Anyway - more logical is C than A, since the team fails to keep up the sprint commitments.
What the team is struggling with is a mystery. But it is a fact that the team is in face of the difficulty on delivery as they commited. We don't know whether the problem is caused by (D) product design or (C) stakeholders. (B) is not Agile for a list and agreement, Hence (A) becomes the better answer. Team expectations are what you anticipate and expect from your team. (A) shields the team from the impact of high team expectations of the sponser
What the team is struggling with is a mystery. But it is a fact that the team is in face of the difficulty on delivery as they commited. We don't know whether the problem is caused by (D) product design or (C) stakeholders. (B) is not Agile for a list and agreement, Hence (A) becomes the better answer. Team expectations are what you anticipate and expect from your team. (A) shields the team from the effect of team expectations of the sponser
What the team is struggling with is a mystery. But it is a fact that the team is in face of the difficulty on delivery as they commited. We don't know whether the problem is caused by (D) product design or (C) stakeholders. (B) is not Agile for a list and agreement, Hence (A) becomes the better answer. Team expectations are what you anticipate and expect from your team. (A) lows down the team expectations of the sponser
B & D does not have anything to do with the issue.
C makes more sense than A as the Team should get a vision to be able to take ownership of the delivery
I'm not english-native speaker and "struggle to do something" confused me. But correct translation is "Team working very hard to take ownership of delivery, but ..." It this case Scrum Master don't need to push team even more to take ownership. SM has to shield team from negative effect of failing the iteration. So A. seems to be correct answer.
upvoted 2 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Opemati90
1 month, 2 weeks agothewalker
2 months, 3 weeks agojanojano
9 months, 3 weeks agojanojano
10 months agoPetrevski
1 year, 6 months agoMinhha3
1 year, 7 months agoInvisibleBeing
1 year, 10 months agoEli8
2 years, 3 months agoEli8
2 years, 3 months agoEli8
2 years, 3 months agocozyhead
2 years, 4 months agorichck102
2 years, 4 months agothuha1704
2 years, 8 months agoHTTPS
3 years, 5 months agoVijayKrish
3 years, 10 months agoMokel
4 years agosrv3
3 years, 11 months ago