The daily standup is the most common. The attendees include the Development Team and Scrum Master, and the team uses this time to discuss their progress on a project and identify any hurdles. They share what they accomplished yesterday, what they plan to finish today, how it aligns with the sprint, and the issues they’re facing. These discussions help ensure that everything is going according to plan.
What is important thing is to focus on the reporting the plan / blocker. Even if there is blocker in your userstory, these items should be discussed in the different meeting such as tech huddle. By doing this, team members can understand the situation of other userstories as overview. If the topic is going to deep dive, anyone, especially Scrum master, should suggest the topic is off topic and make it on the other meeting.
Tech huddle
These are all nothing but quick discussions amongst the team members to talk about design approaches, resolve technical blockers etc. They can also be used to do group code reviews and code walkthroughs.
The different name is dev huddle, dev meeting, daily huddle.
Sprint Planning meetings
Think of the sprint planning as a whole-staff meeting for the project. The entire scrum team needs to be present so everyone is aware of the stakeholders, instructions, updates, and goals. During the meeting, the Product Owner presents the product sprint backlog. The latter can include feature improvements, bug fixes, and other updates. Once the team is presented with these items, they draft objectives or sprint goals. Once the goals are locked, the sprint begins.
A sprint review meeting occurs so the team can tackle output from their previous sprint. Along with the development team, product owner, and scrum master, stakeholders are also present. The team will showcase their work to receive feedback throughout the sprint. This helps agile teams track progress and share notes.
The sprint retrospective meeting occurs after the sprint review. It includes the agile team and is completed by the end of the sprint. In most scenarios, the Scrum Master leads this meeting to reflect on the product.
Backlog grooming is a regular session where backlog items are discussed, reviewed, and prioritized by product managers, product owners, and the rest of the team. The primary goal of backlog grooming is to keep the backlog up-to-date and ensure that backlog items are prepared for upcoming sprints. Backlog grooming, referred to also as backlog management, backlog refinement, pre-planning, or story time
Lean Coffee is a structured, but agenda-less meeting. Participants gather, build an agenda, and begin talking. Conversations are directed and productive because the agenda for the meeting was democratically generated.
