Cyber Monday 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 PL
Mob_nav_barsMENU

Scaled Agile Exam SSM Topic 3 Question 21 Discussion

Actual exam question for Scaled Agile's SSM exam
Question #: 21
Topic #: 3
[All SSM Questions]

During which of the following Agile Team events do team members estimate relative story sizes?

Show Suggested Answer Hide Answer
Suggested Answer: A

Backlog Refinement is the Agile Team event where team members estimate relative story sizes.Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single iteration2To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35(Must be taken from SAFe 6 Scrum Master resources)


Team Backlog - Scaled Agile Framework

Backlog Refinement - Scaled Agile Framework

Story - Scaled Agile Framework

How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog

Why Your Agile Team Should Use Relative Story Point Estimation

by Lavonna at Jul 12, 2024, 11:28 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Emerson
4 months ago
C) Iteration Planning, for sure. Unless the test is written by a kangaroo, in which case the answer is probably B.
upvoted 0 times
...
Kerrie
4 months ago
Haha, I bet the test writers are trying to trick us with these Agile terms. But I'm going with C - Iteration Planning sounds about right.
upvoted 0 times
Onita
2 months ago
Let's stick with C, Iteration Planning for this one.
upvoted 0 times
...
Latia
2 months ago
I agree, it's all about planning out the upcoming iteration.
upvoted 0 times
...
Alpha
3 months ago
Yeah, that's when we discuss the work and figure out how long it will take.
upvoted 0 times
...
Valentin
3 months ago
I think you're right, C - Iteration Planning is where we estimate story sizes.
upvoted 0 times
...
Raul
3 months ago
Yeah, that makes sense. Let's go with that.
upvoted 0 times
...
Cathern
4 months ago
I agree, I think it's C - Iteration Planning.
upvoted 0 times
...
...
Kirk
4 months ago
Hmm, I'm not sure. Maybe B) Iteration Review? That's when we look back at the completed stories, right?
upvoted 0 times
...
Krissy
4 months ago
I think it's A) Backlog Refinement because that's where we prioritize and size the backlog items.
upvoted 0 times
...
Rozella
4 months ago
But don't we also estimate during Iteration Review?
upvoted 0 times
...
Johnathon
4 months ago
Definitely C. I remember learning that in my Agile training. Sizing stories is a key part of the planning process.
upvoted 0 times
Alton
4 months ago
It helps the team prioritize and plan their work for the upcoming iteration.
upvoted 0 times
...
Kris
4 months ago
Yes, that's correct. It's important to estimate story sizes during Iteration Planning.
upvoted 0 times
...
Antonio
4 months ago
C) Iteration Planning
upvoted 0 times
...
...
Rueben
5 months ago
I think the correct answer is C) Iteration Planning. That's where we discuss and size the stories for the upcoming sprint.
upvoted 0 times
Nicolette
4 months ago
That way we can plan our sprint effectively and make sure we can deliver on our commitments.
upvoted 0 times
...
Cary
4 months ago
It's important to make sure we have a good understanding of the work involved in each story.
upvoted 0 times
...
Helaine
4 months ago
Yes, you are correct. We estimate relative story sizes during Iteration Planning.
upvoted 0 times
...
Jolene
4 months ago
That's right, it's important to size the stories during Iteration Planning to ensure we can commit to a realistic amount of work for the sprint.
upvoted 0 times
...
An
4 months ago
Yes, you are correct. We estimate relative story sizes during Iteration Planning.
upvoted 0 times
...
...
Giovanna
5 months ago
I believe it's C) Iteration Planning.
upvoted 0 times
...
Rozella
5 months ago
I think it's A) Backlog Refinement.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77