Why isn't the daily scrum considered to be micromanagement?

Under any other circumstances expecting to get a daily update from developers would be considered micromanagement. Maybe even pico-management. (did I just invent a term?)

Even a weekly update was considered borderline micromanagement by many.

What changed that the daily scrum is acceptable, both to the engineers and the Project Managers?

(Future question: can this change (if it exists) be used for more frequent updates in a non-scrum setup?)

  • 20
    The daily standup is a intra-team coordination meeting, not a status pull. pm.stackexchange.com/a/6657/4271
    – Todd A. Jacobs
    Commented Jan 2, 2019 at 16:57
  • The Dev Team maintains the burn-down chart, which can be used as a status update. In every case the (PO) has a lot of contact with the Dev Team during the Sprint and s/he is always updated by the Dev Team in the case of a problem. Thus, the Big Boss has to either check the burn-down chart or to ask the PO directly. Commented Jan 3, 2019 at 22:16

7 Answers 7


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 dire consequences for developers, projects and scrum itself (as a concept). If you can, consider using the term "dark scrum".

from the linked page(ronjeffries.com),

EDIT: I emphasize that below is a description of "dark scrum":

Every day, the team is supposed to get together and organize the day’s work. This practice, the “Daily Scrum”, is imposed on the typical team. There might be one person in the room, the ScrumMaster, who has been told how it should be done. The programmers haven’t been told. Quite often, even the Product Owner hasn’t been told. Almost certainly other power holders haven’t been told.

But the power holder already knows his job. His job is to stay on top of what everyone is doing, make sure they’re doing the right things, and redirect them if they’re not. How convenient that there’s a mandatory meeting where he can do that, every single day!

The result: instead of the team rallying around their joint mission and sorting out a good approach for the day, someone else drags information of of them, processes it in their head, and then tells everyone what to do. Since nothing ever goes quite as we expected yesterday morning, this improper activity often comes with a lot of blame-casting and tension.

Dark Scrum oppresses the team every day. Self-organization cannot emerge.

  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Todd A. Jacobs
    Commented Jan 8, 2019 at 16:24

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 Daily Scrum. [...] The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

If someone outside the Team is asking for progress reports or otherwise attempting to micromanage during the Daily Scrum, the Scrum Master should request for him/her to stop.

If the developers are automatically reporting to someone outside the Team during the meeting (you can tell this if they always face someone during the meeting) even without being asked, then that someone should be removed from the meeting to remove this temptation.

If the developers are automatically reporting to someone inside the Team during the meeting (such as the Scrum Master), then steps should be taken by the Scrum Master to discourage this. For example, the Scrum Master could make certain to move about the room during the meeting, to prevent the person speaking from being able to see him/her (and, thus, force the person speaking to shift his/her attention to the group at large).

  • 14
    Sadly, in my experience this is very unusual. The Project Manager or their manager is almost always serving as Scrum Master on projects I've been involved with.
    – catfood
    Commented Jan 2, 2019 at 19:19
  • 9
    Or sometimes the Scrum Master is in practice "standing in" for the management.
    – davidbak
    Commented Jan 2, 2019 at 21:54
  • @davidbak A fair point. I added a paragraph.
    – Sarov
    Commented Jan 2, 2019 at 22:19
  • 3
    I’m now imagining a scrum master playing hide-and-seek during stand-ups. Thanks for that! :) Commented Jan 3, 2019 at 23:07
  • 2
    @catfood Yes, most companies seem to be very keen on being "Agile", without actually trying to follow the guidelines. Needless to say, even the original paper on SCRUM for software development is very clear that under no circumstances should the scrum master be part of the management (among other things). Ideally, it's a dedicated role that does nothing else (on multiple teams if need be). It definitely isn't the product owner, the team leader, the project manager... the scrum master is there to guide the meetings (keep them on track) and be a cheerleader, he doesn't lead anything.
    – Luaan
    Commented Jan 4, 2019 at 14:48

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 from management towards the team. Nobody tells the team what to do or how to do it during the daily standup. There is no management activity going on during the daily standup and that is why it isn't micro-management - because it isn't management at all.

That doesn't mean this culture as-written is strictly put into practice in your environment, so your confusion might very well result from the practice being different from the book. If management has taken over the daily standup and is using it to micro-manage the team, then indeed the daily standup has become micro-management. If you continue to run it in that way, then yes you are engaging in micro-management. But it shouldn't be called the daily standup anymore.


Under any other circumstances expecting to get a daily update from developers would be considered micromanagement.

That's not true. I'm not even sure if we are defining micromanaging properly here as there are ways to micromanage without requiring a daily update from developers.

A Scrum standup is not for management. It's for developers and by developers. It's where developers get in sync and plan what to do next, who needs help and who can provide help.

It is meant to go quickly, a few minutes per developer to sync with the other developers and then call it quits. I've work in actual Scrum and Kanban teams doing real stand-ups, and those have been the most productive exercises in my 25 years in software.

Problem is, many people hijack the term 'standup' to conduct an actual 30 min or even hour-long meeting. Now, a 30-60 min daily meeting can be valid and useful in some organizations and contexts.

The problem here is two-fold:

  1. meetings that are not useful in proportion to their lengths of time and frequency,


  1. people taking those meetings and calling them "standup".

As Voltaire allegedly said once : "If you wish to converse with me, define your terms."Voltaire's quote


When the "stand-up" is properly orchestrated, it's a free exchange of ideas about each other's work. It's meant to enforce collaboration, not confrontation. Unless your manager is actively developing with you (they usually are) they should not be in the meeting.

Too many times have I worked on projects where people who worked across the isle from each other could have saved the other person 6 months' work.


I thought I will also add my 2 cents although Sarov gave an very good answer.

Under any other circumstances expecting to get a daily update from developers would be considered micromanagement.

The developers should not give feedback in the stand up as and update to Managers but rather give the team an update using the three stand up questions

  1. What tasks have you worked on since we last talked?

  2. What tasks are you planning to work on next?

  3. Is anything getting in the way of finishing the work as expected?


A NFL team mid game gets together to discuss plans for the next play. The players do not give plays individually but rather a player will say " What did he try the last play, What play he wants to try, and if there is any obstructions he ask if someone to help opening the field" - He did not give an micromanaged update but rather informed the team how he plans to reach the goal.

Rather giving "someone an update" look at the sprint board and inform the team what you are doing and keep within the timebox.


The daily scrum is not to be considered micromanagement because it does not target any individual.

Nobody feels threatened when everybody has to do it.

Furthermore it is more about getting more tasks to do then about reporting about yesterdays progressing - so no feel of microm.

  • 8
    Not sure I agree with your first two sentences. If the Big Boss(TM) is requesting status updates from the Team every day... that's still micro-management; s/he's just micro-managing the Team, rather than individuals.
    – Sarov
    Commented Jan 2, 2019 at 15:08
  • 5
    If you don't do anything with information, then what's the point of having that information in the first place...?
    – Sarov
    Commented Jan 2, 2019 at 20:45
  • 1
    "[I]t is more about getting more tasks to do then about reporting about yesterdays progressing[.]" What is your source for this? It does not seem to align with anything in the Scrum Guide.
    – Todd A. Jacobs
    Commented Jan 3, 2019 at 19:29
  • 1
    "Nobody feels threatened when everybody has to do it." Even if the whole class is playing dodgeball, the small nerdy kid that's getting picked on feels more threatened than the class bully. It's still management even if you do it in a group setting. Commented Jan 3, 2019 at 22:45
  • 1
    @Sarov It's about sharing information with other members of the team, not the management. Sadly, plenty of managers are way too scared to let go of the wheel, and end up messing everything up constantly, and then you have 30-minute long stand ups every day that are utter waste of time and just make everyone hostile to each other.
    – Luaan
    Commented Jan 4, 2019 at 14:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.