Think retro as a process that has two parts - take inputs asynchronously and run it synchronously.

Let’s be honest. Teams don’t always have something big to showcase every sprint. Without substantive demos, the sprint reviews become a formality and a reporting exercise. Take a pragmatic approach to sprint reviews instead.

Sprint planning is amongst the most time consuming activities for development teams. One could argue that the value you get is not proportional to the effort you put into these meetings. With some effort you can drop sprint planning meetings completely.

If all you want to share is a “yesterday, today, blockers” update, you don’t need a standup meeting.