|Seth Engelhard||Engineering Manager, Monitor Health|
|Peter Leitzen||Senior Backend Engineer, Monitor|
|Sarah Yasonik||Backend Engineer, Monitor|
|Clement Ho||Frontend Engineering Manager, Monitor Health|
|Simon Knox||Frontend Engineer, Monitor Health|
|Tristan Read||Frontend Engineer, Monitor Health|
|Laura Montemayor||Frontend Engineer, Monitor Health|
|Olena HK.||Senior Frontend Engineer, Monitor Health|
|Achilleas Pipinellis||Technical Writer, Create, Package, Monitor, Secure, Defend|
|Amelia Bauerly||Product Designer, Monitor & Package|
|Sarah Voegeli||Senior Product Designer, Monitor & Package|
|Ahmad Sherif||Site Reliability Engineer, Manage, Monitor & Configure|
|Amarbayar Amarsanaa||Senior Site Reliability Engineer, Create, Plan, Monitor|
|D.H.||Senior Product Manager, Monitor:APM|
|Sarah Waldner||Product Manager, Monitor:Health|
|bg||Product Marketing Manager, Monitoring, Create|
This team maps to the Health Group category and focuses on:
The purpose of our async standups is to allow every team member to have insight into what everyone else is doing and whether anyone is blocked and could use help. This should not be an exhaustive list of all of your tasks for the day, but rather a summary of the major deliverable you are hoping to achieve. All question prompts are optional. We use the geekbot slack plugin to automate our async standup in the #g_monitor_standup channel.
While we try to keep our process pretty light on meetings, we do have a few recurring meetings to keep in sync and to keep our backlog in good shape. We hold the Monitor Group Weekly Meeting to discuss agenda items that have been added over the course of the week and to walk through our current issue board together.
There is also an optional Monitor Social Hour meeting every week. This call has no agenda and alternates times every other week to be more inclusive of team members in different time zones.
Our goal is to move towards a continuous delivery model such that the team completes tasks on a weekly basis. In our weekly meetings, we prioritize grooming our backlog to prioritize specific issues that are ready for development. Every release, the product manager will collaborate with the team to identify notable features that we want implemented. These issues will be shared in the product kickoff call and will have a frontend engineer assigned to them before the development milestone starts.
The development of these assigned issues should not typically last the entire release cycle. Once frontend engineers have completed their assigned issue, they are expected to go to the Health issue board and assign themselves to the next unassigned issue in the list that has the
workflow:ready for development labels. The issues in the board are prioritized based on importance (the lower they are on the list, the lower the priority). In the event that all issues are assigned for that milestone, frontend engineers are expected to assign themselves to issues on the next milestone on the issue board list.
The frontend group also has a kickoff issue each release to help frontend engineers get visibilty to the work of other frontend engineers asynchronously. In this issue, it is recommended to only comment on the assigned issues as those are the primary issues that the team has committed to at the time of the kickoff issue.
Just like the rest of the company, we use PTO Ninja to track when team members are traveling, attending conferences, and taking time off. The easiest way to see who has upcoming PTO is to run the
/ninja whosout command in the
#g_monitor_standup slack channel. This will show you the upcoming PTO for everyone in that channel.