4 ms·
Back when I first started doing daily standups at jobs almost 20 years ago -- when agile/xp was first starting to buzz -- it honestly felt like a breath of fres
by cmrdporcupine 7y ago
Back when I first started doing daily standups at jobs almost 20 years ago -- when agile/xp was first starting to buzz -- it honestly felt like a breath of fresh air and explicitly something that management would _not_ want. Quick, informal, brief checkpoint with your coworkers, then back to work. We had a group of almost 20 engineers & QA people in a circle, but it went quickly and inobtrusively... nobody spoke for more than a few seconds. We all knew what everyone else was doing, and could go offline and have a discussion afterwards if necessary.
It was a meeting for ourselves, not for management. There were no status reports to management, no gantt charts, no percentage estimates of completion, etc. Just: here's what I'm doing/not doing.
Fast forward a decade or two and I've seen good and bad use of this meeting form. But I still think it's a good idea, it just requires discipline to stop people from hogging air space or veering off into tangents.
- ubermonkey 7y ago"It was a meeting for ourselves, not for management. There were no status reports to management, no gantt charts, no percentage estimates of completion, etc. Just: here's what I'm doing/not doing." That's my understanding of what a standup is supposed to be, and it's what my experience of them has been. THIS is useful. It's in particular useful if you have devs on the team who tend to get kinda "wound around the axle" on problems rather than speak up or seek help. There will always be devs who think any meeting is by definition a waste of time, and you can't make those people happy, but a true brief standup meeting as described here is SUPER useful. (Daily's probably too much though.)
- ownagefool 7y agoLike many things, if it works for you and doesn't turn negative, then that's great and more power too you. Personally, when I lead a team, I keep abreast of what people are working on and ask them if they need help, or tell one of the more suited senior guys to offer a hand if it's an area I can't easily help in. I imagine the standup helps more when you're lead is a non-technical scrum master guy who doesn't have much of a personal relationship with the team. On the latter point I typically buy my team members fancy coffees and the occasional lunch, and it's easy to get on with them if you care about their careers, so I've never needed a standup.
- cmrdporcupine 7y agoThat's the point: the stand up is for the team, not the manager. She/he should stay out of it.
- ownagefool 7y agoThat's a difficult argument? Is the manager not part of the team? Depends on the org, I guess. Either way, I'm not so sure the statement means much. The point of agile is to do what's helps, so if a standup is useful for the above reasons, it's entirly possible that another approach solves the same problem, negating the need for the standup.
- kthejoker2 7y agoNot every group interaction requires every member of the group, not sure what's hard to grasp about that. The manager has plenty of other ways to gather status updates and feedback as you note.
- ownagefool 7y ago> not sure what's hard to grasp about that. Your tone is slightly rude considering you're essentially agreeing with me. You'll need to note the entire thread for the context of my discussion. I was specifically saying a good tech lead and other senior engineers can help engineers get unstuck without actually necessitating a standup. For me, standups are fine if the team actually want to do them and find them useful, but 9 times out of 10 they're enforced by someone non-technical and require the entire team listen to people drone on justifying what they did yesterday. Personally, I find the assumption that I can't communicate with fellow engineers without such a thing pretty insulting, but do understand that some of us do struggle with this thing, so it's different strokes for different folks.
- cmrdporcupine 7y agoIt definitely depends on the structure of the org. But I do make a distinction between management and team lead. On some teams the management is technical and involved in daily tasks. In others, less so. But the key thing is that the daily standup is NOT a status report for management! That should not be its purpose! It is for the team members to sync with each other, not a daily report for task management.
- artsyca 7y agoYea, the minute the managers stick their beaks in the whole vibe turns sour
- jsight 7y agoI seem to remember a time when standups did not necessarily involve the product owner. I feel like a lot of things have changed in Scrum that have progressively brought more of management into its ceremonies in ways that have actually disrupted a lot of the early goals of the process.
- cmrdporcupine 7y agoInteresting, yeah, we were doing something closer XP, not Scrum. I've never done Scrum. Haven't done "agile" in the last 10 years, as it's not really a thing where I work now. But yes, in XP, the 'customer' or 'product owner' would not attend a daily standup. The purpose of the meeting was for developers to sync and maintain velocity and social and work cohesion. Meeting with customer/PM was something that happened at the end or start of iteration.
- rezeroed 7y agoWhat use is knowing what 20 other people are doing today? Are you interacting with all of them? Interesting to know what projects they're working on, but I can be told that once a month if I haven't already got that while chatting to them at the coffee machine. A 20 person meeting for each to speak for a few seconds is to me very theatrical - drop a sentence in a chatroom. If I'm not working directly with you I'm not going to read it, nor listen to you in a stand-up.
- cmrdporcupine 7y agoIn an 'agile' process people should only be working on any particular 'story' for 3-5 day period. Everyone on the team should be interested in what they other people are doing, because they may in turn be pulled into work on some part of it next. In a healthy team everyone should be invested in the success of the product, and have some knowledge of most aspects. Frankly, once things scale beyond that, where you have large teams of people disinterested in what's happening beyond their choice of specialization -- "agile" starts to not be a good match anymore.