Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the Support Steward role #187

Closed
6 tasks done
Tracked by #355
choldgraf opened this issue Aug 2, 2021 · 3 comments
Closed
6 tasks done
Tracked by #355

Define the Support Steward role #187

choldgraf opened this issue Aug 2, 2021 · 3 comments

Comments

@choldgraf
Copy link
Member

choldgraf commented Aug 2, 2021

Actions

@choldgraf
Copy link
Member Author

choldgraf commented Nov 10, 2021

Update: Feedback from last support steward debrief

@damianavila and I had a brainstorm session about his experience with the support steward, here were a few things we'd like to improve in our support steward docs:

  • Add language about the “support steward lifecycle” to our document, add a <24 hour turnaround with support. Something like
    • Target response time: <24 hours to respond (not to resolve) (and excluding weekends/holidays)
    • When you receive a ticket, communicate that you have received it and note the next steps you’ll follow to resolve it.
    • Give updates to the community as you work to resolve the issue
    • When it is resolved, tell the community what you’ve done to resolve the issue
    • In general, it is encouraged to prioritize support-related issues over development/backlog issues
  • Emphasize that it is about "communicating" and "routing".
    • But as support steward is router, people develop expertise in certain areas, and it's ok to route requests to such a person. Also ok to route something to someone if they were just working on it / were very active in that space. Must be balanced against making sure we don't pigeonhole people
  • Also language about tackling support issues that are created (like creating new hubs). These are auto-assigned to the support steward.
  • Events, and when the support steward needs to pay special attention to certain kinds of tickets
  • Update to be a 2 person team where one person rotates off every week
  • Clarify that the support stewards are the main point of contact for all support tickets regardless of the community - there is no community-specific support person, just the team
  • Make explicit that support steward has the right to ask others for help moreso than usual

@damianavila
Copy link
Contributor

Update to be a 2 person team where one person rotates off every week

I think the rotation would be every 2 weeks (to be in sync with the sprints) but still a 2 person team.
That means you will be serving in a support role for a month (2 sprints) but a 50% capacity since you will have a support partner.

@choldgraf
Copy link
Member Author

I'm closing this one, as the PR that defined this role has been merged, and we have other issues opened to discuss iterative improvements to the role!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants