Scrum PSM-I Exam - Topic 3 Question 48 Discussion

Actual exam question for Scrum's PSM-I exam

Question #: 48
Topic #: 3

How much of the Sprint Backlog must be defined during the Sprint Planning event?

AJust enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.

BThe entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.

CEnough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

DJust enough to understand design and architectural implications.

Show Suggested Answer

Suggested Answer: B

by Dyan at Jan 07, 2023, 07:17 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Melodie

7 months ago

D makes sense for understanding implications, but we need more than just that.

upvoted 0 times

...

Arlie

7 months ago

Wait, so we don’t need the whole backlog defined? That’s surprising!

upvoted 0 times

...

Micheline

7 months ago

A sounds a bit vague, though. How do we know if we have enough?

upvoted 0 times

...

Maurine

7 months ago

I think B is too strict. Not everything needs to be defined upfront.

upvoted 0 times

...

Lashon

7 months ago

C is spot on! Just enough to get started.

upvoted 0 times

...

Herminia

8 months ago

I remember discussing how the Development Team needs a clear direction, so maybe C is right? It sounds familiar from our last review session.

upvoted 0 times

...

Long

8 months ago

I’m leaning towards A, but I’m not confident. It seems like the Scrum Master’s role is more about guidance than defining everything upfront.

upvoted 0 times

...

Monroe

8 months ago

I feel like it could be B, but that seems a bit too strict. I recall a practice question that emphasized flexibility in the Sprint Backlog.

upvoted 0 times

...

Theron

8 months ago

I think the answer might be C, but I'm not entirely sure. I remember something about just needing enough tasks to get started.

upvoted 0 times

...

Delmy

8 months ago

Ah, this is a tricky one. I think Tanzu Kubernetes Grid is the answer, but I'm not 100% confident. I'll make a note to come back to this if I have time at the end.

upvoted 0 times

...

Cecil

8 months ago

The key is to identify the plan that specifically aims to prevent interruptions to normal business activity. Based on that, I believe the correct answer is a Business Continuity Plan.

upvoted 0 times

...

Ahmad

8 months ago

This is a tricky one. I think the answer might be social engineering, since that relies more on manipulating people rather than just technical measures.

upvoted 0 times

...

Dorinda

8 months ago

This seems like a straightforward ethics question. I'll focus on the key principles of integrity and professional behavior.

upvoted 0 times

...

Aleshia

1 year ago

Just enough to understand the design and architectural implications, huh? Might as well just stare at the ceiling and call it a day. C'mon, people!

upvoted 0 times

Celestine

12 months ago

D) Just enough to understand design and architectural implications.

upvoted 0 times

...

Helene

12 months ago

C) Enough so the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.

upvoted 0 times

...

Gabriele

1 year ago

A) Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.

upvoted 0 times

...

Barbra

1 year ago

Option B? Are you kidding me? That's just setting the team up for failure. Who has time to estimate the entire backlog in one meeting?

upvoted 0 times

...

Cristal

1 year ago

I'm going with option C as well. Trying to define the entire Sprint Backlog during the planning meeting would be way too time-consuming and unrealistic.

upvoted 0 times

Cassie

11 months ago

Option C allows for adaptability while still providing a clear direction.

upvoted 0 times

...

Bettina

12 months ago

It's important to have a balance between planning and flexibility.

upvoted 0 times

...

Beatriz

12 months ago

Definitely, trying to plan out every detail would be overwhelming.

upvoted 0 times

...

Naomi

12 months ago

I agree, option C makes the most sense for efficient planning.

upvoted 0 times

...

Shonda

1 year ago

I'm going with option C as well. Trying to define the entire Sprint Backlog during the planning meeting would be way too time-consuming and unrealistic.

upvoted 0 times

...

Hyun

1 year ago

C) Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

upvoted 0 times

...

Glory

1 year ago

A) Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.

upvoted 0 times

...

Dominque

1 year ago

I agree with Yuette. The Scrum Guide states that only enough of the Sprint Backlog needs to be defined to get the team started. Anything more would be overkill.

upvoted 0 times

Dierdre

1 year ago

C) Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

upvoted 0 times

...

Lashaun

1 year ago

A) Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.

upvoted 0 times

...

Yuette

1 year ago

Option C seems to be the most reasonable approach. We don't need to define the entire Sprint Backlog, but enough to get us started and understand the work that needs to be done.

upvoted 0 times

...

Kaitlyn

1 year ago

I'm not sure, but I think D could also be a valid option as it focuses on design and architecture.

upvoted 0 times

...

Tu

1 year ago

I agree with Filiberto, C makes sense because it helps the team plan for the Sprint.

upvoted 0 times

...

Filiberto

1 year ago

I think the answer is C.

upvoted 0 times

...