To win over a hesitant team during stand-ups, we should initially start by demonstrating agile's value through small, low-risk experiments that lead to quick wins. We can highlight how Agile can solve their existing challenges, like reducing long meetings or speeding up delivery. We can also create an open forum for them to express their concerns, and address them with empathy, offering factual responses. We may demonstrate how stand-ups streamline communication and keep the team aligned, emphasizing its benefits to their workflow. Also, the team may confuse standups with project status meetings, and we may help to clear their doubts. Gradually, their experiences with the positive impacts of agile will lead to greater buy-in and acceptance.

To address team's hesitance about a new methodology during stand-ups, encourage an open discussion. Invite team members to share their concerns and any past experiences that might shape their views, demonstrating that their opinions matter. Next, outline the benefits of the methodology, emphasizing how it can enhance collaboration, boost efficiency, and lead to better outcomes. Sharing success stories from other teams can also help persuade them. I’d suggest a trial period to implement the methodology on a small scale, allowing the team to experience its advantages without a full commitment. Continuous feedback during the trial will help team adapt the process , fostering trust and buy-in.

To win your team over, start by addressing their concerns directly. Often, teams resist Agile because they see it as just more meetings. Emphasize that the stand-up isn't for status updates but to identify roadblocks and get quick support. Keep the meeting short, ideally under 15 minutes, and focused on three things: what was done yesterday, what will be done today, and any impediments. A key point from my CSM training: make it a safe space where people feel comfortable voicing challenges without feeling judged. The more effective and concise it is, the more buy-in you'll get.

Rather than creating a realisation of what change the team is going through, agile can be directly implemented to the projects easily by having frequent discussions to have an efficient plan for project, break project into chunks. When the official terms come into picture I have seen team resisting the change. If the same concept is termed to them as change in approach of project management, they consider it as an organization level decision to accept it & move on.

To win them over, highlight the benefits of Agile, like improved collaboration and quicker problem-solving, and encourage open discussions about their concerns. Gradually introduce Agile practices, showcasing small wins to build confidence and trust in the process.