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

SAP Exam C_ACT_2403 Topic 1 Question 1 Discussion

Actual exam question for SAP's C_ACT_2403 exam
Question #: 1
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 Tyra at Mar 18, 2024, 09:26 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
Lamar
1 years ago
I personally prefer option C, where we use relative effort estimate in Ideal Person Days. It gives the best estimate for the project.
upvoted 0 times
...
Youlanda
1 years ago
I disagree with I believe option D is more accurate, where the product owner breaks down each story into tasks for a detailed bottom-up effort estimate.
upvoted 0 times
...
Jolene
1 years ago
I think the best estimation technique to use in Agile is B, where the Scrum Master provides a detailed top-down effort estimate in story points.
upvoted 0 times
...
Thomasena
1 years ago
Wait, they're not asking about the best way to estimate pizza toppings during the company lunch, are they?
upvoted 0 times
Brent
1 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Gilma
1 years ago
A) Project Manager's relative effort estimate that will be needed to implement and test the user story
upvoted 0 times
...
...
Chan
1 years ago
Thanks for clarifying, Tomas. I think I'll go with D as well now.
upvoted 0 times
...
Cordelia
1 years ago
I dunno, Option D sounds like a lot of work. Isn't Agile supposed to be all about simplicity? I'm going with Option B.
upvoted 0 times
Lyndia
1 years ago
I think I'll go with Option B too. It just makes more sense in an Agile approach.
upvoted 0 times
...
Kenny
1 years ago
I agree, Agile is all about simplicity. Option D does seem like a lot of work.
upvoted 0 times
...
Ozell
1 years ago
Yeah, simplicity is key in Agile, I also prefer Option B.
upvoted 0 times
...
Hannah
1 years ago
Option B is the way to go. It's simple and based on story complexity.
upvoted 0 times
...
Nan
1 years ago
I think Option B is the way to go, keeping it simple in Agile.
upvoted 0 times
...
Carla
1 years ago
I agree, Option D does seem like a lot of work.
upvoted 0 times
...
...
Tomas
1 years ago
Option B is about the Scrum Master estimating based on complexity, while option D is about breaking down the story into tasks for a detailed estimate.
upvoted 0 times
...
Dusti
1 years ago
I'm not sure about this question. Can someone explain the difference between the options?
upvoted 0 times
...
Wei
1 years ago
Hah, Option A is a joke, right? We're in the 21st century, not the 90s. Scrum Master all the way!
upvoted 0 times
Orville
1 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Markus
1 years ago
A) Project Manager's relative effort estimate that will be needed to implement and test the user story
upvoted 0 times
...
Peggy
1 years ago
Yeah, we need to embrace Agile practices and move away from old-fashioned estimation techniques like Option A.
upvoted 0 times
...
Lenna
1 years ago
Agreed, the Scrum Master's approach is more accurate and takes into account the complexity of the user stories.
upvoted 0 times
...
Isadora
1 years ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Novella
1 years ago
Option A is definitely outdated. Scrum Master's detailed top-down effort estimate in story points is the way to go.
upvoted 0 times
...
Flo
1 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
...
Catrice
1 years ago
Personally, I prefer Option C. Ideal Person Days is a classic estimation technique that works well for Agile. Keeps things simple!
upvoted 0 times
Reena
1 years ago
I think Option B could also work well, as it provides a detailed effort estimate based on the complexity of the user story.
upvoted 0 times
...
Janet
1 years ago
I agree, Option C is a great choice for Agile projects. It helps in keeping the estimation simple and effective.
upvoted 0 times
...
...
Galen
1 years ago
Option B is the way to go! Story points are the way to estimate in Agile, not some arbitrary 'Manager's estimate'.
upvoted 0 times
...
Chan
1 years ago
I disagree with you, Tomas. I believe the answer is D. The product owner should break up the story into tasks for a detailed estimate.
upvoted 0 times
...
Tomas
1 years ago
I think the answer is B. The Scrum Master should estimate the user story in story points.
upvoted 0 times
...

Save Cancel