BlackFriday 2024! 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

SAP Exam C_ACT_2403 Topic 1 Question 4 Discussion

Actual exam question for SAP's C_ACT_2403 exam
Question #: 4
Topic #: 1
[All C_ACT_2403 Questions]

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

sprint planning?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Carissa at Mar 15, 2024, 07:19 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Truman
5 months ago
Hmm, I'm torn between B and C. Maybe I should just ask the Scrum Master to roll some dice and give me a random number. That's probably as accurate as these options!
upvoted 0 times
...
Kimbery
5 months ago
D all the way! Breaking down the user story into smaller tasks is the only way to get an accurate bottom-up estimate. The product owner knows what's up.
upvoted 0 times
...
Mi
5 months ago
Option A seems a bit outdated. The project manager's relative effort estimate? Come on, this is Agile, we need the dev team's input on this!
upvoted 0 times
Charlene
4 months ago
D) Detailed bottom-up effort estimate by the product owner that breaks up each story into short tasks
upvoted 0 times
...
Paris
4 months ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Vallie
4 months ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Dustin
4 months ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Nadine
5 months ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
...
Clay
5 months ago
Definitely going with C on this one. Relative effort estimate in Ideal Person Days is the way to go for sizing user stories. Seems the most straightforward to me.
upvoted 0 times
Hector
4 months ago
I prefer D, breaking down each story into tasks can give a more accurate estimate.
upvoted 0 times
...
Dante
5 months ago
I think B could also work well, as it provides a detailed effort estimate based on complexity.
upvoted 0 times
...
Onita
5 months ago
It provides a good estimate based on ideal person days.
upvoted 0 times
...
Marti
5 months ago
Agreed, it's a good way to get a clear estimate of the work involved.
upvoted 0 times
...
Kimberlie
5 months ago
I agree, C is the best option for sizing user stories in Agile.
upvoted 0 times
...
Carmelina
5 months ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
...
Antione
6 months ago
That's a good point, Different estimation techniques can work depending on the project.
upvoted 0 times
...
Ailene
6 months ago
I prefer using the Project Manager's relative effort estimate. It gives a broader view of the work needed.
upvoted 0 times
...
Justine
6 months ago
I agree with Story points help give a better understanding of user story complexity.
upvoted 0 times
...
Antione
6 months ago
I think using detailed top-down effort estimate by the Scrum Master in story points is the most accurate.
upvoted 0 times
...
Rene
6 months ago
I would go with A, the Project Manager's estimate is crucial for planning.
upvoted 0 times
...
Francine
6 months ago
I'm with Chantell, B makes more sense to me.
upvoted 0 times
...
Kristeen
6 months ago
I disagree, I believe it's D, the product owner should break down the tasks.
upvoted 0 times
...
Sherly
6 months ago
I think option B is the best choice here. The Scrum Master's estimate in story points is the perfect way to size user stories during sprint planning in an Agile approach.
upvoted 0 times
...
Chantell
6 months ago
I think the answer is B, the Scrum Master should estimate based on complexity.
upvoted 0 times
...

Save Cancel