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 Slack channel:
- EMEA/Americas Meeting – Retrospective Questions
- APAC Meeting – Retrospective Questions
What went well?
- Updates to GitHub to make it easier to navigate
- Prioritising and labelling of issues on GitHub to make it easier to identify what items are of high priority or quick fixes for new contributors
- GitHub activity now shows
- Taking feedback on GitHub issues during weekly meetings
- Lots of great interaction in Social Learning Spaces (SLS)
- Lost of collaboration around the training community GitHub is now easier to navigate, links filtered by priorities, version
- Collaboration with #meta on tracking Helpscout responses as part of contributing and triaging site functionality issues.
What could we improve?
- Create a few training pieces on how lesson plans and workshops evolve into courses
- Reaching out to new contributors by setting up the Faculty Program so we can involve more people
- Draft training needs analysis
- The team still faces challenges in creating content, it is hoped that this will be mitigated with the introduction of the Faculty Program.
What will we do differently?
- Work in the open as often as we can and set better deadlines
- Draft objective statement and assist new creators in getting started
- Draft a proposal or workflow for new releases – we can look at setting up Calls for Content Creation similar to Calls for Testing.