Since the events of the blog post we've been experimenting with some similar steps, which have been working quite well. I hope to write them up soon.
We do standups in UK morning so EU members have a morning standup and China members have a 'day closing' standup: "today i did..., tomorrow i will begin with ...".
works like a charm.
I might suggest we trial what you're doing on Monday.
Everything conveyed in a standup is covered by your project tracker (what you did, what you're working on, and where you're stuck) and discussion can happen in your team chat.
Async development is the way to go. If you're having a standup, you're wasting time. And it doesn't work if you're distributed.
The issue tracking really shows what the status si. IF you're stuck, you assign the issue to someone to help you fix it, or you ask in the team chat room.
Keeping abreast of what's going on in the chat room keeps you abreast of the status of the team. The kanban board records it.
There is still someone (now specifically product owners) who bridges between both sides but both team now feel better sense of ownership as they their separate responsibilities in same product.