The Scrum meeting is executed daily, usually performed as a stand-up meeting.
Equivalent terms are daily scrum or simply standup. Participants include all scrum team members, such as product owner, Scrum Master and development team. It serves the purpose to share an individual’s progress of work and an estimation of the level of completeness until the next Scrum meeting. Any obstacles that detain the sprint goal should be expressed.
To confine any deviation it is significant for the Scrum Master to time-box the meeting and moderate arising issues appropriately.
A team can elevate its dynamic by introducing the Scrum ball, an item that is being tossed around for everybody’s turn to speak.
Scrum meetings require everyone involved in the product’s development to attend. This includes the development team, the scrum master and the product owner. Stakeholders and other parties outside of the development process need not attend scrum meetings — unless they want to (and the rest of the team is happy to have them there!)
There are some scrum meeting types that slightly differ from this requirement. For example, when answering who attends a daily scrum meeting, you might want to let the product owner off the hook.
There are 5 different types of scrum meetings. Each type serves a specific purpose and therefore should be held at specific points during development.
The 5 types of scrum meetings are:
Sprint Planning Meeting - This is the first scrum meeting held during a project. The entire team will get together to develop realistic goals, build and prioritize the product backlog.
Daily Scrum Meeting - Held at the beginning of each day, this meeting serves as a progress update to ensure the team is still on track.
Sprint Review Meeting - At the end of each sprint, the team will demonstrate the current product iteration and discuss what has been achieved during the sprint.
Sprint Retrospective Meeting - Not to be confused with the sprint review, the retrospective meeting covers not only the work that has been done, but also how the work was performed. The intention is to identify what went wrong, what went right, and what can be improved.
Backlog Refinement Meeting - This meeting is the Grand Prix of agile prioritization. Backlog items are categorized and prioritized after technical discussions about deliverables and their requirements.
You need to get as much information out as you can in a small amount of time during the daily scrum meeting. With that in mind, it’s always worth going into it with some form of agile scrum meeting agenda or template. This could be as simple as having a list of three questions that need answering during the meeting, such as:
What did you do yesterday?
What will you do today?
Is there anything getting in the way of your work?
These simple questions will help streamline the daily stand-up meeting so only topics of importance are discussed.
For any agile team to be effective, they all need to be aligned with the vision for the project and business. They also need to be actively aware of what others on the team are doing at any one time to ensure high productivity, seamless collaboration, and a smooth development process.
Scrum meetings provide the team with an opportunity to realign and assess how well the project is running. During these meetings, any opportunities to improve, any reasons the team needs to pivot, and any issues that need fixing can be raised, allowing the team to open up meaningful discussions.
Agile and scrum teams who hold regular scrum meetings often produce higher quality products with less risk, increased transparency, while still being flexible enough to pivot when the project requires. Thanks to the streamlined and optimized processes, businesses also see a reduction in costs, time and resources, which contribute to a faster ROI.