Consider the standup to be the canary in the coalmine. Most of the time people can ignore the dysfunction, work around it and pretend it isn't happening by just getting on with the job as much as possible.
But the standup will then become increasingly uncomfortable. Every single day.
In a healthy organisation, you can have perfectly pleasant standups, even without Scrum or Agile. I mean, what does a healthy team have to fear from standing around for a few minutes bringing each other up to speed?
It's a process that is very close to what often happens quite naturally around the time everyone on the team has arrived at the office (or online).
A standup can only become poisonous if the poison is injected from elsewhere. In Gareth's case abusing it for management status reports. In other cases it might be tension between team members, not having a clear goal, whatever.
The point is, you cannot have pleasant standup if there is that kind of stuff going on. Which is all the more reason to have a standup, unless it's your policy to ignore problems rather than dealing with them.
Standups aren't just not poisonous either: they are a very good poison detector.
This is exactly the behavior I have seen of well functioning teams. Usually there is a period when the person comes in, maybe after coming up to speed on their email where they get informed and up to speed on what is happening with everyone, if anyone needs anything, what people are working on, and then get to work!
Standups are just a formalized approach to what can be a drawn out process for an individual, and in some cases may not be "normal" for your standard introvert dev types who sit at a computer all day and perceive meetings as multi-hour long chores that are inflicted on their participants instead of quick high quality bursts of information distributed in an efficient fashion (face to face).
0. 9am, catch up on email, then coast for a while knowing you'll have to stop work at 10am.
1. Find out which meeting room the 10am standup is in
2. Figure out where in the building that room is
3. Travel to the rough part of the building, hunt around for the room.
4. Wait for everyone else to do the same.
It's now 10.20am
5. Stand (OMG the standing!) around for 30 minutes listening to a boring load of status updates from 20 people that have absolutely nothing to do with you.
6. Give your status update (Yesterday I did some work. Today I'll do some more work. What's blocking me is this f'king meeting.)
It's now 10.50am
7. Travel back to the part of the building your desk is in today (if you can find it) and grab a coffee on the way.
That's an hour gone, and it's only another hour to lunch, so no point getting into anything too major. Knock off some smaller to-do items. Lunchtime!
An alien race observing us would conclude that teams were a device used to prevent work getting done.
I like doing the stand-up as early as possible, so that there's minimal slack time before hand. And I prefer to work in ways that are less dependent on the state in one's head, including test-driven development and pair programming.
The standup is always in the team room. Everybody on the same team works in the same room. Generally, you do it in front of the kanban that shows the state of the project.
Because it's right where everybody works, it's pretty easy to be on time. Regardless, it starts on time. No waiting for stragglers; it just encourages them.
You stand for 10 minutes or so.
The team is some reasonable size; I think of 12 as a maximum.
If the people turning up have nothing to do with you, then it's not actually a team. Teams are groups of people that win or lose together. Team members help one another out to achieve shared goals.
If what people say is boring, you should be able to tell them so. They are there to talk to the team; there's no point in them saying things that aren't useful to the team.
Coffee should be in or near the team room. Ditto water, snacks, and other things necessary for humans to do work.
The stand-up should be run in such a way that people leave ready to jump on things.
If I had to guess from your description, I'd say that Yahoo took a top-down culture, pasted on some Agile rituals, and kept right doing the same old bullshit. Which, honestly, is a giant waste of time. If you're going to do waterfall in a command-and-control context, just do that. No sense putting agile lipstick on your waterfall pig.
12 minutes, a team of 8. Every time.
Additionally, I think it is important to remember that standup is not a "justify my existence on the team" meeting. Having nothing to report is fine.
Off the top of my head, I'd look at the size of the unit of work and the length of the release cycle. I think Agile processes work best when the work is broken down into lots of small deliverables that meet the INVEST criteria:
If the team is jointly completing a few shippable things a day, then everybody should have a pretty good idea that everybody else is working. Doubly so if those are actually getting released daily.
Conversely, this particular dysfunction of standups is a useful index of how much the corporate culture leads people to feel like they must justify their existence.
In a meeting where you're supposed to say what you've been working on, at a job where you're paid to be working on it, in what way is it fine to have nothing to report?
That said, in a quality team staffed with quality people, you don't worry about people goofing off during the time they're blocked... you assume they are doing some kind of self-development, or tweaking some small detail somewhere, etc. It's when somebody is blocked for long enough that it puts their tasks in jeopardy that the scrummaster needs to start escalating things and working to get the roadblocks removed, and/or manage expectations vis-a-vis the tasks for the iteration.
I learned one of the Agile methods before the term Agile was even invented. Adopting it made a giant difference in the quality and sanity of my work.
But so many people today have have pseudo-Agile methods inflicted on them in large corporate contexts. There, the point isn't to make things saner and more effective. It's to please some executive who has a bee in their bonnet. And often, they only adopt some labels and some rituals. It's all pain, no gain.
I wrote about how this happened here: http://agilefocus.com/2011/02/21/agiles-second-chasm-and-how...
But it's at the point where I avoid using the term "Agile". Or any other buzzword. I look at the circumstances, and say, "Hey, you guys feel pain X. Can we try change Y and see if that helps?" Often, the tool is one from the Agile or Lean toolbox. But I won't talk about the particular process I'm borrowing from because a) most people don't care, and b) a lot of people have been burned with faux-Agile adoptions.
I believe the bulk of what people call "Agile" these days is terrible. You could say that most of that isn't the true Agile. But at some point I think that isn't a battle worth fighting. Personally, I just say that Agile started out as X and has become Y.
I would rather they didn't throw the baby out with their bathwater, but in the stories I have heard, the vitriol is entirely valid. I don't think it should be all directed at "Agile", in that managers deserve a lot, as do the hierarchical power structures in which the managers work. But the Agile people also made choices that led to this outcome, so I think it's fair that there's some spleen-venting directly at the Agile movement.
For a while I worked on a team with a small codebase, which we all knew pretty well, and it was very likely that if somebody made a change today, I'd be working in the same area of code in the next day or two.
In that situation I thought standups were really helpful.
My current team/project is a bit larger and it's maintenance on a much, much larger code base. The project is large enough that nobody really knows the whole thing very well, and everybody works on a different section and there's not much overlap. If I were to switch places with somebody I'd have a lot more to learn than just what they've worked on recently.
On this project we're still required to do standups, but they're useless. The information wouldn't be very useful to me even if people kept to one or two sentences of what they were doing. Of course, few people do that, and they usually go into obscure details that maybe two people in the whole group really understand. And that's when I tune out...
I think the real problem is when a standup is the only way that a team actually communicates status. At turntable we rely heavily on chat, which also contains messages indicating when new things are being pushed, and we also make it a point to have a lot of face-to-face communication. Our twice-weekly standups are a good way to fill in the gaps, if there are any, but they are by no means the only way that people find out what's going on.
Also: training/coaching wouldn't hurt..
Usually they either are void of real information (as they are supposed to be quick) and nothing is discussed in depth, or if things do end up discussed they end up taking too long.
Unfortunately they have propagated in most work places/engineering cultures.
Information should flow naturally between engineers. If you have a jelling team, people should communicate with each other naturally, without having to be forced to stand up and listen to status reports (that's exactly what standups are).
I prefer once or twice a week engineering 30mins sync ups. Short meeting, that get to the point on whats going on, and you have some time to discuss things in depth if needed. For any small things, the expectations would be that engineers should communicate with each other directly.
Instead of having 5 interruptions a week, you have one or two (slightly larger ones). At the end of the day accountability should be on the delivery of projects (end results), and not efforts (which standups are more about showing efforts, rather than results).
From personal experience, experienced engineers tend to highly dislike them, and the over-reliance on standups is an indication of a weak engineering culture.
I've noticed that developers can be divided into two groups based on whether they prefer to work with others or by themselves.
Those that prefer to work by themselves take chunks of work that can be done without input (formal or informal) from their fellow developers, (who they may refer to as "teammates" despite the fact that they don't work as a team in any real sense.) For this group, having a daily standup is a waste of time, because there is no work to coordinate.
Those that prefer to work with others take chunks of work that can't be considered complete until their fellow developers have also completed their portions. They seek continual input from their teammates in order to keep everyone on the same page. For this group the daily standup is just a more formal version of what they already do informally.
Edit: Haven't tried them myself; just did an hnsearch. It would be great if Hacker News would always show the subdomain if not www.
1) not correctly identifying "chickens" and "pigs". Pigs get to talk in a standup, chickens do not. In fact any interaction with the pigs and chickens should go entirely through the scrum master (and not during the standup). If chickens want to come to the standup it is to observe only.
2) conversations. The standup is not the time for conversation. The best method I've employed is to have each person specifically answer three questions: what did you do since the last standup? What are you going to do between now and the next one? Are you impeded in any way? The last one is where conversations often start. Scrum master needs to stop those, identify the people who need to talk after the stand up, and move things along.
When you follow those as hard fast rules, standups shouldn't take more than N*3 minutes where N is the number of pigs.
If you're doing Scrum, the only issues you should really be bringing to standups are those you can't solve within the team that you need the Scrum Master to sort out. Anything the team can fix for itself isn't blocking, it's business as usual.
Consider a team working on a live browser/Facebook-based free to play game (social game as a service). There are many releases a week.
- Engineering typically requires art assets to begin/complete work. Ie. building models, unit models, 2D unit images, item images, etc.
- Releases don't end when they are pushed up to prod -- most releases have some kind of "go to market" plan that must be executed. For example, if a new Dragon Armor is released, we need to message all players to inform them of the new functionality and educate them on how it works, there would typically be a simultaneous tournament or contest that awards the new Armor as a prize, and possibly some other sale or promotion on a related item.
- It's a time for product to provide updates on where different specs are and on key game metrics.
- Customer Support/Community Management also provide updates on any emerging issues in the game, which improves everyone's situational awareness.
Of all the standups I've participated in going back 5 years I'd say only one was any good. It was every other day, it was forcibly limited to 15 minutes or less, it was always on time, it was never allowed to go off on a tangent, it only had about 3 or 4 people in it, and it was actively pushed away from being a status meeting. This contrasts with every other standup I've been a part of which almost always cut into productivity, and worse. For a while there was a daily standup with 12+ members that often went for 45 minutes and sometimes went for an hour and a half.
The problem with a formalized methodology like standups (or agile in general) is that if you don't have very well defined and explicit reasons and goals and you don't make that a part of the system then people will just drift into doing what seems to make sense to them, which is status reports and aimless meetings.
Your last paragraph explains why you have to be committed to doing it right. It's easy to do it wrong, and it becomes worse than doing nothing. But if your complaint is that doing it right is hard or that you need management buy-in, that's different than it doesn't work in practice.
As I said, the problem is that the reasoning and goals become too easily separated from the activity. And then before you know it you've got cargo cult behavior on your hand.
Wouldn't you know it, the instances where standups were used effectively was when the team had a lot of experienced people who knew how to work well. A methodology that is only effective for people who already know how to work well is not a good methodology in my book.
Meetings are one tool among many for team communication, it's just that very few people are able to run a meeting effectively. I used to believe that all meetings, in any form, were a waste of time. Right up until I worked for someone who actually knew how to run a meeting. It was amazing - in a 12-15 person meeting, everyone person contributed, tangents were quickly cut-off, and they rarely lasted more than 30mins. Sadly, she was promoted (i mean, good for her, bad for my group at the time) and without her guidance our group meetings quickly reverted back to a multi-hour mostly useless waste of time.
The lesson I learned is not to dismiss meetings outright. Spend some effort learning how to run them effectively, and it's still a useful communication tool.
Trello does all the communicating.
1) It tells me whats done and what is not, through the checkboxes
2) On larger projects, the guys leave updates in the activity section every couple of hours or when they hit a milestone or a are stuck with a problem or are unsure of something. Think of these as like facebook style updates but for large projects.
These updates are delivered to me in real time. We can then discuss any problems etc at a suitable time at their convenience or I can pre-emptively direct them to someone who can help. Unless the problem is urgent in which case we discuss it then and there.
This way I know what's what and the guys have an open channel to me.
If it lasts too long, the person running it has lost control
If it ends up berating a coder twice a day, every day, regarding a multi-day implementation task, the person running the standup is an incompetent project manager
If, as others have given examples of, people zone out, or become unconfortable, the project has become toxic and the standups can't fix that
If standups adhere to dogma more than they solve problems, the person running them lacks critical thinking skills and knowledge of project management techniques
Every morning we have our meeting which maxes out at 15 minutes. The designated note-taker rotates daily and takes the list of current action items to be added to RedMine.
The biggest difficulty was fairly simple actually - removing digression from the mix and also removing things we've completed from the meeting.
There are no side conversations while stuff is being covered, and every day we sum up what we did in a company-wide email. Other subjects happen offline between relevant parties. This has been remarkably effective for us :)
That works for our team of 4-5, but I understand that it can't scale. Of course, if management started calling it a stand-up meeting and took away the coffee, I'm fairly certain we'd get less out of it.
tl-dr; why is a stand-up meeting better than just grabbing a coffee with your colleagues?
The problem with standups at the company I work for is our team work on multiple projects so standups end up being just "I'm working on project X and it's going well, no blockers, cheers!" updates from everyone in the circle.
Standups are probably better for teams working on a single product as everyone has a stake in what's going on
Would you rather get at least one extra IM or phone call(?) from each member of the team randomly throughout the day as you're quietly and productively working in your own zone?
I'm all for anything that tends to eliminate mental context switching during the day. Needless to say, not a fan of any office environment for coders.
This, on a team with four engineers and three QA types. We sat next to each other. We didn't need standups, we needed to be left alone to do work.
Finally, on one project the PM (who had appointed himself scrumlord) finally let us meet only twice a week, and had the common decency to call the meetings "status".
Call things what they are.
If done well they can be a great facilitator. Just make sure it fits your culture.
Most people post by noon, and the manager has a written log. It's been working well so far.
Some places don't manage standups well at all, and that is one of the big problems with standups in general - they become status meetings and take too long. When done right, they are very useful as you quickly know what everyone is working on and if someone might need your insights on something (which should then be a separate meeting and not covered in the standup).
There are a few main features of standups that, if abused or ignored, can lead to awfulness.
- They're supposed to be short, very short. A few minutes at the most. They do not work for large teams (20 people giving a status update is a lot), and if you find yourself having 20-person standups it's time to think about if you should be breaking them into multiple independent standups.
- Managers aren't present, or aren't allowed to speak. This is an opportunity to ask questions, ask for help, describe what you're working on, to other members of your team, not to justify what you were up to yesterday to your boss. It's sharing, not reporting. This part is key.
- You don't troubleshoot in a standup. If you say "I can't figure out why I can't Foo module Baz", there shouldn't be a discussion about it, but someone else might go "I've worked with Baz a lot, let's take a look together after standup.", or later in the day someone might go "Oh hey, that problem you were having with Baz? I think I know what's happening." - this is the ideal intent of standups. Very quick snippets that highlight certain things in everyone's minds.
- It doesn't need to be documented. It's not a meeting, you don't need to take down minutes. Actual tracking of work done occurs separately (your scrum master should be doing this).
From the article:
- Make sure everyone is working on the right thing
- Help out other team members by taking work off their plate or helping them by sharing domain-specific knowledge
- Keeping everyone informed
How is that different from a status meeting? I've heard "standups are not status meetings" over and over from the agile community, but I don't get it. They sure seem to be quick status meetings that allow everyone to get a handle on the current status of the iteration?
I think standups could work, but they should only focus on things that impact the project (breaking change to an interface, or significant new things that are available) or things that are blocking work. And honestly I think email does a better job at that with a lot less impact on flow.
It actually has worked really well in preventing of siloing/cliquing of work effort. Another thing that has helped greatly is using a physical task board and organizing conversation by task instead of by person. This puts less emphasis on "looking useful" as individuals and more on championing tasks to see their completion.
This is a very good approach. Separating task and people is key to getting things done. When things are getting tough for an individual, the team can rally behind.
E.g., Your stand-up is from 9-930a. After which you can't start anything substantial because 'lunch is coming,' but that's 2.5 hours away (assuming you lunch at noon).
I like morning stand-ups, but a big problem is that if the stand-up is at 9, I start winding down whatever I'm doing around 8:30, and I don't start new tasks after 8-8:30. Multiply the loss by the entire team every day and that's potentially a big loss of time. And because everyone's schedule is different, there's really no place to put the meeting that avoids the problem.
The benefits of a well-run standup can outweight this productivity cost, but it's a real cost that needs to be considered.
I guess this does presume that everyone wraps up at about the same time every day, which I've generally found to be the case, but may not work well with widely distributed workers or places where people actually practice a wider range of work hours.
Team members report on what they did that day, but seldom think about the things they are going to get done next and the things that are preventing them from getting started on the next thing, which in my opinion, are the more important things to focus on.
We had a huge problem with non-delivery people scheduling meetings willy-nilly, just because people's calendar's were free.
I've put the kibosh on that, as much as possible, especially in the afternoon.
I would strongly prefer to have a stream of commits and JIRA issues in HipChat to review the following morning than have to do a standup. But not all engineers are as good as they like to believe they are at following development workflows and processes.
The purpose of the meeting is for the team to get together and co-ordinate the work that needs to be done in order to meet their Sprint goals. So while you may be able to get status information out of that, it's more important for team members to use that time to figure out how to meet their goals.
In addition, status should be obvious in Agile teams. This is why you usually see things like cards on walls and burn down charts. If status isn't obvious to everyone, you may want to see if there are other ways the team can make that information highly visible.
Check out: https://www.udemy.com/improv-your-agile-scrum-stand-up/?coup... for more.
I definitely agree with this. Standups/scrums have become much more productive since management stopped attending. It's hardly a "status" meeting any more -- sure, we talk about what we're working on, but there's a lot of jumping in by other team members with suggestions, help, or "I was going to do something similar, let's coordinate after the meeting".
Also, who are people talking to if not the rest of the team? Why are they saying things that other team members don't care about?
Edit: wrong, not right.
Another wrong way is to take a long time. It's a quick meeting, where everybody syncs up for the day and major issues are raised. I think of it as like the way players will quickly huddle together on a sports field. It should be high energy, biased toward finishing, and tabling any significant discussions for later.
As far as I'm concerned, they only make sense in a team environment. Where people are jointly working on shared goals and extensively support one another. In the Extreme Programming approach, they go along with a team work queue and collective code ownership.
If people, say, have individual work queues parceled out by a boss and don't interact much, then as far as I'm concerned the stand-up meeting is the wrong tool.
I was there because the money was good. Motivationally it was about as effective as being micro-managed on a waterfall project.
The only difference between standups and status meeting is that you're not there to fill a report card. You're not there to show your manager you did something. You're just there because it's the only 10 minutes in the whole day where the whole team comes together to discuss. It's (at least in my place of work) highly informal, very chilled and very genuine. What we do is say what we're working on and ask for help and/or ideas.
We have a private IRC channel for this, but the fact that we meet face to face for 10 mins a day really does bring up interesting fast conversations.
The whole point of standups is not to take notes, not to keep track and just have a quick break to talk (not type) about work.
I also feel like the original "Standups are Poisonous" author may work in such an environment also.
I once worked for a company (who shall remain nameless) where the development process could be generously described as a perversion of agile. They wanted the cool buzzwordy notion of agile, but didn't want to actually subscribe to an egalitarian, hands-off environment where the engineering process is largely self-managed.
So, manager as scrum-master (noooooooooo), manager present at standup (noooooooo), and worst of all, story points becoming a measure of productivity (noooooooooo!). Standups would routinely last half an hour, even though our team was literally 4 people large, because the scrum master/manager would stop someone and drill down constantly.
Oh, and the manager ran estimation too, and with pressure from above would blatantly try to influence estimates downwards. The rest of the team compensated by inflating small tasks. Yay.
Tasks would also get assigned to specific team members from the get-go, because the team was horrifyingly silo'ed and we were constantly "too busy" to cross-train by spreading tasks around. I find that silo'ing is by far the biggest thing that makes standups seems irrelevant - why listen to what that guy is doing if that task has no bearing whatsoever on anything you're working on, or will be working on?
You see these a lot in cargo-cult style adoptions. They understand that they need to do these practices, but they don't understand why. The end result is that they try to pervert them to serve their own purposes (e.g. daily stand-up as a status meeting for managers) and lose the real value. Then they complain that "Agile doesn't work here".
I find it supremely useful - it builds self-understanding in the team and a sense of actual teamwork, even camaraderie, improves visibility of what everyone is doing (and where you may be able to help - we often chip in when someone says they are stuck to say "yeah I know a bit about that, let's chat about it after stand up") without feeling like surveillance. You also get to know if there are going to be any demand on your time for discussion (say of upcoming work) from our line manager. It is not a status meeting. Both the theory and our lived practice make it a synchronisation meeting that defines the heartbeat of the sprint process. Its actually a comfort to know if you are stuck you can say so in the stand up and people are aware you are having difficulty.
If you are doing scrum right then status meetings should be unnecessary during a sprint. The interaction between the team and the product owner (co-ordinated by the scrum master to prevent the product owner becoming noise) should be sufficiently smooth that when you get to the demo at the end of the sprint nothing should be a surprise to the product owner (they are part of the team after all) but should be for consolidation and display to wider stakeholders. We use e-mail and GitHub issues to keep the product owner in the loop at all times (increasingly moving to just GitHub) and HipChat for status throughout the day. As for "higher level" status meetings, our line manager has no need for this from us because she is much closer to the work through the stand up and our scrum master will handle these duties as required so we can get our heads down in the sprint. Status meeting for more senior management are the job of the line manager, who also plays a role in just letting the team get on with development. Status meetings as people seem to be describing them here seem to be the kind of productivity killing time sinks that the scrum process defines as "noise" and attempts to use the scrum master to keep as far away from the team as possible.
(PS I work in IS Web Development University of Kent where we take agile process in our team very serously - we'll shortly be hiring ;-) )
"Wednesday, 24 April
Fixed bug #434, added protocols between user and tasks. "
And if they _really_ want to know what I am going to work on or what issues I have. Please check my tracker. There are bugs, features and chores. And each of them has comments that describe any issues I might have run into or will.
If you are fixing bugs then the story should be "x bugs related to foo feature" and your daily standup report should be "I fixed x bugs on foo, I have y to go, should be done today, no blockers"
Agile in not optimal for maintenance or emergency production issues. These are dealt immediately and only mention in the daily stand up as a blocker stopping you from finish the task you actually intended to complete. They are not even added to the product/sprint backlogs.
As a rule of thumb all user stories added to a sprint should take between half and 2 days to complete. If you have a whole bunch of small bug fixes, group them together so they fit in that time-frame (i.e. all UI bugs in page foo). Otherwise you end up polluting the backlog with hundredths of little things and turning your planning meetings into overwhelming nightmares.
Just think about it: if everybody in the team is working on only one or two tasks every day, the daily stand up will take each member about 30 seconds and the whole meeting less than 5.
standup = log --graph --decorate --oneline --author="YOURNAMEHERE" --since="yesterday"
Status meetings are for the benefit of a manager. They allow everybody to report to the manager so the manager can feel comfortably informed. These are typically useless to everybody else because they drag on for far longer and nobody pays attention whilst each individual briefs that manager. These sorts of meetings are detrimental to getting a team to self organise.
While yes, you may be able to derive status from a daily stand-up meeting, that's not the point.
The point is for the team to co-ordinate their work and figure out how they're going to get things done. Done well, it has more in common with a planning meeting than a status meeting.
I actually have a whole course on how to have good stand-up meetings.
Here's the link: https://www.udemy.com/improv-your-agile-scrum-stand-up/?coup... I added a discount code for anyone who's interested.
Good luck with your course.
Sure you do, at a very high level. "Milo is doing the SYNAPSE adapters, Stinky is working on the compression drivers, Lisa is doing the UI stuff and Teddy is fixing the build system."
That can be covered in 10 minutes, and then the individuals involved can (and should) go off and hold whatever independent meetings - if any - are required for their specific tasks.
To me a standup is a tool to keep the team fully gelled and jump on any issues which will cause a sprint to spiral out of control. They should only last a few minutes per person (we have about ten people) and we schedule coffee immediately following to tackle any issues that were tabled due to a timebox.
Note: We have a 'coffee club' where everyone brings in coffee and we french press it every morning. So its scheduled only so that nobody pulls us into meetings ;). We love our coffee.
If the meeting takes longer than it's supposed to, walk out or hang up.
If someone is rambling on about something that isn't going to help the team move forward, say something.
Standups will not fix a bad team, or a bad manager.
The average card had maybe 4 words on it. We knew about issues because we talked about them.
I love the written word, but it is so much slower and less efficient than face-to-face communication in so many circumstances. The highest-bandwidth, lowest-latency human communication system is conversation.
On top of that if you really want the tool to show everything everyone is blocked on at any time, you wind up spending a lot more time than strictly necessary just typing status updates.
In my team's standups, people frequently wind up shifting plans to cover issues that are brought up or offering work arounds to mitigate blocking issues and kick them down the road a bit to give the scrum master(who is also our VP) time to clear them. We also wind up frequently offering to pair with different people based on what they're working on(i.e. one dev is working on something that touches part of our system that's particularly fragile, another dev more familiar with that area will offer to pair for the morning).
Since we started doing morning standups I've seen our team get more productive.
We're a 6 member team and our standups are typically 5 minutes or less.
We stopped that "what you did yesterday, what you're going to accomplish today, do you have any roadblocks" rigor nonsense.
We just turnaround to see what's going on. In the beginning, I was pretty turned off by the rules we were using for standup, but once we stopped all that, they're pretty helpful, just so we know where we all stand.
My first job out of school, we had a developer that claimed that he couldn't get any work done around the office because he was constantly being interruped. Well, his boss let him work from home on this very important project with a hard deadline. Well, he wasn't checking in and he was being vague about where he stood. Lo-and-behold, 3 months later he has nothing to show for, and he's history.
As a previous poster put it, standup can be a canary in the coalmine.