This would be a massive waste of time if it were with the whole team every day. I don’t need to know what every other employee on the team is doing every single day, and I don’t need to spend time listening to them explain it. I’ve got shit to do.
My husband holds his team meetings at 3/4pm ish on friday on zoom with beers. Afterwards he tells everyone to fuck off home.
THAT is how you do it. It turns into a pile of geeks talking geek and part post-mortem, part decompressing from the week and they’ve actually had some absolutely mint ideas rising out of deformalising the dev pileup.
We used to have a rigorous schedule.
Arrive at the office between 8-830. Make coffee and chat. At 9am we started the daily meeting. We all read what we were going to do today to each other. By then it was 1130 and so we broke for lunch. After lunch, at 1300 we would do the thing we said we would do. At 1530-1630 we would submit out updates to the project management system and produce tomorrow’s report for us to read to each other. 1700 we would go to the bar then head home around 1830.
When I started working for myself I would usually start around 9 to finish at noon, including travel time.
It wouldn’t be explaining it. It would be your teammates telling everyone where they are on the projects you all work on. If you aren’t working the same projects, then you aren’t on the same team. Or you need sub-teams. If your work is so independent you don’t rely on anyone else’s work and vice versa, then you probably don’t need standups.
I agree with you. That’s why we make our teams small enough in size that standups are 10min max, usually more like 5.
That said, it can be really beneficial to hear that Joe is working on something similar to a thing I’m going to start today. He may be able to give me some lessons learned or point me to a library.
But I completely agree that big teams a make this an annoyance. I used to be on a 20 person team and standups were completely worthless.
Now, we have 3-5 devs per team and it’s usually really quick.
This would be a massive waste of time if it were with the whole team every day. I don’t need to know what every other employee on the team is doing every single day, and I don’t need to spend time listening to them explain it. I’ve got shit to do.
My husband holds his team meetings at 3/4pm ish on friday on zoom with beers. Afterwards he tells everyone to fuck off home.
THAT is how you do it. It turns into a pile of geeks talking geek and part post-mortem, part decompressing from the week and they’ve actually had some absolutely mint ideas rising out of deformalising the dev pileup.
Late on a Friday? Yeah, no.
nah yeah, mate. You spend the arse end of your friday workday drinking beer and talking shit in an informal setting and then fuck off early
the problem is, then i a can’t leave at lunch if my shit’s done. And lets be honest, nobody was doing shit on friday anyhow…
Zoom meeting. Everyone works remote
I’d rather be doing that on my own time, or something more productive with friends, thanks.
They are getting paid for it since it is during work hours, and the beer would probably be on the company as well.
Ok, so you go hold your own weekly dev meetings
We used to have a rigorous schedule. Arrive at the office between 8-830. Make coffee and chat. At 9am we started the daily meeting. We all read what we were going to do today to each other. By then it was 1130 and so we broke for lunch. After lunch, at 1300 we would do the thing we said we would do. At 1530-1630 we would submit out updates to the project management system and produce tomorrow’s report for us to read to each other. 1700 we would go to the bar then head home around 1830.
When I started working for myself I would usually start around 9 to finish at noon, including travel time.
It wouldn’t be explaining it. It would be your teammates telling everyone where they are on the projects you all work on. If you aren’t working the same projects, then you aren’t on the same team. Or you need sub-teams. If your work is so independent you don’t rely on anyone else’s work and vice versa, then you probably don’t need standups.
I agree with you. That’s why we make our teams small enough in size that standups are 10min max, usually more like 5.
That said, it can be really beneficial to hear that Joe is working on something similar to a thing I’m going to start today. He may be able to give me some lessons learned or point me to a library.
But I completely agree that big teams a make this an annoyance. I used to be on a 20 person team and standups were completely worthless.
Now, we have 3-5 devs per team and it’s usually really quick.
So what if it’s a waste of time. Gotta make the 40 hours anyway.