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 C_ACT_2403 Exam - 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:

0/2000 characters
Submit Cancel
Dorcas
5 months ago
I thought bottom-up was the only way to go, but I'm open to other methods!
upvoted 0 times
...
Trina
5 months ago
D is a bit outdated, we should focus on story points instead.
upvoted 0 times
...
Yuonne
5 months ago
Isn't it surprising that some still prefer top-down estimates?
upvoted 0 times
...
Doug
5 months ago
I disagree, A seems more structured for sprint planning.
upvoted 0 times
...
Wilda
6 months ago
I think option C is the best for Agile. Breaking it down helps a lot!
upvoted 0 times
...
Wayne
6 months ago
I vaguely recall that ideal person days might not be the best way to estimate in Agile, but I can't remember why.
upvoted 0 times
...
Marla
6 months ago
I feel like the bottom-up approach is more detailed, but I'm uncertain if that's the best fit for sprint planning.
upvoted 0 times
...
Simona
6 months ago
I remember practicing a question similar to this, and I think the team should be involved in sizing user stories, not just one person.
upvoted 0 times
...
Berry
6 months ago
I think we discussed using relative estimation techniques in Agile, but I'm not sure if it's the Scrum Master or the team that does the estimating.
upvoted 0 times
...
Lorriane
6 months ago
Ah yes, I remember learning about this in class. For Agile user story estimation, the team should use a relative effort estimate like story points, not a detailed top-down or bottom-up approach. The key is to estimate as a team, not just have the Scrum Master or Product Owner do it.
upvoted 0 times
...
Yun
6 months ago
I'm a bit confused on this one. I know Agile is all about estimating user stories, but I'm not sure if the "ideal person days" approach is considered Agile or not. I'll have to review my notes on Agile estimation techniques.
upvoted 0 times
...
Ronny
6 months ago
Okay, I've got this. In Agile, we use relative estimation with story points, not detailed effort estimates. The team should come up with the story point estimate together, not just the Scrum Master or Product Owner.
upvoted 0 times
...
Andra
6 months ago
Hmm, this is a tricky one. I know Agile emphasizes estimating user stories, but I'm not totally sure which specific technique is best. I'll have to think this through carefully.
upvoted 0 times
...
Jamie
6 months ago
I'm pretty sure this is asking about estimation techniques used in Agile, so I'll focus on that. I think the key is to use a relative estimation method like story points rather than a detailed top-down or bottom-up approach.
upvoted 0 times
...
Shaquana
7 months ago
Hmm, I'm not too familiar with these security products. I'll need to read through the options carefully to see if any stand out as the "world's most comprehensive" platform.
upvoted 0 times
...
Johnson
7 months ago
Hmm, I'm a bit confused on the difference between != and NOT. I'll have to review that before answering.
upvoted 0 times
...
Sina
7 months ago
I remember a practice question that mentioned accurate reports, and I feel like that ties into data quality too. But I'm not entirely sure!
upvoted 0 times
...
Clorinda
2 years ago
B seems right. Scrum Master usually estimates complexity.
upvoted 0 times
...
Callie
2 years ago
I’ve always used D. Breaking tasks makes it clearer.
upvoted 0 times
...
Olga
2 years 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
2 years ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Gilbert
2 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Ceola
2 years ago
A) Project Manager's relative effort estimate that will be needed to implement and test the user story
upvoted 0 times
...
...
Adelaide
2 years ago
But isn't C more Agile? Ideal Person Days?
upvoted 0 times
...
Portia
2 years ago
I think B could work. Scrum Master using story points.
upvoted 0 times
...
Denise
2 years 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
2 years ago
Yeah, option A sounds like the way to go for quick sprint planning.
upvoted 0 times
...
Louisa
2 years ago
I think I'll go with option A too, keeping it simple with relative effort estimates.
upvoted 0 times
...
Izetta
2 years ago
I agree, option D does seem like a lot of work.
upvoted 0 times
...
...
Linn
2 years 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
2 years ago
I prefer using ideal person days for estimating user stories during sprint planning.
upvoted 0 times
...
Anissa
2 years ago
I usually go with story points for sizing user stories in Agile.
upvoted 0 times
...
Mariann
2 years ago
I prefer using ideal person days for estimating user stories during sprint planning.
upvoted 0 times
...
Gerald
2 years ago
I usually go with story points for sizing user stories in Agile.
upvoted 0 times
...
Wynell
2 years ago
Yeah, but ideal person days can give a different perspective on the effort needed.
upvoted 0 times
...
Georgiana
2 years ago
I think story points are more reliable for sizing user stories.
upvoted 0 times
...
...
Glendora
2 years ago
It's definitely D. Bottom-up effort estimate by the product owner.
upvoted 0 times
...
Loren
2 years 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
2 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
Tonette
2 years ago
C) Relative effort estimate in Ideal Person Days that reflects the best estimate by the project
upvoted 0 times
...
Rima
2 years ago
B) Detailed top-down effort estimate by the Scrum Master in story points, based on the user story complexity
upvoted 0 times
...
...
Casey
2 years ago
Which estimation technique for sizing user stories in Agile?
upvoted 0 times
...
Xuan
2 years ago
I think that one is more about breaking down tasks rather than sizing user stories
upvoted 0 times
...
Fausto
2 years ago
Hmm, interesting. What about D) Detailed bottom-up effort estimate by the product owner?
upvoted 0 times
...
Dong
2 years ago
I've heard that C) Relative effort estimate in Ideal Person Days is also a valid option
upvoted 0 times
...
Xuan
2 years ago
Actually, I believe it's B) Detailed top-down effort estimate by the Scrum Master in story points
upvoted 0 times
...
Fausto
2 years ago
I think the estimation technique we use is A) Project Manager's relative effort estimate
upvoted 0 times
...

Save Cancel