Back to Forum

Query on Sprint Review and Product Owner projection of target and delivery dates

Last post 05:46 am June 16, 2020 by Gongyuan Chen
2 replies
Pankaj Singh
11:29 pm June 10, 2020

Hi All,

 

Had a very basic query on the point 2 related to Sprint review.  Product owner project the delivery dates for which items

- PBIs part of the sprint backlog ? if yes, are they not done already

- PBIs not part of any sprints?

Please clarify

Sprint review

1.A Sprint Review is held at the end of the Sprint

2.Product Owner projects likely target and delivery dates based on progress to date (if needed);

 

Thanks in advance

Ian Mitchell
06:00 pm June 12, 2020

Any work which has not yet been done, and which continues to be valuable, will remain on the Product Backlog. The estimates for any such remaining work ought to be kept up to date. The Product Owner should then be able to make projections regarding the likelihood and timescale of future delivery.

Gongyuan Chen
05:46 am June 16, 2020

Sprint Planning

The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

Sprint Planning answers the following:

• What can be delivered in the Increment resulting from the upcoming Sprint?

• How will the work needed to deliver the Increment be achieved?

By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

Sprint Goal

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

As the Development Team works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements functionality and technology. If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

The above is the original "Scrumguide"

From the original text, we found that during and after "Sprint Planning" and "Sprint Goal", PO can predict "target and delivery dates" based on these transparent information

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.