May 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?

  • Items related to the release that we worked on and improved planning and joint working.
  • Tracking issues across GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ from the source in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo.
  • Launch of the Faculty Program.
  • Interaction between meetings and so many new faces are joining us.

What could we improve?

  • Finish the GitHub automation/actions to be more clear about what contributors can do.
  • Contribute to quarterly goals at least as much as release-related initiatives.
  • Call for Content Creation.
  • Fast track the content review and publish it soon, what we decided earlier in 2-3 weeks.

What will we do differently?

  • Start tracking Gutenberg issues that impact revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. this week.
  • Releases are not stacked right against an international WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. with all the prep for it. And contributor days right after release.
  • Organize a virtual zoom call (contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.) of 2-3 hours, to kick off the review and publish content part. And audit previous content for the latest release.

#retro

#meta, #retro, #training

April 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?

  • Updates to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ 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.

#retro

March 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:

What went well?

  • Additional contributors
  • TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. -> GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.
  • Content Development Github Workflow draft
  • Work on the quarterly (annual team goals) with GitHub migration and rough draft of a Needs Analysis started.
  • APAC meeting interaction with new contributors
  • A lot more contributors stepped up to create and revise content
  • 4 workshops were published thanks to @westnz and everyone that reviewed the workshops.
  • Reading the ‘What could we improve’, I am extremely impressed with the team reps’ ability to keep all these initiatives straight. Well done.
  • I did like last week how @Hauwa Abashiya changed up the sprint reporting structure to be a bit more direct touch by pinging responsible folks
  • Transferring everything to Github
  • I feel there has been more contributors getting involved.
  • Making direct contact with contributors and keeping in contact as time progresses.
  • New faces and contribution increases, thats an excellent thing
  • Social Learning Spaces. @Nick Diego has done a wonderful job since joining.

What could we improve? 

  • We’ve had a slow-down in content creation. Speaking for myself, global news + team administration have taken up most of my capacity.
  • Content has been claimed but not turned in in a timely manner, preventing others from contributing with that topic
  • Over committing to contribute.
  • Personally in last month I overcommitted tasks and couldn’t find time to work upon.
  • Finishing GitHub migration and automations will be really helpful
  • We can improve our handbook guide for new contributor, those like to contribute on creating a lesson plan they could find it in easy way
  • Team support on the Needs Analysis
  • Would be nice to have more clarity on priorities and prioritization process
  • Our check-ins, we need to directly ask people who have committed to working on content to provide an update on progress.
  • Streamlining our processes, reducing the amount of manual intervention.
  • Prioritising tasks for our Sprints.
  • Fixed timeline to publish content
  • Reaching out to get more contributors involved.

What will we do differently?

  • We can manage Monthly sprint in Github
  • Set a timeframe once a content topic is claimed until a draft is available, otherwise open it back up for others to claim. We used to do this as a team.
  • Roadmap for upcoming release 6.0
  • I will continue to try and work more in the open (and encourage people to pick up where I might leave off) if someone is like, “That’s cool, can I work on that too?”
  • Love the idea of opening a topic back up for others to claim, that’s a great idea.
  • YES PLEASE to that roadmap! :heart: That is one way I can prioritize what’s first, second, third.
  • Learn more about Github. I don’t know how it works yet :sweat_smile: And I need to learn!
  • I’m going to look into coffee hours, recaps and sprints for other teams to see what they do. 
  • I will try to work more in the open in 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/. :slightly_smiling_face:
  • Use the GitHub and features such as “milestone” to track actual progress.
  • Recruit more editors and encourage people not to over commit.
  • Provide better guidelines for content creation. Possibly:
    • 2 weeks to draft content – with weekly check-ins
    • 2 weeks for review and publish – with weekly check-ins
  • Maybe shortening the list for sprints.
  • We can chunk tasks in bunches, that way contributors can easily pick from their choices

#retro

Retrospective January 2022

Each month, the Training team works in Sprints. These are goals we hope to accomplish for that month. At the end of the month, we conduct a retrospective by asking ourselves these questions:

What went well? 

  • We shipped a lot of content related to the 5.9 release!
  • We had many new contributors proofread new content and revise existing content
  • Several lesson plans are nearly ready to publish
  • We attempted to ship content related to a release and I think we did well in getting the content there.
  • Timely lesson plans will be shared with 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. organizers in monthly newsletters for their use
  • Several courses launched, especially the Simple Site Editing
  • The team worked together on the 5.9 release was great. team collaboration is quite nice.
  • #forums has been suggesting the FSE course in support responses already to assist folks
  • Workshops related to 5.9 have been really useful for the community to get familiar
  • We were able to pull in new contributors to help.
  • Cross-team initiatives like coordinating with #marketing #docs #wptv and even #core with MarComms for this release
  • We coordinated very well on the release with #marketing #docs #polyglots
  • I’m really pleased to see all the new faces and new contributors. That’s been going really well, and it’s been lovely to get to review people’s lesson plans!

What could we improve? 

  • Easier process for onboarding contributors to Learn and revised roles for editing content on Learn
  • Create a checklist for proofreader to use when reviewing grammar, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) of content (including image alt tags) and more
  • Easier process for tracking contributions so that we can acknowledge them for their contributions.
  • Get the courses for contributors published on Learn so that no one person is depended upon as much for training
  • I dream of the day we can have comments in Learn with drafts
  • We can add more detailed docs in handbook, how to contributor can contribute.
  • Contributors user roles give them access to schedule/publish before content has been thoroughly reviewed. Concern. No fires this time.
  • Not all of our committed goals were achieved
  • We’re duplicating efforts by having similar content in Docs (particularly support articles), lesson plans, and courses.  With some engineering, perhaps we could have 1 source that is maintained and presented in each of those areas.
  • Being clearer on what is available for people to work on.
  • Make sure we address any accessibility needs.
  • Lesson plans created in Google Docs miss the primary template of content that standardizes lesson plans.  Also, it makes including media (particularly screenshots) challenging
  • We are not yet in parity with having a lesson plan matching every workshop
  • Match content revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. with TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. (or soon GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/)
  • We can manage lesson plan through Github as earlier

What will we do differently?

  • Review our commitments and expectations on having the content by a specific date.
  • Factor in additional goals beyond content as we work on the team’s quarterly goals as well.
  • Elevate more opportunities for new contributors and retaining contributors
  • Revisit @Sarah (She/Her)’s suggestion on running working sessions to help new contributors create lesson plans and workshops.
  • Utilize the Revisions Scheduled pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party further
  • Create a standardized faculty team feedback form when reviewing content for accuracy and vetting contributors

#retro