June & July 2022 Sprint Retrospective

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 https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel:

What went well?

  • Training team goals and strategy call – Faculty members meet once a month to discuss the progress.
  • Lots of Online Workshops are running on Learn WordPress Online Workshop meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. group.
  • The development roadmap post seems to have gathered a lot of good feedback and should provide us with a great list for future development content.
  • New Faculty members joined our team and doing a fantastic job.
  • Our #training channel is now 24 hours awake. People are joining from different timezones, and there is always someone to answer questions that are being asked.
  • Other locale content is also available on Learn WordPress. We had our first Greek Lesson Plans published.
  • A great deal of content was created and published.
  • Conversations and sorting through a lot of logistics about how our team creates.
  • PR submitted for Lesson Plans landing page.
  • Work is continuing on the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Theme Creation course. and a public frame for the overall block theme (low-code) course was created, with complete lesson objectives and linked lesson plans, and the frame for each lesson plan is in Learn now. That went really well and It will allow people to submit course frames of their own in the future.

What could we improve?

  • Finish the 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. https://github.com/ automation/actions soon, so contributors can find it easily.
  • Team role implementation, so new contributors will also have a clear picture of their assigned task, it would be helpful when faculty size increases and new faculty members will join our team.
  • Tutorials in different languages will help more people across the world.
  • Additional online workshops in APAC-friendly time zones are a great way to get more involved.
  • We can ease the onboarding process for newcomers and beginners.
  • Identify a few faculty members for welcoming duties.
  • We can set priority on Github issues more precisely and the Role of a GitHub Wrangler is becoming more important now as we get more contributors. Having a few folks who can focus on sorting GitHub issues consistently would be beneficial.
  • We still need to ship the individual learner survey.
  • Creating a formalized Needs Analysis survey.
  • The training team needs more people in the copy editor, reviewer, and auditor roles. More folks ready and excited for those roles are probably the next step to getting content moving smoothly from draft to published.
  • As a team, we cited potential blockers and data metrics we would like in our annual goals. We are unsure of the progress on the data metric sources. and would like to be more data-driven in our decisions for larger changes. 
  • We would love to see more wranglers for specific team roles. So our new contributors could know the point of the contact person.
  • We would like to see more synchronous interactions outside meeting times. and would love if folks working on courses had a set time (time zone dependent) to gather and exchange ideas and feedback before submitting for a formal pre-publishing review.
  • Making the post more visible, perhaps as part of the weekly meetings or when onboarding new folks would help too.
  • It would be excellent to have onboarding videos/lesson plans for each role.
  • More than one contributor will work on tutorials. Like someone will write the script, another will record than another help in editing this someone else will finish making this pretty.

What will we do differently?

  • An innovative way to present lesson plans and make concepts looks easy with examples and scenarios.
  • Call for content creation/review or run Online Workshop.
  • We should run more onboarding processes in different time zones, so more contributors can be onboarded to help us.
  • Something like primary, secondary point of contact. When the primary is not available secondary can take over.
  • Onboarding Online Workshops for the roles.
  • Work with #meta on tracking contributions.