55

It's not that you aren't supposed to report status in the Daily Scrum. Instead, the purpose of the Daily Scrum is to enable the Developers on a Scrum Team to understand the current state of progress toward the Sprint Goal and adjust their plan to maximize the chance of the team achieving the Sprint Goal before the end of the Sprint. What the Daily Scrum ...


34

TLDR: You don't have a Scrum Master Repeat after me: The Daily Scrum is not an update-to-management meeting! Your Scrum Master(SM) is acting not as a SM, but as a manager. The problem is, the SM is not supposed to be a manager. Take a look at the described duties of the SM. Notice the complete lack of anything along the lines of 'track the progress of the ...


22

From the Scrum Guide: Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. All of the events are included in your Sprint timebox.


11

The SM's job is to make sure that the ceremonies happen, not to tell the developers how to conduct their meetings. Daily stand-ups are supposed to be run by and for the development team. While there are no absolute rights or wrongs in stand-ups, I do think it's a waste to use a whole-team meeting to report status. Status can be read from a Kanban board or ...


7

Slightly different statement of the above - I agree with the other answers, but will share a different perspective. If you are reporting status in a meeting of N people, then that status is of no value to N-2 people. most of the people in that meeting are being paid to stand around and act like mannequins. A close friend of mine uses his daily standup ...


4

The team should decide. The meeting belongs to the team. If the issue of starting off is a persistent problem during the sprint, then the SM should bring it up during the retro and facilitate the discussion to come to an agreement.


3

Anyone who has studied for any of the Scrum.org certifications knows the answer to this question because it frequently appears in the practice assessment [paraphrasing] Q. When does the next Sprint begin? A. Immediately after the current Sprint ends. Therefore the Sprint time-box encompasses all the other time-boxed events. The Daily Scrum occurs every day,...


3

The answer from Thomas Owens is correct. However, I would like to add that depending on the team organization, I think it's acceptable to do some of the ceremonies outside of the 2 weeks considered as being the sprint (or whatever length your sprint is). For example, I've encountered teams preferring to do the planification for sprint N on the last day of ...


3

I may have a slightly different take than the rest of the answers. The Scrum structure should be the tool to help reach goals faster. Effective planning, review, retro, and daily scrum should reduce the overall time spent in meetings and let teams pivot as needed to always be taking the best path forward. When the stress is high, that is when those events ...


3

Long term success gets neglected for short term success. A meeting like the retrospective takes time and nothing bad happens immediately if it is canceled. You need to make clear, that the Scrum ceremonies are in for the long run. You don't do them, the team wont grow and might even collect things technical debt along the way by missing out on ...


3

Other answers cover why the Daily Standup shouldn't be a status report to the Scrum Master, but there's a detail missing: If you need a Daily Standup for the team to know the status, then your information radiators (specifically your board that shows in-progress issues) are either not always up to date, not trusted by all team members to always be up to date,...


2

Career-oriented advice: It just doesn't matter. I would conform to the SM's request. I would de-escalate as much as possible. I would report it only as normal job duties require, and with a goal of just being truthful, nothing more. Concentrate on getting your part of the work done. If there is a 'roadblock' to your work outside your control, notify the ...


2

The Scrum Master should coach the team to be self-managing so that they decide and find a way of handling this themselves i.e. if they want to have a specific person, a specific scenario e.g. last joiner or they ask the Scrum Master to nominate someone every day, its totally up to the team. If the team repeatedly don't start the standup and they just stand ...


1

What does "release pressure" really mean in the context of your team(s)? There are sometimes technical blockers to releases. For example, is it truly the case that every sprint delivers a potentially releasable increment? If there are additional things to be done to make a release then maybe the Definition of Done could be improved (i.e. make sure you ...


1

Sadly this is a situation a lot of teams face in organisations that don't fully understand how Scrum works. The key player in this is the Scrum Master. The two main elements of the Scrum Master role are to help the team to remove impediments and to ensure that they are following Scrum. Dropping meetings due to deadlines is a good example of a situation ...


1

As there is no special meaning to who goes first and who goes after, team members should volunteer. If multiple team members volunteer it should take seconds to sort it out because it does not really matter. If nobody volunteers you need to speak with your team about their commitment to this project and team. It is in their own self interest that someone ...


1

Yes, per the Scrum Guide, all the Scrum Events (Sprint, Planning, Daily, Review, Retrospective) are completed within the Sprint timebox. I prefer to start the Sprint on Wednesday and complete the Sprint on Tuesday. By starting and closing in mid-week, the team avoids competing w/ 3 day weekends & for the US, the Monday holidays.


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