Scrum meetings are short and focus on the backlog of project management jobs or directly related worries. Whether you are a Scrum Master, a product owner, or part of a development team, following these key do’s and don’ts can help create an optimal environment for scrum meeting success.
Scrum comes from software development, where it is a portion of agile methodology. It’s designed for small teams who are working in what’s called “sprints,” short periods of no longer than 30 days and usually only two weeks. They track their progress by having short meetings.
Those brief, daily exchanges are typically only 15-minutes long and are called “standup meetings,” “daily scrums” or, for our determinations, a scrum meeting. They’re sometimes called stand up meetings because team members are usually standing up during them, which is a great technique for keeping the meetings short. It’s all about effectiveness when it comes to a scrum meeting.
Suggested Read: Scrum master and scrum project management
But are there other ways to get the most out of your scrum meeting further standing up? If you’re in charge of running a scrum meeting, you’ll poverty to keep it short, get an appointment and when you break, have every role on the scrum team what they want to do next. Let’s take a sprint around the subject, and get original on some ways to run an excessive scrum meeting.
How to run a productive scrum meeting
- Identify and invite the relevant attendees to each meeting to avoid wasting time and frustration. All attendees must add valuable input or be directly involved in the tasks at hand.
- Send out a firm agenda before each meeting so everyone is prepared to be focused and productive.
- Request that all attendees come prepared to discuss these three points (as applicable):
- The status of tasks.
- The tasks they will be working on next.
- Any anticipated obstacles.
Stick closely to the timeline and structure set out in the agenda to allow sufficient time to cover essential tasks and issues. Avoid adding anything to the agenda unless it’s vital to the work.
Create a comfortable, non-judgemental atmosphere that encourages all attendees to share their thoughts and experiences.
Listen carefully to others when they speak instead of focusing only on what you came prepared to discuss. Sometimes what others are saying might help you understand your next steps better or resolve your concerns.
Strive to be concise to allow everyone who needs to speak adequate time to do so. Scrum meetings should be short and highly productive. Allocate time for each person to talk and adjust as necessary.
Also Read: Scrum leaders to build teams
Scrum meetings: What not to do
Discuss tasks or topics that are not relevant to the current meeting or its attendees. This will cause disinterest and end in everyone feeling frustrated.
Allow the meeting to become a complaints session where people ramble on about personal gripes that impact progress.
Jump randomly from topic to topic. Stay organized to reduce the chance of missing valuable information or issues that are time-sensitive.
Just address the commanding figures such as the Scrum Master or Product Manager. Be fully inclusive—the success of a project relies on input from everyone.
Assume everybody understands or remembers how everyone’s responsibilities relate to each other. Use a scrum board to path tasks and equal them to the larger goals.
Move tasks or change a task’s status without ensuring that all of the relevant participants have seen the changes.
Defer to other meetings that may have an impact on a task that needs to be covered in the regular scrum meetings; instead, it is better to postpone a scrum meeting to ensure all pertinent information is available before the session.
Also Read: Job profile of a scrum product owner
Although these are not the only do’s and don’ts for scrum meetings, keeping these items in mind will go a long way toward making your scrum meetings productive and successful.