How we work: inclusive retrospectives for the GitHub Accessibility leadership team

Learn about tools and processes the GitHub Accessibility leadership team uses for retrospectives that fully engage every team member.

GitHub logo
GitHub
•
Mia Arts
•5 min read•beginner•
--
•View Original

Overview

The article discusses how the GitHub Accessibility leadership team conducts inclusive retrospectives to ensure participation from all team members, including those with disabilities. It highlights the tools and processes used to create an accessible environment for retrospectives, emphasizing the importance of adapting traditional methods to meet diverse needs.

What You'll Learn

1

How to set up inclusive retrospectives using GitHub Issues and Discussions

2

Why accessibility matters in team retrospectives

3

How to facilitate discussions that engage all team members, including those with disabilities

Prerequisites & Requirements

  • Understanding of retrospective formats and their purpose
  • Familiarity with GitHub Issues and Discussions(optional)
  • Experience facilitating team meetings or retrospectives(optional)

Key Questions Answered

How can retrospectives be made more accessible for team members with disabilities?
Retrospectives can be made more accessible by using tools like GitHub Discussions, which support threaded conversations and voting on comments. Additionally, providing clear navigation and using appropriate Markdown formatting helps ensure that all team members can participate fully, regardless of their abilities.
What tools does the GitHub Accessibility leadership team use for retrospectives?
The GitHub Accessibility leadership team primarily uses GitHub Issues, GitHub Discussions, Zoom, and Slack for their retrospectives. These tools are chosen for their accessibility features, allowing team members with disabilities to engage effectively.
What are the key components of an inclusive retrospective setup?
An inclusive retrospective setup includes creating a GitHub Issue to house the retrospective details, using a tasklist for discussions, and ensuring that all participants can contribute ahead of time. The use of a structured format, like the Starfish retrospective, also aids in organizing feedback.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Collaboration Tool
Github Issues
Used to house retrospective details and discussions.
Collaboration Tool
Github Discussions
Facilitates threaded conversations and voting on feedback.
Video Conferencing
Zoom
Used for virtual meetings during retrospectives.
Communication Tool
Slack
Used for non-verbal communication during retrospectives.

Key Actionable Insights

1
Encourage participants to contribute to discussions ahead of time to enhance engagement.
This practice allows team members to reflect on topics and set expectations, which is particularly beneficial for neurodivergent teammates.
2
Utilize GitHub Discussions for retrospectives to facilitate accessibility.
GitHub Discussions allow for threaded conversations and voting, making it easier for team members who use screen readers to navigate and participate.
3
Implement closed captions during video calls to improve accessibility.
Closed captions help ensure that all participants can follow along, especially those who are hard of hearing or may miss verbal cues.

Common Pitfalls

1
Failing to provide clear navigation and structure in retrospective discussions can lead to confusion and disengagement.
Without clear headings and organized content, team members may struggle to follow discussions, particularly those using assistive technologies.
2
Not allowing enough time for participants to review materials before the retrospective can hinder effective participation.
When team members do not have time to prepare, it can lead to less meaningful contributions and a lack of engagement during the meeting.

Related Concepts

Inclusive Design Principles
Accessibility In Software Development
Team Collaboration Techniques