All the team members can agree on some set of guidelines to help.
We are following these fun guidelines that are working very well for us:
No person can talk for more than 1 minute at a time.
Every person in the team must talk.
Every person must nominate the name of another person in the team, at the end of his/her turn. The nominated person will then talk ...
A few additional suggestions that we've tried with some success:
To specify seating order, you can do things like:
have everyone roll dice (slack has a D&D dice roller app, use /roll d100 to get a good dynamic range)
have everyone say their favorite color then go in spectral order
choose the first person by something lighthearted like oldest car, or ...
The first item in the Agile Manifesto is:
Individuals and interactions over processes and tools
Your question lists a bunch of tools and asks about more tools, some that are more flexible to use given your new situation with people working remotely.
How about turning the problem on its head and think about improving the interactions between people? At ...
But also, let it be said that most of the software teams that I have worked with over many decades are entirely or partly "remote." (Even within the USA, which is a very big country.) Some people who work in the same city work from their homes and have done so for decades.
Many different types of collaborative software, project management hubs, and so ...
You will have to realize that video conferencing is a far cry from a face-to-face meeting. Almost all the non-verbal communication that takes place in a face-to-face meeting goes out the door in a video conference.
It is also harder to interrupt someone or to detect when someone is about to begin speaking, so people tend to speak more in turns and wait a ...
You can take a look at https://funretro.io/ service. You can share the board in advance so that team adds their points in advance. This will speed up the retrospective. This service offers several popular retrospective templates.
Another tool worth exploring is Miro (previously RealtimeBoard): https://miro.com/blog/features/realtimeboard-is-now-miro/.
Reading the article strongly suggests it is once every two weeks. It is very unlikely you would need to hold a 1-2 hour delivery focused meeting twice per week, every week.
Having said that, the whole article seems way to precise. The frequency and duration of all these meetings are likely to vary depending on the organisation, the domain, the team size and ...
I also think David got the answer right. But to add a little.
Post-mortem is a common term for this activity that is now understood by many.
The word's actual latin meaning is less important than the perceived usage of the term from the medical world, just within a project setting.
This is always the issue of borrowing a words usage rather than it's meaning.