I think they're absolutely worth it. The interruption of flow is minor, because they're predictable. You can plan around them. If you're working on something really complex and urgent, I don't mind if you skip it occasionally (but don't make that a habit).
I think it's good to start the day together, with some idea of what everybody is working on. It helps to detect some issues that otherwise might be ignored or detected too late. Generally, communication is good, and short communication is better.
Yeah, nothing worse than finding out that someone has implemented something that you've already done somewhere else because you didn't know it was being worked on.
Short is definitely good as is the chance to chip in a bit of unsolicited advice from one dev to another ;-)
Comments
I think they're absolutely worth it. The interruption of flow is minor, because they're predictable. You can plan around them. If you're working on something really complex and urgent, I don't mind if you skip it occasionally (but don't make that a habit).
I think it's good to start the day together, with some idea of what everybody is working on. It helps to detect some issues that otherwise might be ignored or detected too late. Generally, communication is good, and short communication is better.
Yeah, nothing worse than finding out that someone has implemented something that you've already done somewhere else because you didn't know it was being worked on.
Short is definitely good as is the chance to chip in a bit of unsolicited advice from one dev to another ;-)