Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

Sprint Report - Closed and New one

Last post 08:41 am April 25, 2023 by Nicholas Gabrichidze
5 replies
01:24 am April 19, 2023

Can you please suggest the best possible Sprint Report examples with:

  1. Carried over backlog.
  2. Velocity
  3. Story Points
  4. Capacity

 


01:34 am April 19, 2023

What do you hope to accomplish with this "Sprint Report" that can't be accomplished through an effective Sprint Review with active participation from the Scrum Team and key stakeholders?


01:39 am April 19, 2023

In a Sprint Review the Product Backlog is updated and nothing is carried over. That's it. The best possible report is no report at all. Who would be reported to and why?


02:24 pm April 19, 2023

Joining the bandwagon but in a slightly different way.

Can you please explain the best possible reasons for Sprint Reports with:

  1. Carried over backlog.
  2. Velocity
  3. Story Points
  4. Capacity

Can you provide definitions of Velocity, Story Points, Capacity so that we can all align on your understanding of them?

Can you explain why the Sprint Review is not adequate enough that you need additional reports?


09:11 pm April 24, 2023

Thanks Thomas, Ian and Daniel for your responses. I have it now.


08:41 am April 25, 2023

The interactive transparent monitoring tools used by developers, would it be Burn Down chart, Kanban, Jira output, whatever else, combined with increment of the product and POs feedback about its value and future release is a best report you can think of. PO can aslo have product burn up chart.

 


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.