The frequency of standups should be determined by the team and blockers should never have to wait till standup to be surfaced.
I work on a growth product team and we frequently have devs pulled away to work on a feature in a different product. The engineers started losing track of availability of others and what features were going to prod became opaque. We opted to move back to daily standups with status reports as it kept the team informed and thus motivated, and gave an opportunity in several cases to refine approaches from the start.
There are, of course, other ways to accomplish this, like having a public issue board, but often private conversations don’t make it to the issues.
The frequency of standups should be determined by the team and blockers should never have to wait till standup to be surfaced.
I work on a growth product team and we frequently have devs pulled away to work on a feature in a different product. The engineers started losing track of availability of others and what features were going to prod became opaque. We opted to move back to daily standups with status reports as it kept the team informed and thus motivated, and gave an opportunity in several cases to refine approaches from the start.
There are, of course, other ways to accomplish this, like having a public issue board, but often private conversations don’t make it to the issues.