Keep reading to find out how!
Table of Contents
What are huddles or stand-up meetings
Bug and crash reporting tool for your mobile app.
To achieve this, all employees answer the following questions:
Once each team member has provided their answers, you’ll have a succinct yet clear overview of the project’s current status and, if necessary, will be able to re-distribute or re-organize responsibilities.
The ceremony has become hugely popular because it allows tasks to be reviewed easily and brings attention to issues before they escalate.
What are the benefits of huddles
Employees have the perfect opportunity to discuss issues, plan for the workday, and celebrate any milestones.
They save time
Although they’ll take 15 minutes out of your day, daily huddles save time in the long run. Since the meetings are so short, employees must share information quickly and efficiently.
Everything can be laid out in those initial 15 minutes.
They improve team communication
The daily huddle ensures those situations don’t happen and incite team communication every morning.
This Reddit user described the crux of the matter well:
During the daily huddle, your developers will be forced to speak up about their current status as they answer the three questions.
As they become more comfortable with one another, informal, natural communication will become more and more commonplace, even outside the daily huddle.
They are easy to set up
Daily huddles have one huge benefit over most meetings: you only have to organize them once.
They always happen at a constant, fixed time, and the only time you’ll need to juggle multiple schedules is with the initial setup.
Once you’ve figured out a time that works for everybody, you’re pretty much set!
Another feature that makes the daily huddle easy to set up is its timing.
They allow immediate problem-solving
If any issue should crop up on a Friday, you’d still learn about this issue 72 hours later at the latest (on Monday).
Because of these instantaneous updates, you can work on possible solutions immediately before things get out of hand.
This Reddit user provided a great example of quick problem-solving:
This type of efficient damage control is only manageable with constant updates from all team members.
How to structure huddle meetings
Discuss the previous day
If by any chance your employees didn’t finish something they should have, this is when you’ll find out.
One Reddit user described their own experience with this question:
Hearing how a project is progressing should inspire all meeting participants, and they should be encouraged to devote their own efforts to the project’s success.
Share priorities of the day
You can begin this conversation by asking another simple question: “What will you do today?”
With a daily update, everyone has unfiltered visibility into each other’s progress and can then easily adjust their workday if needed.
Ask for updates
No new developments must slip under your radar. Just imagine you haven’t heard about the latest UI/UX adjustments—you might revamp a perfectly working codebase through sheer ignorance of the newest business decision.
Encourage asking questions
To combat this, you can ask your team members to write their questions or concerns on cards before the actual huddle.
Here are some example question and concern cards:
Who should attend huddles
As soon as one member is absent, it’s impossible to achieve 100% transparency.
Obviously, you as the team lead should host the meeting, and everyone who directly reports to you should also attend.
However, given the meeting’s 15-minute timeframe, large teams might not have the most effective huddle.
The VP of Engineering could be the host in that huddle.
Take a look at the image below, it visualizes the concept well:
Although not a daily huddle, the organization still profited from this monthly senior-level huddle.
If you have the time, you’d do well to establish similar regular huddles on all organizational levels.
Challenges of huddles
By adhering to your pre-determined, timed plan, you can cut the meeting off when you notice topics taking too long or veering off on a tangent.
Another challenge with daily huddles is organizing teams that don’t start simultaneously. For example, what if half your team comes in at 10 am, and the other begins at 7 am?
Here’s a sample question below:
Despite the lack of an aligned meeting, you’re still provided with a clear picture of everyone’s status.
Daily huddles are an undeniable asset to your development team.
This short yet focused meeting is straightforward to set up yet often results in immediate problem-solving.
Furthermore, they’re a huge time saver and will improve your team’s communication.
When hosting the huddle, begin by discussing the previous day. Follow by focusing on the current day and asking for any project updates. Make sure you end with a round of questions.
Make the meeting mandatory for all your developers, and ensure they provide their input.
Whatever challenges you might face, stick with it—the advantages are worth the effort!