Comment pouvez-vous bénéficier des stand-ups quotidiens?

I my experience shifting to keeping the sprint Goal in focus is key! Focus on the outcome! What do we want the board to look like tomorrow? What is going to stop us from doing that? The Daily Scrum is a planning meeting after all. Whoever is facilitating that daily scrum should do prep work. Items aging has it been in a state a long time. Are the team members multitasking. Having some of this info can help steer the conversation if it’s heading in the direction something unattainable.

I like the standup because of the visibility it gives to all the members of the team on how a team is progressing towards the sprint goal. This fosters ownership from individuals and is a great step towards collaboration, any learnings or mitigating blockers. This also is a platform(provided that 15 mins can be extended) to do team bonding, well not saying it must be a part of stand up but an extension of standup as this is the place where the team meets for the first time in the day.

I also find daily stand ups helpful to resolve any blockers both within and outside the teams. It is also a good opportunity to discuss challenges that team might be facing and coming up with alternate solutions.

Daily standup is a personal commit to the development I believe in those three questions and the scrum master should make sure we focus on those instead of deviating discussion....What are stumbling blocks is a question which may elongate . And would like to add one more What is it that you can offer to bring to the table to reduce the age of any lingering issue ? I feel a motivated team will always try to understand the importance of daily standup and try to make it effective.

Remote product teams can benefit greatly from daily standups. These brief virtual meetings enhance communication, align objectives, and promote quick issue resolution. They foster accountability, efficient task management, and team cohesion. Real-time progress updates and iterative improvements further optimize workflow. In the remote work landscape, daily standups are a vital tool for maximizing productivity and team success.

One thing I've found helpful with daily stand-ups - In today's time of globally distributed team and (or) many preferring to work from home or any other remote locations, these meetings proved to be an amazing way for everyone to keep in contact and aligned with each other.

1) Enable stronger team alignment. 2) Identify and reduce roadblocks. 3) Strengthen team collaboration and communication. 4) Improve accountability and task tracking. 5) Increase focus on priorities and goals. 6) Better understand project progress and status.

Good stand-ups are Short - 15 minutes Concise - The team identify their tasks and highlights any needs to be taken offline by the identified or volunteered resource. Informative - keeps everyone up to date on all activities

My recommendation is to not use the three questions. Instead, talk about what do we need to do as a team to make sure we can keep moving forward. Daily Stand-Ups (or Scrums) are not just for Scrum teams. Kanban, XP, and other teams can also take advantage of these. A highly recommended practice is to use Work Item Age. What on our board is taking too long and how do we come together to get those items moving?

I like to run daily stand-ups by focusing on answering actionable questions instead of boring status reports. The questions are: 1 - "What can we finish today?": Prioritise task completion. 2 - "Is anyone doing something not listed here?": Identify hidden work, promoting transparency. 3 - "Can we pull any card?": Avoid delays. 4 - "What to tackle together?": Address bottlenecks. 5 - "Any urgent cards?": Keep priorities clear. 6 - "Any cards with impediments?": Don't remove blocked cards from the Kanban. 7 - "Do all cards have an owner?": Tasks should have someone responsible. 8 - "Is anyone holding too many tasks?": Evenly distribute the workload.

Remember, the three questions were never a part of scrum and yet continue to appear as recommendations as people see them as a way to work through the daily stand up. I don’t recommend teams use those questions. Instead, they should get focused on who this meeting is for. It’s for the team, by the team, to know if the team is going to make the teams’ commitments. It’s much less about the questions asked or how long it takes.

Time boxing the stand up to 15 minutes is often underrated. Sometimes daily scrum calls end up going all over the place with requirement clarifications and technical discussions happening as soon as someone calls out an impediment they are dealing with. The best scrum masters I have worked with have always intervened to gently remind the team to put a pin on that topic and arrange a meeting/call right after the daily scrum as it is outside the scope of the call, strictly speaking. This ensures that the call is not seen by all as a chore to get through everyday but rather as a quick connect to check progress towards the sprint goal as laid out in the Scrum guide.

It allows the following: 1. Maintain velocity 2. Discuss hurdles to eliminate 3. Effort and time management 4. Brings people face to face, so transparent and quick resolutions 5. And so on...

Totally agree.. If the discussion goes beyond 3 questions, my team introduced a parking lot, which resumes as soon as the stand up ends. Staying back is voluntary. It helps avoid distractions during the stand ups.

The Daily Scrum should be a team conversation about the work so they may evaluate progress toward the Sprint Goal, and adapt as necessary. An alternative is to walk the Scrum Board from right to left and discuss progress and blockers based on the work as shown rather than by person. If you must use the three questions (they are not officially part of Scrum), I suggest changing them to be focused on the Sprint Goal since that is the purpose of the Daily Scrum. Something like: 1. What have you done since we last met to help achieve the Sprint Goal? 2. What are you going to do before we next meet to help achieve the Sprint Goal? 3. What impediments or obstacles are you experiencing that are stopping you from achieving the Sprint Goal?

The best practices for daily stand-ups include: 1. Keep it brief: Limit the meeting to 15 minutes or less to maintain focus and engagement. 2. Stick to the agenda: Share progress since the last stand-up, mention any blockers, and outline your plans for the day. 3. Include the right people: Invite team members directly involved in the project to ensure relevance and efficiency. 4. Stand up: Standing encourages brevity and helps keep the meeting on track. 5. Avoid problem-solving discussions: Use stand-ups to identify issues, but schedule separate meetings to address and resolve them. 6. Foster an open environment: Encourage team members to share updates and concerns openly.

In my experience, at least Software Development, is a team effort. And as the purpose of the daily stand-up is to inspect & adapt to reach the Sprint goal, we go over each item from right to left, asking only the following question: ❓: Are there any hurdles and do you need help (in overcoming them)? This keeps the focus on finishing and involves the whole team to get it done.

The most common one that I have seen is - getting into discussions in the middle of someone status. Once you master the art of politely moving that conversation to little later and give enough time after stand up to discuss those have really helped.

Avoid talking to the scrum master during the event. They are there to facilitate, but often times end up asking each person for a status update. The best Scrum Masters say nothing at daily scrum.

When the daily becomes centered on "what has kept you busy in the past 24h and what will keep you busy in the next 24h" rather than on managing the current work in progress and joining forces as a team to help take it over the finish line.

One of the biggest pitfalls I see is when the the meeting deteriorates from a planning meeting, which it ought to be, into a status meeting, which has limited value to anyone. It's about value delivered and planning, not status!

The most common pitfall, is the daily stand-up being a status meeting. The status of each item should be reflected on the Sprint board. The daily stand-up is meant as an exchange about how to reach the Sprint goal. Therefore, there are only two topics, that should be talked about: 1️⃣: Does one has done something, that influences the work of others? 2️⃣: Does one has a hurdle and needs help?

Its mostly when a standup turns into update. What was done, what will you do today kind of question. Secondly, when the flow of the calls goes into sharing mode, e.g. what was done in order to reach to xyz stage, this should be shared with the team but not in the stand up.

IMHO using flow metrics to drive daily stand-ups and talking objectively based on facts will make it more effective. Eg-Work item age. Look for items which are aging in your board and have conversations on those items on what is holding them. Suppose your SLE ( service level expectations is 7 days 85%) which means 85 % of times, items get competed in 7 days or less and we have an item which is already close to SLE then having discussion on this item couple enable flow Questions to ask? 1. Is this item big. Do we need to split it into smaller one? 2. Is this item dependent on some other team? 3. Is this item blocked? How can we unblock it ? Can we swarm or take action to resolve this? 4. Do we have right skills to take care of this item?

The retro meeting is a perfect place to discuss this and get feedback. I have tried asking explicit questions like how do you think stand ups are working, do you need any changes and have tried to experiment a few things before finalizing. It varies from team to team, you just need to find the right balance that works for your team. Introducing parking lot, and constantly reminding team members and stake holders to keep the daily stand up focus on the 3 questions and moving everything else to parking lot has helped my team immensely.

Agree with the team what the primary focus of the dailys is - is it improved communication flow? focus enhancement by readjusting to their goals? Take the time to define how to measure the outcome and do so, for example by introducing a "Health Check" style questionnaire for overall team health.

Daily standups can be useful and essential for triaging and managing priorities. Some team members may need alternate alignments to bring about a feature in the current sprint. Dependencies are highlighted and slacking is addressed with more skills added from other team members. Its also a place where a quick resolution can be achieved when multiple stakeholders are involved.

I have used a combination of zoom and slack. Deciding on the best time considering different geographical locations and time zones, setting up reminders on slack, and using the jira board to have a visual of tickets have helped.

Remember… it’s a planning meeting, not a status meeting. The team should be using this time to plan their work for the day and discuss progress on the sprint goal. If the team thinks this meeting doesn’t have value, they probably aren’t using it to plan.

SCRUM Team should clearly understand the purpose and the value of Daily Scrums and they should believe it really helps them to achieve their Sprint goals. Team should attend Daily scrums with prior preparation and should strictly follow timebox. Daily Scrums are not for 1. Status update 2. Technical discussions 3. Impediment solving 4. Just Moving tasks Daily Scrums are 1. Short plan 2. Identifying impediments 3. Prioritising tasks 4. Collaborating as a team

Well, if you are struggling with empowerment and decision making in your team, think about adding "Decision Daily" to your stand up: if a team member has to decide something on that day, they get to talk about it: what is it, how are they going to decide (e.g. themselves, an expert, ...) and do they want someone to support them there or are they comfortable with it. This increases transparency of decisions as well as the feeling of self-efficacy over the long run.