Communication and project management are two essential elements of successful project management. Meetings are essential for project management, no matter whether you’re running an agile or waterfall project. Although we have covered the scrum framework in other posts, we didn’t discuss the different types of scrum meetings or their purpose. Depending on your team’s styles and preferences, these meetings can assume different timelines and forms, but they all include the same scrum methodology.Different types of scrum meetings
Sprint planning meeting
Sprint planning begins with the product owner explaining their vision and how they expect team members to complete the project stage. Teams also decide how much work they will complete in a sprint. This meeting occurs when teams move from the product backlog to the sprint backlog. This step is time-consuming and requires a lot planning.
We move on to daily scrums and execution, starting with planning meetings. Each day, team members meet for approximately 15 minutes to discuss any issues and share progress. It’s a short meeting but it’s still important to the scrum process. Daily scrum meetings are intended to keep all team members on a single page and to unite them into a cohesive, functional unit. These meetings are attended by the scrum master. Sprint review meeting
Sprint reviews are intended to show what has been accomplished so far. Sprint retrospective meeting
This meeting is where team members can freely and openly discuss their organizational concerns and teamwork. The meeting should be neutral, non-judgmental and friendly. This is an important part of the team-building and development process. Future scrum projects will depend on this meeting. Backlog refinement meeting
Last but not the least, we have a backlog refinement session where teams focus on the skills and quality work that was involved in the sprints. This meeting is where the product owner will meet with the development team to discuss the final product.
Scrum meetings are intended to help teams evaluate their progress towards their sprint goals. They will also assess risks and make adjustments to meet sprint commitments. All team members must attend scrum meetings. They will assess any risks and make necessary adjustments to meet sprint commitments. If a team member raises a concern, encourage others to help. However, this should be done after the meeting.
Sprint review and retrospectives serve completely different purposes. Let’s look at some differences between sprint retrospective and sprint review. You will notice that both meetings include nearly all participants. Sprint retrospectives are conducted by a scrum team with no input from others. The next difference is the delivery of deliverables. Both meetings are held at end of each sprint. However, the outputs can be quite different. Sprint review output includes updating the product backlog with high priority user stories for the development group. And, finally, we have our goals. The sprint review output is the summary of the sprint.
