Research how to encourage participation in async retrospective

[dmundra]

Provide options/opportunities for more participants to engage in async retrospective.

[dmundra]

Some ideas for async retrospectives. Need to read them:

• [x] https://www.parabol.co/blog/async-retrospective-time-zones
• [x] https://geekbot.com/blog/remote-retrospective/
• [x] https://about.gitlab.com/blog/2019/12/19/how-gitlab-handles-retrospectives/

[dmundra]

Question to bring to accessibility practice area meeting. Fully async retrospective? Relates to #406

[dmundra]

Following https://geekbot.com/blog/remote-retrospective/, a fully async retrospective could look something like this:

• In the week of the retrospective, on day 1 the facilitator prompts in slack the retrospective questions and asks folks to enter them at their own pace throughout the day.
• On day 2, the facilitator summarizes and consolidates common points. They then provide a poll to vote on which ones (up to 3) should be addressed.
• On day 3, the facilitator asks for action items for the 3 most voted items from the poll.
• On day 4, the facilitator creates issues and closes the retrospective.

Other notes, rotate the facilitator, still use GitHub projects with async instructions, facilitator follows up on any threads that have lingering discussions.

[dmundra]

Got approval to try this out. Created a new board (https://github.com/CivicActions/accessibility/projects/4) with new instructions and updated ticket #406.