I really dislike these type of articles. The title is there just to shock you, and so is the content... so much that there's a disclaimer at the end of it. I think I would read it with an open mind if the title was phrased differently... "Maybe you don't need standup" or "how standup slows down our company" something of that sort.
"The natural side effects of not doing standup are:"
"- Developers communicate more
- Your team becomes more remote-friendly
- Tech debt gets addressed
- Developers feel more in control and less stressed
- Developers know you trust them and that you have their back"
These bullet points are non-sense. Perhaps developers were not communicating properly, and that's why you started having stand-ups in the first place. Perhaps your developers need more guidance and someone overseeing them. Maybe your business is growing too fast and you need to have more meetings to get things back under control. Some people are goal driven and can take care of things on their schedule other people don't even know how to make a proper schedule.
Here's what you should do:
1. See what works for you
2. Make adjustments
3. Evaluate adjustments
4. Repeat
Meanwhile, read some books on management and learn from more experienced people. There's no reason to drop everything you are doing because a blog post said so.
Our team of developers is 100% remote and we do a daily standup each morning that lasts anywhere from 15-30 minutes. Each person runs through anything of note from yesterday, our priorities for the coming day, any roadblocks, and anything we feel like discussing with the team.
Coming from a team that did nothing remotely close to a standup, I highly value our current system. It's not perfect, and I have no idea if it fits the Valley's definition of "standup", but it serves its purpose very well and keeps everyone on the same page. I can't tell you how many times a person from my team has reached out in the afternoon about a roadblock I mentioned during standup. Or how many times a team member wanted to help me out on a tough user story simply because I was open about discussing its difficulty.
"The natural side effects of not doing standup are:"
"- Developers communicate more - Your team becomes more remote-friendly - Tech debt gets addressed - Developers feel more in control and less stressed - Developers know you trust them and that you have their back"
These bullet points are non-sense. Perhaps developers were not communicating properly, and that's why you started having stand-ups in the first place. Perhaps your developers need more guidance and someone overseeing them. Maybe your business is growing too fast and you need to have more meetings to get things back under control. Some people are goal driven and can take care of things on their schedule other people don't even know how to make a proper schedule.
Here's what you should do:
1. See what works for you 2. Make adjustments 3. Evaluate adjustments 4. Repeat
Meanwhile, read some books on management and learn from more experienced people. There's no reason to drop everything you are doing because a blog post said so.