Weekly design triage

Weekly triage sessions are run 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/. every Tuesday 16:00 UTC and it is combined with 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/ triage. The goal of this is to within half an hour triage as much as possible, if it’s only a few that is also ok.

Reports Reports

There are 3 reports that need triaging during weekly design. Ideally pick one and focus on it.

Top ↑

Preparation Preparation

  • Choose one of the reports.
  • If there is a release currently in progress and about to head into betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. or ‘release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.’, make sure to highlight those tickets first in triage.
  • If you are using a report with ‘modified’ as a field, click it to start with oldest tickets.

Top ↑

Running triage Running triage

  • Open triage by saying: <triage> and if possible use ‘/here’ to announce start.
  • Introduce triage saying what is about to happen. You can say something like this:

Welcome to this triage session. In design triage the goal is to move on as many tickets as we can in this half an hour. This can be through closing, asking for more information or even a screenshot. Let’s get started!

  • Link the report you are using so everyone can follow along.
  • Pick the oldest ticket, open in your browser and then copy the link to share with everyone in Slack.
  • Give people a little time to read the ticket.
  • Ask if anyone has any ideas. If you have your own mention those.
  • Discussion should happen in Slack but once it seems to reach a point ask:

Would anyone like to update the ticket or shall I?

  • The ticket then can be updated and ‘moved on’ in a number of ways:
    • Giving feedback.
    • Asking for more information: this would be for example a screenshot.
    • If no feedback is needed then remove the keywords.
    • If feedback has been given add ‘has’ to the keywords. For example: ‘has-ux-feedback’.
    • Should this not be an issue anymore you can close, but this is rarely the case and usually your response is one of the above.
  • Congratulations you’ve triaged that ticket! Now onto the next and keep going until you reach 30 minutes.
  • Close out triage by thanking everyone and saying </triage>.

Last updated: