@Avi thanks for the feedback.

source: Nano Banana

@Avi thanks for the feedback.

- re: "leave the meeting if you have nothing to contribute" - I'd hope that before someone leaves they take the opportunity to steer the conversation in a more useful direction.

No because people realize they have nothing to contribute. This is in cases, and I have witnessed them a lot that managers invite complete teams where just 1 or 2 member would be enough.

Time boxing, I do 5min and 5 times 2 if it does not get resolved we have to take a closer look at the issue and someone will be assigned to investigate it and get all pro/con. I also have an Improvements meeting. The goal of this meeting is to reduce back and forth discussions that go on in meetings. So at the improvements meeting team members present issues and at least two solutions. I know I can be a dick but don't complain, I don't want complainers in my teams. Have an issue then come up with two solutions at least. In that same meeting we will discuss the time boxed issue. The improvements meeting is every week and has an agenda. Every team member is aloud to add topics on the agenda and we handle them in FIFO.

I have been in the schedule another meeting after the daily ritual. This is what will happen. You have daily and 3 members have an issue. Now I have 3 extra unscheduled meetings after the daily. But the worst is that communication is not flowing because you have 1-1 meetings maybe 1-2 meetings. But now only those members are aware of the solution and the problem. When you discuss in daily everybody is there and aware of the issue and the solution. No "lost in translations" or "I forgot to mention it to the rest of the team" moments.

If you join my team its obligatory to check the ticket board before daily, it's a rule no discussion, And the same will happen people will ask questions or add comments.

Same goes for code reviews, we have the discussion in the PR not in some isolated meeting for three reasons.

- we keep history of the solutions and can check later on why we decided this

- everybody can add their input

- Juniors learn from the discussions

If there is a discussion in the PR it can be brought up in daily or it will become a topic on the Improvements meeting agenda

If something was done wrong we add it to the comments of the ticket or the PR. The truth is in the ticket comments or the PR comments to have history. It's al nice to discuss verbally but then there is no track of what has been said or the solution picked.

In my teams everyone can be criticized or pointed out for doing things wrong in a civil manner, Because this is how people learn. I have been criticized by juniors or pointed at mistakes I make or mistakes I missed from others.

We are all human, I ask 3 things from my team members:

- Have drive and enthusiasm for the job

- Want to learn

- Handle change

With these 3 skills you can be taught whatever is needed to get the job done