45

The Daily Scrum is not an update-to-management meeting! From the Scrum Guide (emphasis mine): The Daily Scrum is a 15-minute time-boxed event for the Development Team [...] This optimizes team collaboration and performance [...] The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the ...


22

Product Owners Are Silent Observers in Daily Stand-Ups In the quoted description, the word participate has the connotation of "taking an active part." The Product Owner should attend, but should not participate. The daily stand-up is intended as a synchronization and coordination meeting, not a status meeting, and the Product Owner has no active role to ...


21

They seem to treat the daily standup as a reporting meeting for your PO. This is not what the daily standup is supposed to be. As a scrum master it's your job to clarify that the daily standup is for the team and the PO is a tolerated visitor at the meeting. His absence changes nothing. It's also your job to make sure that it actually is that way. It's ...


19

Coordination/Collaboration, Not Formal Task-Tracking While the Scrum Guide used to refer to the stand-up as a commitment meeting, it currently says: 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. The purpose of the daily Scrum is not to hold people accountable ...


17

If you ask this question, or even if you have troubles answering it, you are likely a victim of dark scrum. A daily scrum meeting, done right, has no micro-management. Terms have power, and dark scrum is one of these potentially important terms that I would like to see spread. Scrum was never made for this kind of micro-management, and its mis-use can have ...


16

TL;DR What is the best part of the day to have the Daily Scrum meetings, in the morning or afternoon? There cannot be a single, canonical answer to this question that will be true for all teams and all projects. However, there are certainly some common practices—but keep in mind that "common" doesn't necessarily mean "best." To clarify the trade-...


16

Hope some of these work for you and you start getting relief – and respect. I'll tell you my experience first and how I made the best of it, and then I have a game plan for you to do first thing tomorrow. TL;DR: Skip to the Last Section - Game Plan My Very Similar Situation: 5-Minutes in Stand-Up Hell My last company was amazing, I joined a small startup of ...


15

What the Stand-Up Meeting is For The Stand-Up Meeting (a.k.a. the daily scrum) is designed to accomplish two main things: Coordinate task dependencies within the team. Identify process or resource issues (blockers) that need to be addressed outside the stand-up meeting. Various scrum practices support these objectives. The individual practices are ...


15

In addition to Sarov's excellent answer, there is also the purpose of the meeting. The daily standup is not a management engagement. Neither the Scrum Master nor any other project or senior manager is doing any managing during the daily standup. I see this even stronger than Sarov does - not only is management not being reported to, there is also no flow ...


14

Why would you need to? The daily stand-up meeting should only take five to fifteen minutes, depending on the size of the Scrum Team. If it is taking longer than that, then that's a separate issue you should probably be looking into. If it does only take five minutes, then are your developers really so hard-up for time in the day that the presence of a ...


13

One of the advantages of having such a small team is that, indeed, the people in the team are able to communicate freely throughout the day. A lot of the daily stand-ups might thus often end very quickly and may look like they are a waste, but they can still have a purpose even in a small team like this: to provide extra focus. The daily standup allows ...


12

TL; DR In Scrum, a time-boxed daily stand-up with a structured format is mandated by the framework. If you don't have a daily stand-up, you aren't following the core Scrum methodology. Kanban is less prescriptive, and doesn't actually mandate the daily stand-up as a formal ceremony. However, Kanban teams often borrow the practice from Scrum for the same ...


11

Briefly: No, Daily Scrum with Three Questions is not a sign of team immaturity. Yes, Daily Scrum with Three Questions is valuable, even if you with your team want to switch to Extreme Programming. Verbosely: No, Daily Scrum with Three Questions is not a sign of team immaturity. In reality, I don't understand, why Daily Scrum with Three Questions should ...


11

The stand-up in Scrum has a distinct purpose. As do the other meetings defined by Scrum. There is no overlap between their purposes, so having another meeting is not a good reason to cancel the stand-up. What could be a good idea though is to have both meeting directly following each other. In other words: shift the time of the stand-up to immediately ...


11

Just because you have 150 story points in your backlog now does not mean that work captures the work necessary from your stakeholders' perspectives. Every iteration, you should be evaluating what has been done and what remains, adjusting what remains. You may add work, remove work, or determine that there's no work left to do that's the cost of another ...


10

You can attend and listen in the Daily Scrum but not speak From the Scrum Guide - The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. From Mike Cohn's blog on the Daily Scrum Meeting - ...many teams enforce a rule in which only those who are committed are allowed to talk during the daily scrum meeting. All ...


9

I'm going to give a slightly different answer to Sergey because I don't think this is a simple question with one right answer, but I'd like to also note that I up-voted his answer because I agree with him too. The goal of the daily scrum is for the team to reset with each other on where things stand currently and what the immediate plan is over the next day....


9

The main problem is that your "Daily Scrum" degraded to "Daily Status Reporting Meeting". I believe, that reason of this problem is that your team doesn't understand purpose and goals of Daily Scrum. And, of course, if we will dig deeply, main reason will be that you (as Scrum Master) didn't explaine well purpose and goals of Daily Scrum to your team. There ...


9

Your team has opted a good way for the Technical discussions. Following few points should be kept in mind during the discussion and should be monitored: Discussion is not repetitive All the necessary team members are involved in respective discussion Members should come out with a conclusion after the discussion. If this is not the case with the members ...


9

I am a huge fan of daily stand-ups, but there are some disadvantages: Team members can sometimes wait until the stand-up to communicate important information rather than telling the team immediately. The stand-up can be seen as a replacement for in-sprint planning. The timing of stand-ups can be an area of dispute. This is particularly true if your team has ...


9

There are two parts to the Scrum Master role: Helping the team to resolve impediments Ensuring that Scrum is being followed The second part often gets neglected, but it is very important. If the team does not see value from the Scrum approach they will quickly stop following it. The Scrum Master should coach the team to ensure they understand why it has ...


9

Isn't that all against the idea of a self-organized team? Yes and no. Since the 'team leader' is a member of the Team, his opinion should be taken into account. If any team member's opinion is ignored during organization, then that's a strong smell that there's something wrong with the whole 'self-organizing' situation. One thing you and he need to take ...


9

You have neglected to say whether your team are face to face or working distributed and communicating via Lync etc so for the sake of this answer I will assume distributed. Stage 1: Basic Discipline Take a hard line with the Product Owner and tell him that you will facilitate the session and ensure that it is productive. Sharing the duty is confusing to ...


8

Your team mates know that you have this condition, and it is painful to you to stand, so leave the team. It is a basic human behaviour not to harm each other, and clearly they do and cause you pain. If you cannot leave the team take a chair and sit. They don't care about you, and you should care about yourself. You don't really have a team there anyway. The ...


8

The reason for a "stand up" is to differentiate it from your normal meeting situation. To keep that non-normal atmosphere, you could get a bar stool and sit down on that during your stand-up. It will be sufficiently different from your normal sitting behavior to make a visible difference, but still be on eye level with the standing people. Hopefully it ...


8

Tracking the daily commitments each team member sounds like micro-management at its best. The exception would be for a very short project, or for a tiger-team trying to solve an emergency. When you track daily commitments, either the larger chunks are being ignored (woe to the project) or else they are being unnecessarily broken down into meaningless ...


8

Yes, you absolutely want your PO at the Daily Scrum. First off remember that the Scrum Guide is something like 17 pages and only covers the broadest brush strokes. The product owner is part of the team. They are the direct connection to the business and the person who signs off on stories as done. You absolutely want the PO there so they know what's ...


8

If the information is useful to the entire team, the discussion isn't stopping the standup from completing within the timebox, and the standup is achieving its purpose to inspect progress toward the goals and plan the day, there isn't a problem with discussions in a standup. Ultimately, everyone should continue to get better and providing relevant ...


8

Things wrong with this picture: Scrum doesn't have a "development manager". This sounds like a company who's unwilling to let go of the past. Admittedly this can be a difficult and long process. So this role might be a concession that was necessary to get scrum off the ground in the first place. But the role shouldn't be needed. (Maybe that's the reason for ...


8

It's important to recognize that Scrum does not say that a team must be between 3 and 9 individuals. The Scrum Guide says that Scrum is most effective with a Development Team size of between 3 and 9 people. A Scrum Team (including the Product Owner and Scrum Master) would have an ideal size of 4-11. Development Teams that are smaller than 3 people or larger ...


Only top voted, non community-wiki answers of a minimum length are eligible