Recently I’ve been thinking about feedback loops.
Sprint Review is a working session, not a presentation. But even if some customers participate as stakeholders, it’s challenging to establish what value Increment will generate for them before they start working with the product “for real.” They can’t do that before we release the Increment. I’d argue that before that, all we have are stakeholders opinions.
I’m not saying we need to release every Sprint (or more often). But the fact that the Scrum Guide doesn’t mention releasing at all puzzles me. After all, that’s the only way to get a full feedback. I believe it deserves a comment in the Scrum Guide.
(As the Scrum Framework supports other types of products, I do not mention DevOps etc. Whether the generalization helps software products is a different question.)