際際滷

際際滷Share a Scribd company logo

Armand catala daily scrumdrama

Armand Catal i Alcalde
Armand Catal i Alcalde

Based on the Ken Schwaber and Jeff Sutherland definition of Daily Scrum, in this document you will find some common gaps and how we can avoid it

1 of 2
Download to read offline
Daily Scrum Drama Probably the most well-known event when we talk about Scrum. The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. That is it! Nothing more, nothing less. Nevertheless, there are some many things going not really well during this 15-minute event. Sometimes, the meeting starts with a keynote from the Product Owner on a new requirement, which he just received or learned about. Then, explains it to the team and asks whether the team can drop one of the other requirements and pick up this new one or, even, if the team can assume this new requirement without any sprint impact. Once this discussion begins, no one gets the chance to share their updates, and the stand-up turns into a planning meeting. To discuss a new requirement, we should arrange a new meeting after the stand-up, include the development team and product owner to talk about the requirement, its priority The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain: - What did I do yesterday that helped the Development Team meet the Sprint Goal? - What will I do today to help the Development Team meet the Sprint Goal? - Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? The purpose of these three questions is to share the information that is relevant to inspect the sprint backlog and validate whether we as a team are still on the right track. Nothing more, nothing less. These three questions are not mandatory, even, the team can add more question or use different ones as long as useful to manage the Sprint. For example, we can track the blocking issues, keep in mind the dependences Often it is the Product Owner or Scrum Master, to whom the team answers what the team has been doing and what they are going to do the upcoming day. All the other team members were either looking at their cell phones or watching the team member who was talking to the Scrum Master. Strange! Especially for these roles, because none of whom have an active role during a Daily Scrum. It is up to the Scrum Master to learn the Development Team how to do this. If there should be re-planned, only then it is useful to involve Product Owner in the discussion (if the scope could be affected). In addition, during the explanation we might avoid to talk about the technical details of each task. The question is referred about is done,what not is done. But if anyone wants more details, he can plan a different meeting to talk about it, but he should not steal the time of the 15-minutehow time-box. The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. What the teams usually do, in addition to treating the 3 questions of the Holy Grail for the status update is to individually inspect work instead of the feature that the team is trying to deliver. During the Daily Scrum each team member is concerned only for his own task and they do not really care about what is done by the rest of the team members, because they dont understand which is the aim of each task neither how it could be addressed. This means less interesting discussions during a Daily Scrum, because they are concerned with individual focus. Also it is easier for the team not to be transparent about the work contributed to the Sprint Goal. At the end, the team accept to lose 15 minutes every day and then, each member can start their work. But, by simply adapting the way we present information in such a way to provoke a different discussion. The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or re plan, the rest of the Sprints work. After everyone has answered these three questions, is the team ends the Daily Scrum. Sorry but, nothing could be further from the reality: Actually, has just started! It is not about answering the three questions. It is what you will do with the shared information. If there is nothing special to report, changed or we need to unblock any situation then a Daily Scrum is done in just a few minutes, if not, before ending the Daily Scrum all
the new tasks to manage the found changes should be assigned. The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. During the Daily Scrum the Scrum Master should have not an active role. If the Scrum Master acts as moderator, word shift coordinator or such tickets mover, he is not working as a Scrum Master, he is working as a Secretary. The team can organize those things by themselves. The Scrum Master have to teach the team to understand the purpose of the Daily Scrum (inspect if rescheduling is necessary) and how they can do this no more than 15 minutes. The Scrum Master should have a cup of coffee in his hands and should let the team organize themselves in these 15 minutes keeping busy with those things that they are saying (or not said). Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Teams level of knowledge. This is a key inspect and adapt meeting.

More Related Content

Armand catala daily scrumdrama

  • 1. Daily Scrum Drama Probably the most well-known event when we talk about Scrum. The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. That is it! Nothing more, nothing less. Nevertheless, there are some many things going not really well during this 15-minute event. Sometimes, the meeting starts with a keynote from the Product Owner on a new requirement, which he just received or learned about. Then, explains it to the team and asks whether the team can drop one of the other requirements and pick up this new one or, even, if the team can assume this new requirement without any sprint impact. Once this discussion begins, no one gets the chance to share their updates, and the stand-up turns into a planning meeting. To discuss a new requirement, we should arrange a new meeting after the stand-up, include the development team and product owner to talk about the requirement, its priority The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain: - What did I do yesterday that helped the Development Team meet the Sprint Goal? - What will I do today to help the Development Team meet the Sprint Goal? - Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? The purpose of these three questions is to share the information that is relevant to inspect the sprint backlog and validate whether we as a team are still on the right track. Nothing more, nothing less. These three questions are not mandatory, even, the team can add more question or use different ones as long as useful to manage the Sprint. For example, we can track the blocking issues, keep in mind the dependences Often it is the Product Owner or Scrum Master, to whom the team answers what the team has been doing and what they are going to do the upcoming day. All the other team members were either looking at their cell phones or watching the team member who was talking to the Scrum Master. Strange! Especially for these roles, because none of whom have an active role during a Daily Scrum. It is up to the Scrum Master to learn the Development Team how to do this. If there should be re-planned, only then it is useful to involve Product Owner in the discussion (if the scope could be affected). In addition, during the explanation we might avoid to talk about the technical details of each task. The question is referred about is done,what not is done. But if anyone wants more details, he can plan a different meeting to talk about it, but he should not steal the time of the 15-minutehow time-box. The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. What the teams usually do, in addition to treating the 3 questions of the Holy Grail for the status update is to individually inspect work instead of the feature that the team is trying to deliver. During the Daily Scrum each team member is concerned only for his own task and they do not really care about what is done by the rest of the team members, because they dont understand which is the aim of each task neither how it could be addressed. This means less interesting discussions during a Daily Scrum, because they are concerned with individual focus. Also it is easier for the team not to be transparent about the work contributed to the Sprint Goal. At the end, the team accept to lose 15 minutes every day and then, each member can start their work. But, by simply adapting the way we present information in such a way to provoke a different discussion. The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or re plan, the rest of the Sprints work. After everyone has answered these three questions, is the team ends the Daily Scrum. Sorry but, nothing could be further from the reality: Actually, has just started! It is not about answering the three questions. It is what you will do with the shared information. If there is nothing special to report, changed or we need to unblock any situation then a Daily Scrum is done in just a few minutes, if not, before ending the Daily Scrum all
  • 2. the new tasks to manage the found changes should be assigned. The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. During the Daily Scrum the Scrum Master should have not an active role. If the Scrum Master acts as moderator, word shift coordinator or such tickets mover, he is not working as a Scrum Master, he is working as a Secretary. The team can organize those things by themselves. The Scrum Master have to teach the team to understand the purpose of the Daily Scrum (inspect if rescheduling is necessary) and how they can do this no more than 15 minutes. The Scrum Master should have a cup of coffee in his hands and should let the team organize themselves in these 15 minutes keeping busy with those things that they are saying (or not said). Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Teams level of knowledge. This is a key inspect and adapt meeting.