Last updated Mar 21, 2023
community success
.
#support
grew, we decided to have an on call engineer that will be available to respond, while working on the sprint tasks.
After a few weeks, we learned that this approach is pretty limiting. By only being reactive, we miss opportunities to help users get the most of Elementary. Also, small tasks that can be closed in minutes and users are waiting for are pending prioritization in sprint planning. Meanwhile, on days an engineer was on call, it was really challenging to make progress on the sprint tasks due to the constant context switching.
We decided to try a different approach: When you are on call you focus only on the community, and your goal is helping users succeed with Elementary.
Triage 👀
. Filter on this label and respond to issues. If you think the issue requires product scoping, respond that this is the case and change label to Product review
.
Product review
issues, and decides if each should be a sprint task, community backlog and / or open to contribution.Community
label and form the community backlog. If you have a relatively low #support
volume, you can work on a task you choose from this backlog.In Progress
. Generally speaking, we should aim that threads will be in this status as little as possible. If you are waiting for a reply from the user or still researching, this is the right status.#community-success
channel./pd oncall
on Slack.
What should I do during non-working hours?
Try to provide at least an initial reply. If you can reply and help, that’s great.
If not, don’t feel bad about it. Simply do the following:
“We would love to learn more about your use case! If you are willing to share, you can schedule a short call with Hadar who is leading to product by using this link -https://savvycal.com/Hadar-Sagiv/9e49a464”