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 7 Question 6 Discussion

Actual exam question for SAP's C_ACT_2403 exam
Question #: 6
Topic #: 7
[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

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 Reference:

: Planning Poker


by Kattie at Apr 19, 2024, 08:55 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Clorinda
10 months ago
B seems right. Scrum Master usually estimates complexity.
upvoted 0 times
...
Callie
10 months ago
I’ve always used D. Breaking tasks makes it clearer.
upvoted 0 times
...
Olga
10 months ago
Ah, the age-old question: how to size user stories in Agile? I say we just throw darts at the options and see what sticks. That's the most Agile approach, right?
upvoted 0 times
Tyra
9 months ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Gilbert
9 months ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Ceola
10 months ago
A) Project Manager's relative effort estimate that will be needed to implement and test the user story
upvoted 0 times
...
...
Adelaide
10 months ago
But isn't C more Agile? Ideal Person Days?
upvoted 0 times
...
Portia
10 months ago
I think B could work. Scrum Master using story points.
upvoted 0 times
...
Denise
10 months ago
D seems like a lot of work. Who has time for 'detailed bottom-up effort estimates' when we've got sprints to plan? I'll go with the good old 'relative effort' in option A.
upvoted 0 times
Leslie
10 months ago
Yeah, option A sounds like the way to go for quick sprint planning.
upvoted 0 times
...
Louisa
10 months ago
I think I'll go with option A too, keeping it simple with relative effort estimates.
upvoted 0 times
...
Izetta
10 months ago
I agree, option D does seem like a lot of work.
upvoted 0 times
...
...
Linn
10 months ago
Hmm, I'm torn between B and C. Story points or ideal person days? Decisions, decisions... Maybe I'll just flip a coin!
upvoted 0 times
Marquetta
9 months ago
I prefer using ideal person days for estimating user stories during sprint planning.
upvoted 0 times
...
Anissa
9 months ago
I usually go with story points for sizing user stories in Agile.
upvoted 0 times
...
Mariann
9 months ago
I prefer using ideal person days for estimating user stories during sprint planning.
upvoted 0 times
...
Gerald
9 months ago
I usually go with story points for sizing user stories in Agile.
upvoted 0 times
...
Wynell
10 months ago
Yeah, but ideal person days can give a different perspective on the effort needed.
upvoted 0 times
...
Georgiana
10 months ago
I think story points are more reliable for sizing user stories.
upvoted 0 times
...
...
Glendora
11 months ago
It's definitely D. Bottom-up effort estimate by the product owner.
upvoted 0 times
...
Loren
11 months ago
Option B all the way! Scrum Master knows best when it comes to story points. Forget those project managers and their 'relative effort' nonsense.
upvoted 0 times
Beula
10 months ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Tonette
10 months ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Rima
10 months ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
...
Casey
11 months ago
Which estimation technique for sizing user stories in Agile?
upvoted 0 times
...
Xuan
12 months ago
I think that one is more about breaking down tasks rather than sizing user stories
upvoted 0 times
...
Fausto
12 months ago
Hmm, interesting. What about D) Detailed bottom-up effort estimate by the product owner?
upvoted 0 times
...
Dong
12 months ago
I've heard that C) Relative effort estimate in Ideal Person Days is also a valid option
upvoted 0 times
...
Xuan
12 months ago
Actually, I believe it's B) Detailed top-down effort estimate by the Scrum Master in story points
upvoted 0 times
...
Fausto
12 months ago
I think the estimation technique we use is A) Project Manager's relative effort estimate
upvoted 0 times
...

Save Cancel