Before changing to Scrum, we usually performed some type of review with the Project Manager (now Product Owner), the Project Lead of the development team and the stakeholders. Our development teams are composed of 3 developers and a QA.

The Scrum Guide specifies the participation of the Development Team but does not mention if it is the whole Team or just some representatives.


Is it necessary for all members of the Development Team to participate in the Sprint Review, or could it be done with just a few of them?

1 Answer 1


First off, +1 for checking the Scrum Guide!

The book answer would be that it says the attendees include The Scrum Team and with no extra qualifiers, it can be assumed that it means the whole scrum team (Dev team, PO, SM). But I'd hate to just give you the book answer, so in my time practicing Scrum, here are some of the benefits I've seen to including everyone:

1) No whisper-down-the-alley. If you ever played that game in school, you probably know that for every person a message has to go through, it loses details and gets distorted, regardless of how hard you try to get it right. The Sprint Review is an opportunity to close that gap between stakeholders and developers.

2) It creates ownership. When developers have to show their own work, they value it more. They also get more exposure to the effect their work and other team members work have on the overall product and fulfilling stakeholder needs. When they aren't there it sends a subtle message that it isn't their product to show, even if you don't mean to send that message.

3) It makes it important. Telling a developer that the review isn't worth spending at most an hour per week on diminishes the value of the review and other people notice (and let's face it, it's usually far less).

4) Questions get answered quickly. If either developers or stakeholders have questions, you can answer them on the spot and account for them in the backlog. In my experience, most teams I see not having effective reviews actually spend more time chasing answers down than they would have spent if they just all went to the review.

I'm sure there are many more benefits - those are just the ones that sprint to mind. Maybe other people can add some in the comments that I missed.

  • Excellent points, especially about subtle implicit messages being sent. A few questions of my own : 1. How do you insure that value is injected into these reviews for all participants. There are clear downsides to not attending (as you've noted), but if a team member sees it as "a waste of my time", that has its own negative impact. 2. Does this sort of review invite a bicycle shed scenario, where everyone feels they need to add input, which leads to trivial features being over discussed/weighted?
    – Anthony
    Sep 6, 2018 at 14:19
  • @Anthony: I agree. If the team member finds it to be a waste of their time, it is important to understand why and address it. I've heard quite a few people say that and there are many reasons, so it's important to be curious and understand why. That said, most of the time I see it it has been because they don't actually have stakeholders engaged at the review. For 2, it certainly could, especially if that is common in the company culture. I'd hope the SM or PO would manage that.
    – Daniel
    Sep 6, 2018 at 14:52

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.