Today we are going to talk about Scrum Ceremonies. These are set of meetings. We will learn about who is primary audience, what is the agenda of these meetings, and how short or long these meetings should be.
Planning meeting -
1) Attendees – It has to be attended by entire team including product owner, scrum master and the scrum team. Stakeholders and users are optional attendees.
2) Agenda – Product owner will describe the high priority features to the team. The team can ask as many questions as they want to understand the user story, so that they can translate into dev tasks and can create sprint out of it.
3) Duration - it should be time boxed to at 2 hours per week of sprint.
4) Prerequisite - Before this meeting, product owner has to have ordered product backlog, out of which scrum team can create their sprint backlog.
5) Outcome - At the end of the meeting, sprint backlog and spring goal has to be finalized. Also the it should clearly define the forecast of work in the sprint.
Daily Scrum meeting –
Objective – Objective of this meeting is to understand what everyone in the team is doing. Team has to answer only 3 questions what did they do yesterday, what’s their plan for today and are there any blockers for them.
Attendees – scrum team. Scrum master can facilitate this meeting, but this meeting is mainly for developer team only.
Duration – it has to be very short meeting, around 10-15 mins. This is the reason that it should be stand up call so that everyone covers it quickly.
Sprint Review –
Objective – At the end of every sprint, there has to be coded, tested and usable software available for client. The objective of sprint review meeting is to showcase team’s accomplishment. In general it is more of a demo of new features. During the meeting product is assessed against the sprint goal determined during planning meeting.
Audience – This meeting is attended by all members and can be attended by product customers and management as well. The developers from other products can also attend this meeting.
Sprint Retrospective –
Objective – Main objective of meeting is to evaluate how we as team are doing and what are improvement areas. Identify areas for - a) What should we start doing? b) what should we stop doing? C) what should we continue doing? The ideas are taken from everyone and are voted in the last to conclude the modified practices.
Attendees – Entire team, scrum master. Scrum master will facilitate this meeting and go around the table to ask people their ideas.
Duration – This meeting can be an hour long, as this is more of self-evaluation. Sometimes it can take longer as well, because there can be some conflicts which requires more brainstorming.
Planning meeting -
1) Attendees – It has to be attended by entire team including product owner, scrum master and the scrum team. Stakeholders and users are optional attendees.
2) Agenda – Product owner will describe the high priority features to the team. The team can ask as many questions as they want to understand the user story, so that they can translate into dev tasks and can create sprint out of it.
3) Duration - it should be time boxed to at 2 hours per week of sprint.
4) Prerequisite - Before this meeting, product owner has to have ordered product backlog, out of which scrum team can create their sprint backlog.
5) Outcome - At the end of the meeting, sprint backlog and spring goal has to be finalized. Also the it should clearly define the forecast of work in the sprint.
Daily Scrum meeting –
Objective – Objective of this meeting is to understand what everyone in the team is doing. Team has to answer only 3 questions what did they do yesterday, what’s their plan for today and are there any blockers for them.
Attendees – scrum team. Scrum master can facilitate this meeting, but this meeting is mainly for developer team only.
Duration – it has to be very short meeting, around 10-15 mins. This is the reason that it should be stand up call so that everyone covers it quickly.
Sprint Review –
Objective – At the end of every sprint, there has to be coded, tested and usable software available for client. The objective of sprint review meeting is to showcase team’s accomplishment. In general it is more of a demo of new features. During the meeting product is assessed against the sprint goal determined during planning meeting.
Audience – This meeting is attended by all members and can be attended by product customers and management as well. The developers from other products can also attend this meeting.
Sprint Retrospective –
Objective – Main objective of meeting is to evaluate how we as team are doing and what are improvement areas. Identify areas for - a) What should we start doing? b) what should we stop doing? C) what should we continue doing? The ideas are taken from everyone and are voted in the last to conclude the modified practices.
Attendees – Entire team, scrum master. Scrum master will facilitate this meeting and go around the table to ask people their ideas.
Duration – This meeting can be an hour long, as this is more of self-evaluation. Sometimes it can take longer as well, because there can be some conflicts which requires more brainstorming.
No comments:
Post a Comment