Having been a sysadmin / various kinds of techie for the majority of my career,nevertheless from most of my initial visibility into business & management worlds; and now having been full-time manager for 18 months; my feeling is that absolutely you need to understand, support, and enable your engineers to work on and in the way that makes them productive and satisfied... but last thing you should possibly do is "leave them the fuck alone". Otherwise, very quickly, there would be no salary for anybody :|
That being said, to the topic here, most "standups" I've been to have been a "spoke and hub" model where a PM elicits list of one-on-one status updates, and having done their part, people can doze off for rest of the meeting. In meetings I own, I try to change that to "Tell us of things that matter / are interesting to everybody here". It's not an easy criteria to fulfill though, for management or techies alike.
First, people got demotivated due to seemingly no one caring what they do and when they are done. Some people were unable to finish tasks or self-organize. And this was the most functional team under the circumstances.
Second, in one team where cooperation was necessary, actual lack of defined responsibilities and leader meant that important tasks were not done. There were fights over how less important tasks should be done. Some controlling people tried to take over leadership, fighting among themselves. Then for a while everyone gave up leading to no one having initiative. Then fights again followed by people not talking to each other.
Third, customer ended up complaining over low performance and having to tell everyone the same thing again and again, cause people did not shared info.
To be fair to the agile movement, self-orgainizing teams and the value of individuals are all themes expressed quite clearly.
Maybe you could try a small pilot and see where it goes.
So, the project manager/Scrum Master for the team, plus the technical members of the team. That's it.
You can have guest attendees, if there is a good reason. You can have temporary members, if they're working with the team for a short period of time.
But the basic rule should be just the engineers plus their project manager/scrum master.
And no one should be in multiple standups without a really good reason. Maybe the PMs or Scrum Masters should be in a Scrum of Scrums, but that's about it.
Allow all guests, even announce all times. People will learn to attend where it matters, and simply won't have time for many standups. Format should cut off bad management and time-sinks too. Harder to contain democratization (the opposite of every other suggested model!).
In my experience (27 years worth), agile is a watered-down compromise _on paper_ but is actually worse in practice.
time, features, reliability: pick two
In principle you could have those three if you throw enough resources at them.
How unnecessary!