- 45 minutes: it should be 5-10 minutes, 15 on a bad day, and literally never 45.
- 15 people: this is probably just too many people in a single standup. Based on my experience, it's quite likely this can be split up into 2-3 teams that can have more autonomy, and meetings like standups will become far easier to run and far more efficient.
14 doesn't seem crazy to me. And splitting this team up runs into some issues as well.
Do you now have 3 tech leads who acting as pm reporting to the head pm? Do you try to split up the code base? How do you split up QA/Production Champion/Devops? All these decisions seems to have drawbacks.
Whether the codebase should also be split up is another question that is impossible to answer in general. I can speak from experience though and say it's easy to have two teams work on the same large codebase when they're focusing on different areas, different projects, different priorities, etc. I've seen 3-4 different web teams work on the same website with the same underlying codebase without any issues at all because it was clear in advance that their work wasn't going to directly conflict in any way. It would've been hugely counterproductive to force all those people into a single standup and a single team.
Interruptions are frustrating (don't get me started on phone calls), but when you are working on a project collaboratively, touching bases and knowing what other people on your team is doing is important.
I just think stand ups as I've experienced over 10 teams and 5 organizations haven't been especially useful. They have been a status update mostly for the pm and a little for the tech lead.
What is an example of helpful information you guys are sharing in your stand ups?
A big chunk is actually most useful for the PM, but often enough other issues get addressed that our short status meetings don't bother me.
But it always devolves into "what I did..blahblahblah" because both PM/Managers want an accounting and people feel like they need to justify themselves (as you mention).
"what am I doing today" -- not sure yet
I do those every day, they rarely last more than 20 minutes.
seems like your standup team is too big.
As a supporting datapoint, in the entire company I work at, there isn't a single standup with that many people.
A couple of questions Was the company you work at a software product company? Are your teams cross functional? Do people exist across multiple teams?
My fundamental issue with splitting a 15 person team into three 5 person teams it seems more difficult to satisfy two other attributes I think are valuable in teams. That they are cross functional and flat.
Where I work it is all software. We can and sometimes do have folks on multiple teams but generally try to avoid that. And teams can definitely be cross-functional.
how many of those 15 ppl care about what you are doing on a regular basis. I am guessing not more than 5. I've never been in a standup with more than 5-6 people, 15 ppl standup sounds too ridiculous to me.
I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.