Best describes the topics covered in Sprint Planning

> I think answer 1 is right

The question isn't simply asking for the right answer, it's asking for the best one. The process of evaluation is important. So, why do you believe answer 1 is the best? Can you explain why the other options don't seem to be as good?

Hello Ian,

i think:

2: It is input for other Meeting
3: Scrum team member roles (PV, DT and Scrum Master) must be clear by beginning the project and when changed not input for sprint Planning meeting
4: who will do it discuss in daily scrum

But im not sure righty answer is number 1 or 2

2: It is input for other Meeting

Yes, what went wrong & what to do differently should be discussed in a Sprint Retrospective, not Sprint Planning

3: Scrum team member roles (PV, DT and Scrum Master) must be clear by beginning the project and when changed not input for sprint Planning meeting

Membership could potentially change as an adaptation following a Sprint Retrospective, but it would be unusual to do so. You are right that the matter has nothing to do with Sprint Planning.

4: who will do it discuss in daily scrum

The team can make tentative plans for the allocation of work to team members during Sprint Planning. However, any such plans are subject to modification during the Daily Scrum, or indeed at any point. Therefore, this is not likely to be the best answer.

What about number 5 though? Should a Scrum Team look at "how conditions have changed and how the Product Backlog should evolve"? If so, can you identify the Scrum Event that is most suitable for that purpose?

Yes. Check requirements / conditions changed is important! And impact must be considered into PB. 1 and 5 correct. But detailed and important statement answer 5.
Thank you for your help Ian :-)

Hi Mandy,

For (5), would you consider the Sprint Review event to be more appropriate?

I would say that answer 5 is more about Backlog Grooming and Sprint Review but can be done in any Scrum event as all of them are an opportunity to inspect and adapt.
So I would say that answer 1 is the best fit.
Please correct me if I'm wrong as I'm planning to pass the PSM assessment and think this question might come up.

Hi Darya,

From an assessment perspective, I would select 1.

If there's more clarification needed, I would encourage people to look at the Scrum Guide's section on "Sprint Planning."

Sprint Planning answers three questions; Why, What, and How. 

The answer is 1.

Why this/these PBIs? Usually answered and clarified by the Product Owner, after which developers should have the courage to voice their concern if they think otherwise, then the whole team can respectfully deliberate on it and agree.

What do we need to do? Usually answered by the developers

How do we do it to meet DoD and the timebox? Usually answered by developers, taking Definition of Done into consideration as well the the sprint timebox of 30 days (or less depending on what the team agrees on)

Why?

PO proposes how product increase value in the current sprint, the Scrum Team defines a Sprint Goal reflecting this and communicating this to the stakeholders.

What? 

Dev Team selects PBIs based on past performance and DoD, Scrum Team refines.

How?

PBIs be decomposed by Dev Team into work items smaller than one day and how to work on them is at their sole discretion.

Sprint Backlog

Why (Goal), What (PBIs) and How (Plan) is referred to as the Sprint Backlog.

I will post easy-to-understand articles, videos and infos around my understanding of this exciting framework on my blog.