Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

BCS Exam CTFL4 Topic 3 Question 17 Discussion

Actual exam question for BCS's CTFL4 exam
Question #: 17
Topic #: 3
[All CTFL4 Questions]

During iteration planning, a scrum team uses an estimation technique called planning poker to estimate the effort required to deliver a critical user story. In advance of the estimation session, the team agreed on some ground rules to limit the number of poker rounds and save time.

The team agreed on the following:

1. They will use the following progression for estimation: Extra-small, Small, Medium, Large, Extra-large, and Extra-extra-large.

2. If estimation values differ significantly, the highest score will be used for estimation purposes.

The result of the first round of planning poker:

Team Member Estimation

Business Large

Development Extra-extra-large

Testing Extra-extra-large

Which of the following options best represent the team's next actions?

Show Suggested Answer Hide Answer
Suggested Answer: D

In a planning poker session, if there is a significant difference in the estimations, it indicates that there may be misunderstandings or different perspectives on the complexity of the user story. According to the agile principles, the team should discuss these differences to reach a common understanding. The goal is to ensure that all team members have a shared understanding of the user story's scope and complexity before finalizing the estimate.


Contribute your Thoughts:

Skye
2 months ago
Ah, the joys of planning poker. Where the numbers are made up and the points don't really matter!
upvoted 0 times
...
Sophia
2 months ago
The business rep's view is important, but the whole team should be involved in the estimation process. I'd go with option D and discuss the differences.
upvoted 0 times
...
Penney
2 months ago
I'm not sure breaking it down into smaller stories is necessary. The high estimates just mean the team has more work to do, not that the user story is poorly understood.
upvoted 0 times
Katina
1 months ago
D) the team discusses the differences in the estimates and repeats the poker round until an agreement is reached.
upvoted 0 times
...
Roy
1 months ago
B) The pre-agreed rules state that the highest score should be used for estimation, resulting in the user story being categorised as Extra-extra-large.
upvoted 0 times
...
Fidelia
1 months ago
A) The fact that all estimations are high indicate that the user story is not well understood or should be broken down into multiple smaller stories.
upvoted 0 times
...
...
Tawanna
3 months ago
The pre-agreed rules seem clear to me - we should use the highest score, which is Extra-extra-large. No need to overthink this.
upvoted 0 times
Merilyn
1 months ago
D) the team discusses the differences in the estimates and repeats the poker round until an agreement is reached.
upvoted 0 times
...
Michell
1 months ago
B) The pre-agreed rules state that the highest score should be used for estimation, resulting in the user story being categorised as Extra-extra-large.
upvoted 0 times
...
Antione
2 months ago
A) The fact that all estimations are high indicate that the user story is not well understood or should be broken down into multiple smaller stories.
upvoted 0 times
...
...
Donte
3 months ago
But shouldn't we also consider the input from the business representative in categorizing the user story? Option C seems valid too.
upvoted 0 times
...
Kirby
3 months ago
I disagree, I believe option B is the correct action as per the pre-agreed rules to use the highest score for estimation.
upvoted 0 times
...
Donte
3 months ago
I think option A is the best choice because all estimations are high, indicating a lack of understanding or need to break down the user story.
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