August Sprint Retrospective

The training Team works in monthly sprints. At the end of each Sprint, we ask ourselves the following questions. Below is a compilation of the responses from the team following the retrospective discussions held in the #training SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel:

What went well?

  • Considerable content in multiple languages shipped.
  • Additional long-time contributors are rejoining.
  • SMEs started working in collaboration.
  • We established some helpful security measures for Online Workshops to protect our facilitators and attendees from disruptions/Zoom bombing.
  • We had our first Online Workshop in Japanese. And many more to come in other languages.
  • We made some good steps to update onboarding and process documentation.
  • The decision to move the APAC meeting time was a good one.
  • Individual Learn survey is live now after so much wait and dispute

What could we improve?

  • We have more meetings (beyond routine weekly team meetings) and less availability to create content.
  • We still need course creators’ input on how to revise the content for any feature changes in WordPress. Unfortunately, we don’t have a process for that yet.
  • The course updating content is also weighing on my mind.
  • We could continue building the handbook so contributors have more precise guidance.
  • We should work on clear guidelines for new joiners, especially for basic and Intermediate-level contributors.
  • We can improve how we use GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner., but as far as I know, we are already working on this.
  • We can improve how we use GitHub for courses.

What will we do differently?

  • Reducing the number of meetings will help. Rotating team meetings to every other week and keeping faculty-related meetings to that regularly scheduled time will also help.
  • We could use the team blog more for in-depth discussions (maybe reducing the need for synchronous/zoom meetings?) and keep topics that are quick discussion points in the weekly meetings.
  • We can have a Call for an Audit and content update for the upcoming WordPress 6.1 version. So other contributors can also help us in auditing, updating and delivering content at the time of the 6.1 release.
  • We can perform a sprint sweep at the end of the month and assign specific issues to the Sprint.