SAP Exam C_ACTIVATE22 Topic 6 Question 17 Discussion

Actual exam question for SAP's C_ACTIVATE22 exam

Question #: 17
Topic #: 6

[All C_ACTIVATE22 Questions]

Which estimation technique can you use in an Agile delivery approach to size the user stories during sprint planning?

ADetailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity

BProject Manager's relative effort estimate that will be needed to implement and test the user ^ story

CDetailed bottom-up effort estimate by the product owner that breaks up each story into short ^ tasks

DRelative effort estimate in Ideal Person Days that reflects the best estimate by the project ^ team

Show Suggested Answer

Suggested Answer: A

A is correct because Planning poker is an estimation technique that you can use in an Agile delivery approach to size the user stories during sprint planning. Planning poker is a game where each team member uses a set of cards with numbers that represent the relative effort of a user story. The team members reveal their cards simultaneously and discuss their estimates until they reach a consensus. This technique is based on the concept of story points, which are units of measure for expressing the overall effort required to fully implement a user story. Story points are assigned to user stories based on their complexity, risk, and uncertainty. Verified :

: Planning Poker

by Glory at Mar 20, 2024, 09:37 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Jestine

5 months ago

Detailed estimates? In Agile? What is this, the Dark Ages? I'm going with D - the team knows best.

upvoted 0 times

Octavio

4 months ago

Yeah, detailed estimates can slow down the Agile process. Let's trust the team's judgment.

upvoted 0 times

...

Marylyn

4 months ago

I agree, the team's estimate in Ideal Person Days is the way to go.

upvoted 0 times

...

Reyes

4 months ago

B) Project Manager's relative effort estimate that will be needed to implement and test the user story

upvoted 0 times

...

Serina

4 months ago

Yeah, detailed estimates can slow down the Agile process. Let's trust the team's judgment.

upvoted 0 times

...

Darci

4 months ago

C) Detailed bottom-up effort estimate by the product owner that breaks up each story into short tasks

upvoted 0 times

...

Mertie

4 months ago

D) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project team

upvoted 0 times

...

Gerald

4 months ago

I agree, the team's estimate in Ideal Person Days is the way to go.

upvoted 0 times

...

Quiana

5 months ago

I tend to agree with C seems like the most appropriate estimation technique for Agile delivery.

upvoted 0 times

...

France

5 months ago

I disagree, I believe the answer is C. The product owner breaks down each story into tasks for a detailed bottom-up effort estimate.

upvoted 0 times

...

Pearly

5 months ago

I think the answer is A. The Scrum Master usually provides detailed top-down effort estimates based on story complexity.

upvoted 0 times

...

Felix

5 months ago

That makes sense, breaking down each story into tasks can be more accurate.

upvoted 0 times

...

Lisha

5 months ago

I prefer detailed bottom-up effort estimate by the product owner.

upvoted 0 times

...

Eleni

5 months ago

I don't know, man. Detailed estimates from the Scrum Master or Product Owner seem a bit overkill for Agile. Let's go with the team's best judgment on this one.

upvoted 0 times