Communications

The best approach to dealing with a scrum team that is struggling with their daily standup is to 'Coach the scrum team on the objectives and structure of the daily standup, focusing on the 3 key questions'. The purpose of a daily standup is to synchronize the work of team members by answering three key questions: What did you do yesterday? What will you do today? Are there any impediments in your way? Coherent and focused sharing will help reduce the time spent and ensure everyone gets a turn. On the other hand, 'Skipping the daily standup occasionally to save time' does not solve the issue. The standup is a crucial part of Scrum to ensure everyone is aligned and up-to-date with the team's progress and any roadblocks. 'Increasing the time limit of the standup meeting' also doesn't address the root of the problem. The idea of a 15-minute timebox is to encourage succinct and relevant communication. Finally, 'Excluding team members who are not currently working on major tasks from the standup' is not consistent with the principles of scrum, which emphasizes team collaboration and collective ownership of the project, regardless of the size or importance of individual tasks

Let's carefully consider each possible response step by step. The first answer suggests introducing a facilitation technique or game that fosters constructive criticism and feedback. This approach is suitable because it encourages more effective communication, reduces the likelihood of personal attacks, and transforms criticism into opportunities for learning and improvement, as commended by the PMI Agile Certified Practitioner course. The second option of filing complaints in writing, instead of discussing them, can lead to misunderstandings and doesn't encourage open communication, which is a cornerstone of Agile methodology. The third answer, 'Only allow positive feedback', is not a good practice as it may cause problems to be overlooked and miss opportunities for improvement. Lastly, skipping the retrospective to avoid conflict, negates the purpose of a retrospective, which is to explore what worked well, what could be improved, and how. Therefore, the best answer is to introduce a technique or game that encourages constructive feedback.

The Agile approach recommends welcoming changing requirements, even late in development, if it benefits the customer. So, 'Incorporate the change if it does not disrupt the sprint goal and potentially extend the sprint, and provide updates through Sprint Reviews' would be the best approach to handle this situation. The updates can be provided through routine Sprint Reviews, thus negating the need for daily individual updates. The other answers are less suitable because Agile is flexible and customer-centric, ignoring the request or stopping the sprint would not be the best practices. The stakeholder's request should be respectfully considered and discussed within the team, then proceed based on the team's consensus for the benefit of the end product and customer satisfaction.