Ceremonies in Scrum Framework

Sprint Planning Meeting:
The Sprint Planning meeting cam challenging for new team. There is sure to be lots of questions from people, and perhaps indecision about what to expect or is expected, especially at the beginning of the meeting. Therefore it is important to deliver the meeting with opinion and sureness, but also get out of it what you need in order to set the team up for a great sprint. Write out the agenda of Sprint on which team is going to work. Dealing with all type of planning for upcoming sprint e.g. Resources, Hardware anything else team needed. Clarify story points in terms of complexity, and announce planning poker. Discuss the next sprint stories one by one Go through the stories and assign tasks to team members. Go back to the story points and ask whether the team feel their original estimates are still accurate and Promise for sprint goal(s).

Daily Scrum Meeting:
Every day at the same time and place may be in company premises, the Scrum Development Team members spend of 15o20 minutes reporting to each other. Each team member summarizes what he did the previous day, what he will do today, and what impediments he faces. The daily scrum meeting is not used as a problem-solving or issue resolution meeting. Issues that are raised are taken offline and usually dealt with by the relevant subgroup immediately after the meeting. During the daily scrum, each team member answers the following three questions:
What did you do yesterday?
What will you do today?
Are there any impediments in your way?

Note:
One thing keeps in mind! The SM is not the center of the Daily Scrum, the Dev. Team is! The Daily Scrum Meeting is an event for the Development Team to synch activities and create a plan for the day. The Scrum Master needs to make sure that the Development Team has the Daily Meeting, but the Development Team is responsible for conducting the Daily Scrum.

Sprint Review Meeting:

Each sprint lead to two-part sprint review meeting. It starts with a customer review and demonstration and ends with the team retrospective. Both of these components occur on the last day of the every sprint. The duration of the meetings vary and depends on last ended sprint. For Example if your sprint based on one week duration, apply one hour of meeting time for the customer review. But if it is based on two weeks Sprint would result in a two hour review. Moreover, the team should spend no more than one hour preparing for the review. The purpose of the demo is to produce a discussion between the Team and the stakeholders about how to make the product better. The Product Owner incorporates the lessons learned during the conversation into the Product Backlog, completing yet another inspect and adapt cycle. The meeting itself should be strictly time boxed to no more than an hour per week of Sprint. (So a two-week Sprint would have a two-hour review and a one-week sprint a one-hour review.) Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture
Informal 2-hour prep time rule and it may without power point slides and Whole team participates.

Retrospective Meeting:

The sprint retrospective is a meeting facilitated by the Scrum Master at which the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive. The sprint review looks at what the team is building, whereas the retrospective looks at how they are building it. The retrospective includes three main questions/points for discussion:

What we have to send in quality manner in last Sprint?
What we have to send with Bad quality in last Sprint?
How we could to improve lagging Point?

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *