Growth/Team/Chore list

The chores table can be seen here.

Chore Norms

 * If you encounter something during chores that needs immediate attention post to #growth-engine-room or #growth-team on Slack
 * Noteworthy incidents should be added to Growth/Engineering/Incident tracking; when in doubt about whether to list something, ask the team.
 * When you file a task in response to reviewing Logstash or Grafana, please note the task in the "notes" column on the Growth/Team/Chores page.
 * If it's your chore day, but you'll be away, don't worry about it. Someone will pick up chores the next day on rotation.
 * If you'll be away for a long time (weeks and weeks, e.g. sabbatical or health reasons), talk to the team about it. A train day might also be relevant.
 * Chores are timeboxed to 45 minutes! Don't overdo it.
 * When in doubt, file a phab task (with @ mentions to teammates) and if it's urgent, also comment in #growth-engine-room or #growth-team
 * Feel free to suggest adding or removing chores on the team list.

Logstash

 * Are there errors that don't have phab tasks? If so, create phab tasks and ping team. Our aim is to have an empty dashboard.

EventLogging validation errors

 * Are there errors that don't have phab tasks? If so, create phab tasks and ping team. Data validation errors are urgent issues for our team, because we heavily rely on instrumentation to validate our work.

Link recommendation service

 * Are there errors that don't have phab tasks? If so, create phab tasks and ping team. Our aim is to have an empty dashboard.

Triage / Tidy

 * Rapid triage of inbox tasks in #growth-team workboard
 * The task should move into one of:
 * "Triaged" – This column signifies that our team (usually just the individual doing triage) has looked at the task. It doesn't mean that the task will get done, or that it won't get done. It just provides an indicator to others that someone has looked at it. You are welcome to write some kind of response if you wish. Most tasks will end up in this column.
 * "Needs discussion / analysis" – our team needs to talk about it, either in a meeting or via chat, before deciding what to do. If the task contains direct questions from community members that are not straightforward to answer, it should go in this column so that we can figure out how to respond.
 * "Current sprint" – Something is on fire (e.g. production error) and our team is responsible – place into current sprint. Document on the chores page that you've moved that task.
 * Steps:
 * Take a quick look at the tasks in the Inbox column and complete the following actions:

Processing the Needs Discussion / Analysis column
If there are more than 5 open task threads in the #growth-team-task-discussions channel, then:


 * Check the open threads and if you are supposed to respond, please do; if someone else is supposed to respond but hasn't yet, consider a ping or asking if more information is needed. Double check that the task has information about impact/severity and level of effort.

If there are fewer than 5 open task threads in the #growth-team-task-discussions channel, then visit the "Needs Discussion / Analysis" column and do this for each task until there are up to 5 open task threads in #growth-team-task-discussions:


 * If the task hasn't progressed out of "Needs discussion" in 30 days, move it to "Triaged"
 * Does the task description contain information about 1) impact / severity, 2) level of effort, 3) decision maker(s)? If not, please add.
 * Is there a thread for this item in #growth-team-task-discussions? If not, create one.
 * If the last comment on the task is asking a question and there hasn't been a response in one week, please ping those people in the thread

Link recommendation service

 * Look at charts. See if there are any unusual spikes. If so, make a task and document this on the chores page, and ping the team on chat.

Special:Homepage / Suggested Edits

 * Look at charts. See if there are any unusual spikes. If so, make a task and document this on the chores page, and ping the team on chat.

Misc

 * Follow up on Technical Forum requests for feedback (in theory weekly, but they have been less frequent so far) (Gergő)