Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Atlassian Exam ACP-610 Topic 1 Question 14 Discussion

Actual exam question for Atlassian's ACP-610 exam
Question #: 14
Topic #: 1
[All ACP-610 Questions]

Contribute your Thoughts:

Arthur
2 months ago
Wait, are we talking about Scrum or Scrabble here? Because I'm pretty sure 'sub-task' isn't a Scrabble word.
upvoted 0 times
Emerson
1 months ago
B) Estimated a story in the backlog.
upvoted 0 times
...
Dick
1 months ago
A) Added a fix version on a committed story.
upvoted 0 times
...
...
Tiera
2 months ago
Hmm, this is tricky. I'm going to go with A and E. Adding a fix version and adding a sub-task seem like the most logical scope changes to me.
upvoted 0 times
Annelle
14 days ago
Yes, those actions would definitely change the scope of the sprint.
upvoted 0 times
...
Emily
19 days ago
I agree, adding a fix version and a sub-task definitely impact the scope.
upvoted 0 times
...
Bettye
1 months ago
I think A and E are the correct actions for scope change.
upvoted 0 times
...
...
Ashley
2 months ago
Hold on, did they say the team uses Story Points? In that case, I'm going with D and F. Logging work on committed stories doesn't change the scope, right? Unless the Story Points change, of course.
upvoted 0 times
Wilson
1 months ago
F) Logged work on several committed stories.
upvoted 0 times
...
Cecily
1 months ago
D) Modified the estimate value on a committed story.
upvoted 0 times
...
...
Jerrod
2 months ago
I think B and C are the correct answers. Estimating a story in the backlog and dragging an estimated story from the backlog to the sprint don't change the scope.
upvoted 0 times
Yolande
1 months ago
Adding a fix version and modifying estimate value on a committed story are the actions that change the scope.
upvoted 0 times
...
Inocencia
2 months ago
I agree, those are the correct actions that reflect scope change.
upvoted 0 times
...
Claribel
2 months ago
Estimating a story in the backlog and dragging an estimated story from the backlog to the sprint don't change the scope.
upvoted 0 times
...
Jerilyn
2 months ago
I think B and C are the correct answers.
upvoted 0 times
...
...
Pedro
2 months ago
Options D and E are the correct answers. Modifying the estimate value on a committed story and adding another sub-task to a committed story are both considered scope changes.
upvoted 0 times
...
Cyndy
2 months ago
I believe dragging an estimated story from the backlog to the sprint is also a scope change.
upvoted 0 times
...
Yuki
3 months ago
I agree with Deangelo. Modifying the estimate value on a committed story is also a scope change.
upvoted 0 times
...
Deangelo
3 months ago
I think adding a fix version on a committed story is a scope change.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77