14 seconds is a long time to answer them if you are prepared and don't dilly dally around. For goodness sake, the majority of time, someone is working on the same feature today as yesterday and has no blockers. It takes seconds to communicate.
It isn't like everyone isn't aware of all the work to be done and it isn't an appropriate forum in a cross-functional team to go into details. People do that after with the people interested.
The only time I've found people run over 5 minutes is if the person running the meeting is lax or if meeting doesn't start on time.
I guess sometimes another meeting happening after might get rolled in, but then it isn't a standup.
If you're doing it correctly, it should definitely not run over 15 minutes. Other groups that I've observed are having 30-minute standup meetings with 15 or 20 people and they're dominated by two or three people with lots to say.
That's not what it's for. I like your approach better than ours.
How exactly are you supposed to make three whole statements per person and also leave room for helpful reactions and questions... in an average of 14 seconds per person-statement and response?
That might be how long it takes if nobody has anything to say in response, but it won't be the average, more like the floor.
Either we're not talking about the same thing, or your dev team are moonlighting as auctioneers.