|Seth Engelhard||Engineering Manager, Monitor:Health|
|Peter Leitzen||Senior Backend Engineer, Monitor:Health|
|Sarah Yasonik||Backend Engineer, Monitor:Health|
|Vitali Tatarintev||Senior Backend Engineer, Monitor:Health|
|Allison Browne||Backend Engineer, Monitor:Health|
|Sean Arnold||Backend Engineer, Monitor:Health|
|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|
|Ahmad Sherif||Site Reliability Engineer, Manage, Monitor & Configure|
|Amarbayar Amarsanaa||Senior Site Reliability Engineer, Create, Plan, Monitor|
|Dov Hershkovitch||Senior Product Manager, Monitor:APM|
|Sarah Waldner||Product Manager, Monitor:Health|
|Nadia Sotnikova||Product Designer, Monitor|
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_health channel. Every team member should be added to the async standup by their manager.
While we try to keep our process pretty light on meetings, we do hold a Monitor Health Backlog Grooming meeting weekly to triage and prioritize new issues, discuss our upcoming issues, and uncover any unknowns.
In our group, the (frontend + backend) engineering managers are responsible for adding the
~deliverable label to any issues that the team is publicly stating that to the best of their ability, they expect that issue to be completed in that milestone. We are not perfect but our goal is that 100% of the issues with that label do ship in the release that they are scheduled in. This allows engineering to share what issues they commit to and helps set expectations for the product manager and for the community.
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.
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.