46

If You Aren't Planning Together, You Aren't Working Together The Daily Scrum is not for addressing "issues," minor or not. It's a just-in-time planning meeting for the Developers to collaborate on the current day's work. If there are issues or blockers identified that won't easily fit within the time box of the Daily Scrum, then this is the time to ...


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 ...


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 ...


11

If there are even minor issues - from my experience, it's better to keep it. Issues can be incorrectly investigated, hence, fixplan may be incorrect, hence estimations of the time to fix can be wrong. If the issues truly minor, it's easier to explain them to the team (people like to tell good news) and more joyfully to save the time remained from the ...


9

I can offer another reason for not cancelling the daily scrum, even if you don't think there is anything important to discuss. Developers' personalities vary enormously. Some will gladly announce every obstacle they're currently facing, or highlight every potential issue they can see coming. Others are more reticent, and – if not prompted or given the right ...


8

Project Scheduling isn't a science, but an art. So it's not enough to provide you with a simple equation - which I'm sure you could also do using a calculator - you also have to "understand" your project. E.g.: In your example case, one would need to know why iterations 4, 6 and 7 had low velocities. Was it because new team members were added and their ...


6

When you ask should I, that makes me wonder whether the developers are being allowed to operate as a truly self-organising team. The daily scrum is owned by the team and is for the team's benefit, so only the team should decide to cancel it. If you are not part of the team then your intervention would be outside interference and the SM should feel justified ...


6

TL;DR Hold the event daily, even if you don't use the whole time box allocated for the meeting. Don't skip it routinely, even if you think you have good reasons. Doing so may not bite you right away, but it probably will eventually. If you're not finding value in the Daily Scrum, it's likely because the team isn't really performing just-in-time (JIT) ...


5

In Scrum, a project is done when the client tells you that the product you delivered is good enough or when they don't want the product anymore. That can be when all the tasks currently on the backlog have been completed, but it can also be earlier or later. If your organisation wants to hear a predicted end-date, you can calculate that based on the amount ...


4

The idea of a daily stand up isn't just to discuss issues, but for the team to which includes the scrum master, the product owner and the rest of the team (developers, BAs, etc.) to confirm what they've worked on, are going to focus on during the day and any issues. Sometimes the feeling between the team is 'well, we already know the answers', but the ...


4

I can't think of a good reason to cancel the Daily Scrum. First, there's the reason why the Daily Scrum is held every working day of the Sprint, and ideally at the same time and in the same place - it reduces complexity. By removing the decision on if the team should meet (not to mention when and where), it takes away one decision. Removing as many decisions ...


3

You don't give any context about why people might feel humiliated, besides you mentioning that they are high skilled specialists, so I'll add two things that could cause this kind of behavior from the little information you provided. The first is if your daily standup is in fact just a status report to management. Someone from management participates in ...


2

The idea of daily standups long pre-dates Scrum, and the textbook format--yes, there is one--makes clear the function is not primarily to discuss issues. It is not a status meeting; it is a commitment meeting. If we take the standard three questions and reorder them with the psychology of motivation in mind, here is what is happening: One day, you come in ...


2

If people find briefing leadership or customers humiliating, then it is extremely likely leadership or customers are humiliating them. Thick skin or not, being humiliated is humiliating. Their response, to avoid humiliation, is to provide a type of brief, likely altered in an unfavorable way (read fake). If they're being humiliated, attack the humiliators....


2

TL;DR To perform agile release planning, or to calculate the estimated number of Sprints needed to complete a set of items from the Product Backlog, requires you to calculate your team's velocity as a per-iteration value or range. That value/range is then used to determine how many complete iterations (rounded up) are likely to be needed. Calculate a ...


2

What to do if some talents consider it a humiliation? Step 1 is of course always "Listen". Why do they consider it humiliation. Having said that, in an attempt to be useful, I'll offer the following observation. Sounds to me like the consequences of a mildly toxic culture in which Visibility Is Punishment. I've encountered this relatively frequently as ...


1

Things to bear in mind when you are asked when something will be "complete": The items at the bottom of the backlog are generally the least important, so knowing when they will be done is much less important than knowing when earlier items will be done. A healthy backlog grows - it doesn't just shrink. Being done is not in itself a desirable state to be in ...


1

There are many blog posts (such as this one) which discusses the "pros" of having daily standups. So I'll focus on the "cons". But first things first: I really liked @Barnaby Golden's answer, especially the first two points. Using daily standups as a "silver-bullet" to make sure there's a minimal communication (context-sharing) ...


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