|
I mean, whoever is facilitating the standup should be telling people to take it outside of the standup. THat's where poo poo breaks down during a standup and make it turn into the most useless meeting. Our offshore teams used to have 1:1 standups that lasted for 2 hours. I tried talking/coaching the PM who was doing this but they said it was just their culture to be very personal with their devs.
|
#
¿
Dec 9, 2015 01:08
|
|
|
|
| # ¿ May 12, 2024 09:03 |
|
|
I'll usually just ask my teams to tell me their plan for the day. Any discussion outside of their plans for the day are relegated to huddling after (1:1 or whoever wants to participate basically). I try to keep the meeting to a minimum but there're times where the team itself really wants to keep discussing. We'll sometimes cheer if the team looks up for it but that's dependent on the team. I've seen long 2 hour standups with teams next to mine and everyone looks horrified. They end up getting stools, stand around their white board, and begin discussing the product merits of their solution. This was a team populated by 2 devs, 2 BAs, a product manager, designer, and a senior director. This was all run by a lean coach from a large agile consulting company who are "thought leaders" and whose name follows closely with that type of leader. It was the worst thing I have ever seen in terms of standups.
|
|
#
¿
Aug 17, 2016 23:02
|
|
|
OWLS! posted:If you hadn't said "teams" I would have thought you were my boss. I'm wondering - is this a good thing or bad thing since I try to be a minimalist in terms of meetings?
|
|
#
¿
Aug 29, 2016 18:38
|
|
|
TheresaJayne posted:The meetings we have we do this, but then the people needing to talk never do. That's really up to the person running the meeting to make sure they do talk. If they don't, they hear about it the next day (or after lunch). We generally try to have these followups right after the standup for the people who need them.
|
|
#
¿
Sep 13, 2016 23:52
|
|
|
We've stopped doing whole project estimations because kicking off a project used to take 2-3 weeks. We've tried to nail it down to a completely dedicated one week treatment where no dev work is done or a 2-3 hour sprint where only relevant project work is estimated. At this point though I'm more of the opinion that most stories more or less are the same size. If you find a large one after discussions, breaking that down is what takes the bulk of any planning meetings. Everything else is just wasteful.
|
|
#
¿
Dec 5, 2016 22:19
|
|