My experience in startups has been that improvements or bug fixes are often ignored in favor of projects that have some long-shot possibility of increasing revenue, even if the existing customers threaten to and do leave over the bugs and hate the new features.
Instead of stand-ups let developers spend 15 minutes each day in a call with a customer who has a problem or feature request.
Extreme Programming got that part covered much better.
At least occasionally look at how actual users are using software?
In case of paying for software system I would require it as part of a contract.
If I would be decision maker on software project I would also demand it.
"We notice you're all still using the old UI and talking about how bad the new UI is when it's actually great! You don't need those features that aren't accessible from the new UI anyway. We're going to default everyone to the new UI now and you'll have to manually change the setting back if you want to."
"Ok you're all still using the old UI, even though the new UI is obviously better, so we're going to turn off the old UI at the end of the month"
"Oooooops! A bunch of people said they'd stop paying us if we turned off the old UI so we will now keep the old UI on until the end of the year"
"The Old UI is gone now. Where did all our customers go?"
In my personal experience, this only happens after the development. We have found no way to obtain useful feedback during the design phase.
Exactly as I said, it's already too late. For it to be most effective, such advice must arrive before I start coding.
Probably the solution is to have the developers get as deep an insight as possible into the problem area they are trying to solve, and work very closely with users at every stage.
Some even expect magical abilities from software to turn bad user data in correct data without any work by U. Address data comes to my mind.
Or I want to see all data at once but why does it take so long and doesn't fit on one page and is incomprehensible?
As far as I can tell, the number one rule of being a UX or UI specialist is that one must never, under any circumstances, actually talk with a U, nor consult the team whose job it is to assist U's with the X the designers and developers swear up and down is so intuitive it should never require explanation.
Most applications are still horrible and unintuitive to the people expected to use them, especially when they're built for niche users. This is the normal experience of using software as a non-developer.
Almost every company has customer support people who are beating their heads against their desks trying desperately to surface this feedback in a way that anyone in the company will care about, but support agents "aren't technical," so the developers don't think they could possibly have anything useful to say about their work.
It's a vicious circle. It doesn't have to be this way. But I'm all put of ideas about how to change it.