Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ScrumStudy SMC Exam - Topic 1 Question 64 Discussion

Actual exam question for ScrumStudy's SMC exam
Question #: 64
Topic #: 1
[All SMC Questions]

You are the Scrum Master for a team that is working on a project for a chemical engineering company. During

one of the Sprints, the Product Owner suggests changes to the Acceptance Criteria on the basis of new

requirements by the stakeholders. Which of the following best describes the steps that should be taken next in

this situation?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Sue at Jan 08, 2023, 01:17 AM

Limited Time Offer

25%

Off

Get Premium SMC Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lenna
5 months ago
D sounds like avoiding responsibility, not cool!
upvoted 0 times
...
Arletta
5 months ago
Wait, can they really reject a deliverable like that? Seems harsh!
upvoted 0 times
...
King
6 months ago
I think A is a bit too much, we can't just re-work everything.
upvoted 0 times
...
Moon
6 months ago
Totally agree, C is the way to go!
upvoted 0 times
...
Josefa
6 months ago
The Product Owner can change Acceptance Criteria anytime!
upvoted 0 times
...
Holley
6 months ago
I vaguely remember something about not re-working deliverables in the same Sprint, so maybe option B is the right choice?
upvoted 0 times
...
Ira
6 months ago
I feel like the team should definitely not reject the deliverable outright, but I can't recall if we should just inform the Product Owner about bandwidth issues.
upvoted 0 times
...
Moira
6 months ago
I think option C sounds familiar from our practice questions, where the deliverable gets added to the backlog for future work.
upvoted 0 times
...
Elenore
6 months ago
I remember we discussed how changes to Acceptance Criteria should be handled, but I'm not sure if we should re-work the User Story in the same Sprint.
upvoted 0 times
...
Lorenza
6 months ago
Hmm, this is an interesting one. I'm not entirely sure why the cause of the risk might not be identified, but I'm thinking it could be due to the organization having a high risk appetite or perhaps they didn't record the cause for cultural reasons.
upvoted 0 times
...
Rolande
6 months ago
I'm a bit confused by this question. What exactly is RBI, and how does it relate to the commitment and cooperation of the organization? I'll need to review my notes to see if I can figure this out.
upvoted 0 times
...
Latia
6 months ago
And for the second recommendation, option B looks good - configuring Service Cloud profile data to sync to the Marketing Cloud profile center. That will help maintain consistent profiles across the platforms.
upvoted 0 times
...
Carmen
11 months ago
Haha, yeah Coletta's got a point. Those stakeholders, always keeping us on our toes! But seriously, C is the way to go here. Gotta keep the Scrum process clean and efficient.
upvoted 0 times
...
Coletta
11 months ago
I'm leaning towards C as well. Seems like the most logical way to handle the situation. Although, I do wonder if the Product Owner will try to sneak in some last-minute changes again. Gotta watch out for those stakeholders, am I right?
upvoted 0 times
Emerson
9 months ago
Absolutely, communication and transparency are key in situations like this.
upvoted 0 times
...
Tyra
10 months ago
Definitely, we need to stay vigilant with the Product Owner and stakeholders to avoid last-minute changes.
upvoted 0 times
...
Tracie
10 months ago
I agree, the deliverable should be rejected and added to the backlog for a future Sprint.
upvoted 0 times
...
Lai
10 months ago
Yes, C does seem like the best option. It's important to prioritize the new requirements.
upvoted 0 times
...
...
Curt
11 months ago
Option B seems reasonable too, but I'm not sure the Product Owner should just reject the deliverable without adding it to the backlog. Gotta keep that transparency, right?
upvoted 0 times
...
Caprice
11 months ago
I agree with Azzie. The Scrum team shouldn't be expected to rework an already developed deliverable in the same Sprint. It's better to handle it as a new requirement in the backlog.
upvoted 0 times
Zona
9 months ago
B) The Scrum Team will not re-work an already developed deliverable; however, the Product Owner will reject the deliverable in Demonstrate and Validate Sprint.
upvoted 0 times
...
Lai
10 months ago
C) The deliverable is rejected on the basis of the changed requirements, and added to the Prioritized Product Backlog with the new Acceptance Criteria to be worked on in a subsequent Sprint.
upvoted 0 times
...
Stefan
10 months ago
A) You will direct the Scrum team to re-work the User Story in the same Sprint.
upvoted 0 times
...
...
Gladys
12 months ago
I'm not sure about that. Option D also seems valid, as we need to consider the team's bandwidth.
upvoted 0 times
...
Azzie
12 months ago
Interesting scenario. I think the best approach here is to go with option C - the deliverable should be rejected due to the changed requirements, and then added to the Prioritized Product Backlog with the new Acceptance Criteria for a future Sprint.
upvoted 0 times
Jade
11 months ago
Yes, rejecting the deliverable and adding it to the backlog for a future Sprint ensures that the new requirements are properly addressed.
upvoted 0 times
...
Lavonna
11 months ago
I agree, option C seems like the most logical step to take in this situation.
upvoted 0 times
...
...
Alecia
1 year ago
I agree with Simona. It makes sense to reject the deliverable and add it to the backlog for the next Sprint.
upvoted 0 times
...
Simona
1 year ago
I think we should go with option C.
upvoted 0 times
...

Save Cancel