I’m almost afraid to answer this because it’s pretty controversial.
Ime. Depends. If it’s in service to the work, and the developers find it useful, then sure. But I’ve seen teams work a whole lot of different ways and be successful.
But the important thing is that the team finds it useful.
There are plenty of ways to build a product or a company that doesn’t rely on a daily meeting.
Remember that Scrum doesn't care about the format: that's up to the developers to decide. Scrum only cares that people stay on the same page and most importantly are productive in helping move forward with open communication and collaboration to hit the sprint goals.
I’ve seen this meeting used by clients and executives to micromanage everything, and sometimes telling the “business owner” they aren’t invited to the meetings isn’t possible. For example, telling a non-technical, micromanaging startup CEO who’s just discovered the power of SCRUM while under pressure for a raise and feeling behind on their product delivery to sit down and just listen very easily. Or in some teams doing a daily meeting works only around releases and they don’t feel like it’s useful all the time. There are a lot of forms that works successfully, but everyone has strong opinions on what does and does not work.
You don’t want to be too prescriptive. What my experience has taught me is to have someone in charge of the product delivery — and then allow them to run the show with whatever support they need. That allows for a lot of flexibility while keeping accountability.
