Inputs to the Sprint Planning meeting

Also, when a Sprint is cancelled, there are different factors which are considered. One of them is the following:-

 If part of the work is potentially releasable, the Product Owner typically accepts it.

I am not much clear about this. Can anyone please help me in understanding this?

Hi Urvashi,

Why is the feedback from the stakeholders in the Sprint review meeting not considered as the input in the Sprint planning meeting?

  Why do you think feedback from the stakeholders in the Sprint review meeting not considered as the input in the Sprint planning meeting? Then why is sought in first place ?

If part of the work is potentially releasable, the Product Owner typically accepts it.

Think about a PBI/User story that's completed in a cancelled sprint, what should happen to that and where should that PBI/US go ?

Urvashi,

The feedback from the stakeholders at the Sprint Review should be used in the Sprint Planning Meeting as needed.

That said, it really depends on what type of feedback we are talking about. For example, the view we receive may point out something that the Scrum Team can improve. That will be discussed in the Sprint Retrospective, which is when the Scrum Team assesses itself.

If, however, the feedback is related to the increment released, it can and should be used in the next Sprint Planning meeting and that must respect the roles accountabilities. For example, if due to the feedback, there is a change in priority, it is the Product Owner who needs to translate that into the backlog. If the feedback can help the way the team develops work, it is down to the Dev Team to decide how to implement it. If the feedback highlights an issue, it might be the responsibility of the Scrum Master to remove that impediment.

I hope it helps.

Cheers.

Why is the feedback from the stakeholders in the Sprint review meeting not considered as the input in the Sprint planning meeting?

A very strict answer to your question would be that the Product Backlog should be the single source of requirements, and it should be clearly accounted for by the Product Owner.

However, a Product Owner should go to great lengths to ensure stakeholder interests are properly represented in a timely fashion. This can include inviting stakeholders to a Sprint Review so their feedback can be incorporated into the Product Backlog, and the value of the product maximized in forthcoming Sprints.

As the clear authority on product value, the PO should further account for stakeholder interests in Sprint Planning and throughout each Sprint.