The startup I currently work for uses stand-up scrum's in the morning to discuss what one has crushed the day before (completed items) and what one is going to

The startup I currently work for uses stand-up scrum's in the morning to discuss what one has crushed the day before (completed items) and what one is going to crush today. This is also the time to explain to the various different teams (Android/Java API, C++ api, server/backend) what you changed, what things they need you to be aware of and what requires more meetings and or having a time where a switch-over is required do to changing something that touches all teams or some of the teams. For example, letting the other teams know that DNS entries now server ULA IPv6 addresses as well as IPv4 addresses and they should probably do testing to verify everything still functions. It works for us, although sometimes the meetings can be a drag when the day before you spent a lot of time in meetings and you don't have a lot of input. It is one way of kinda putting you on the spot if you aren't producing anything which keeps people accountable.