In one of the projects, we have business stakeholders signing off completed user stories in the Daily Scrum.

There are instances where we will not have any stories to demo in the Sprint Review, as they've all been gone over during the Daily Scrums. We cancel the Review.

The Scrum guide clearly says that we need to have these separate meetings.

Please give your inputs on canceling the Sprint Review.

  • 2
    Opinion polls are generally off topic. If your practices are causing you some specific problem, please describe it in detail and provide some additional context.
    – Todd A. Jacobs
    Mar 3, 2019 at 3:16
  • @ToddA.Jacobs I am not having any issues with that, but would like to have an expert opinion if this is Okay to be put in practice across organization Mar 3, 2019 at 3:42
  • Are the business stakeholders just confirming that the stories are done according to the acceptance criteria, or do you also get discussions where they try to change the scope of stories and/or what work will be picked up next during the current sprint? Mar 3, 2019 at 10:35
  • @BartvanIngenSchenau They confirm the stories based on the acceptance criteria. No further discussion on future stories / sprint. Mar 3, 2019 at 12:24
  • 5
    This is not Scrum. Still, if it works for you, why change it? If not-Scrum works for you, asking anyone outside your organization if the process is okay is just opinion polling.
    – Todd A. Jacobs
    Mar 3, 2019 at 15:17

2 Answers 2


I would give the following comments to your practice.

Daily Scrum:

The daily Scrum is a meeting for the team members to discuss if it is possible to reach the sprint goal. In my opinion, there is no space for Stakeholders to review certain user stories.

Sprint Review:

I wouldn't cancel the meeting. Referred to the Scrum Guide, demo the user stories, which are done, is not the only item on the agenda.


In a good Scrum team, there is in any way a lot of contact with the stakeholders. I would define an additional bullet in my Definition of Done: Reviewed the functionality with affected Stakeholders.

It's up to you to decide. But I recommend leaving the agenda list of the Daily Scrum as it is.


A few things to consider:

First, let's start with the best: you have super-engaged stakeholders. That is so awesome! And nothing in Scrum says you have to wait until the end of the sprint to show completed work to stakeholders. I don't think it can be overstated how wonderful it is that your team and stakeholders talk frequently!

Personally, I wouldn't do it at the daily scrum. The daily scrum is for the team to sync up. I can see that knowing if a key stakeholder is happy with the work could be useful info for in my daily scrum, but I would do it before. Personally, I'd be nervous that the stakeholder conversation would crowd out the conversations that are supposed to be happening in the daily scrum.

Lastly, I want to encourage you to push further and get more out of it. The idea of sign-off can be problematic in scrum. Because you don't want ambiguity in signoff, you usually consolidate that decision into one person. This can limit your view to one stakeholder, when there are actually many. Signoff also usually frames work in a pass / fail context. In Scrum we want feedback. If you are meeting every stakeholder's every need on the first try, that is suspicious (largely because that is probably an impossible task). This is where is is still important to have that review. Have every stakeholder who is interested attend. Hear all of their feedback. Decide how that impacts your backlog - what do you keep, what do you set aside. This is where the benefits of scrum really shine through!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.