Just one question, so, if in Scrum "sprint review should happen before anything is shipped to a customer", is it possible that it means that Scrum is not compatible with Continuous Delivery?

Ok, I know, I know. One thing is to Deploy, another is to Release. And if we define "ship" as release, the team can deploy multiple times per day into production and the product department can release after the sprint review.

But, does not sound that inefficient? The aim of Continuous Delivery is getting real feedback as soon as possible, but, if everything is delayed until an arbitrary date.

---

I'm rereading the Official Scrum Guide again. It does not mention the word "ship" (only relationship), but it mentions "release". More exactly it says:

"The Sprint Review should never be considered a gate to releasing value."

That is precisely what Continuous Delivery advocates for: removing all manual approval gates. In this case, means that anything can be shipped to a customer before the Sprint Review.

Now at this point, I am starting to think that after almost two decades practicing Scrum (or variants like ScrumXP, SAFe), no training, no course, no coach, ... really taught me what Scrum really says. But, I believe that Scrum adapted itself to the improvements that have been discovered in software development. So, probably, if I found an older version of the official scrum guide it would say otherwise.

Does it make sense?