Skip to main content

Sprint Planning

Last post 06:58 pm April 29, 2024 by Ian Mitchell
6 replies
07:43 am October 19, 2013

Someone asked me question in which will be Sprint Planning provides the Development Team with a target and overarching direction for the Sprint sprint backlog or sprint goal?


12:37 pm October 19, 2013

A Sprint Goal should set the target and overarching direction of the Sprint. In combination with the Sprint Backlog, this represents the Sprint Plan, and is the expected output of a Sprint Planning session.


12:20 am October 22, 2013

Sprint Planning is nothing but detailed planning of each User stories. We can plan the total targeted hours for Development and testing tasks. Even we can plan for the resource availability.


12:45 am October 22, 2013

Sprint Goal provides directions to Dev team while sprint backlog and sprint planning are artifacts and event for supporting and achieving the goal.

Cheers
Sanjay


10:03 pm October 24, 2013

Coming to the Sprint planning the Product Owner should know which his highest priority items are. He then informs the Development team of his desire and this is what forms the initial basis for the Sprint goal.

During the 1st part of the Sprint Planning meeting the Development team picks up items which it thinks it can accomplish during the course of the upcoming Sprint. This is when the Sprint Backlog starts getting formulated and a clearer picture of the Sprint goal emerges. In the 2nd part of the Sprint planning meeting the team figures out to a certain extent how it will accomplish the items it has selected. So you might see tasks, tests, etc etc getting added to the Sprint backlog.
At the end of the Sprint planning meeting the Sprint goal is very clear and it does offer some flexibility to the team.
Bear in mind that the Sprint backlog can change over the course of the Sprint and the team can negotiate with the Product Owner.

Scrum embraces change so trying to predict everything during the Sprint Planning is foolish.


02:41 pm April 29, 2024

Good morning! So, I'm just asking for confirmation: "The drafting of a non-modifiable Sprint Plan at the end of the sprint planning meeting is NOT SCRUM"?


06:58 pm April 29, 2024

That's right. If it was non-modifiable, the Developers would be unable to inspect and adapt their plan during the Sprint, and their ability to meet their commitments under complex evolving conditions would be put at risk.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.