This experience is based on the practice summary of two small and medium-sized projects (one 2000 Manday, one 1500 Manday) in the past two years, and I hope to discuss and make progress with you.
- Discussion content
> What did I do
today > What problems did I encounter today and need your help
> What do I have to share with you today > What
to do tomorrow
- Insist on opening every day
- No more than 15-30 minutes per meeting
- Facilitate the team Communication, Collaboration and Engagement
- Knowing the Project Status, Doing the Right Thing and Doing the Right
Thing What are you going to do tomorrow".
We don't really want to use the precious time of the morning for this meeting, let's let everyone do more work while everyone is more awake
, so we schedule the meeting at 4:30 pm, so that everyone at 4:45 or Come back to your seat at 5:00 to do some cleanup or further discussions around what was mentioned in the meeting.
Daily Meeting is actually a good management tool .
(1) It can help track the task status and update it daily.
(2) Find problems in the project in a timely manner and work together to solve them.
(3) Control the direction of the team. Once there is a deviation, correct it in time. Started low-priority tasks, used the wrong method, etc.
(4) Promote team communication and knowledge sharing. So, our Daily Meeting also added a fourth item "What do I have to share with you today" .
Taking it a step further than the above mentioned, I think Daily Meeting is also a good platform for teams to fulfill "social needs" (check out Maslow's Hierarchy of Needs if interested). Imagine if the team can communicate with other team members in a good atmosphere every day, share useful knowledge with team members every day, and get help from team members every day, how wonderful it is. It can be said that a harmonious family is nothing but this. Such a team would be a very effective team.
For example, an agile team will have the following scenarios in their usual communication or Daily Meeting.
quote
Programmer A: I don't know how to do it. Today, saving Chinese characters to the database always shows garbled characters.
Programmer B: This is easy, I already have a way to convert the encoding.
Leader programmer: Great, you come down and talk in detail.
Programmer B: This is easy, I already have a way to convert the encoding.
Leader programmer: Great, you come down and talk in detail.
quote
Programmer A: Hey, Programmer B, the output of my module has been changed from NUMBER(18,2) to NUMBER(18,5), have you noticed this change?
Programmer B: It’s over, I just noticed that the data type you output has not changed, but I didn’t expect the accuracy to change, thank you so much.
Programmer B: It’s over, I just noticed that the data type you output has not changed, but I didn’t expect the accuracy to change, thank you so much.
quote
Programmer A: Hey, Programmers, I wrote a very common calculation method today, is it useful for you?
Programmer B: Great, I'm going to write a similar method tomorrow. Let's study it and see if it can be shared.
Leader Programmer: Programmer A, can you write an email and introduce your method to everyone?
Programmer A: Sure.
Programmer B: Great, I'm going to write a similar method tomorrow. Let's study it and see if it can be shared.
Leader Programmer: Programmer A, can you write an email and introduce your method to everyone?
Programmer A: Sure.
Of course, there are some caveats to be aware of .
(1) Since this is a daily meeting, detailed discussions of topics that are only relevant to a small group of team members need to be avoided. Otherwise, team members will feel it is a waste of time and boycott the meeting.
(2) This meeting needs to avoid being too serious, and should create a relaxed and harmonious atmosphere, encouraging all team members to actively participate and respond.
(3) Try to open on time and leave on time.