Product Intelligence Weekly Team Update 2022-06-06
Hello @gitlab-org/growth/product-intelligence
this is the weekly update issue for YYYY-MM-DD
Please read through the issue description check the items marked with Action required : and unassign yourself after you have finished.
🌻 General
🎈 Team day 2022-06-10
We have a team day scheduled for Friday 2022-06-10, we are all invited and welcomed to attend o the social sessions https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/625
🚒 Triage schedule
Action required : PLease review Triage schedule and add yourself when is the best time for you, by opening an MR to the handbook page.
⭐ Highlights
📗 Product Intelligence Knowledge Share [Incubation Engineering]
This week we have the Knowledge sharing for the Incubation Engineering group, see the event details
📓 Handbook updates
- Check out the Getting started guide added by
@michold
, this might be interesting read. We can also recommend this page when we get questions related with How to instrument metrics, what tooling to use. - Adding knowledge sharing content to HB (gitlab-com/www-gitlab-com!105159 - merged)
- Add issue template for ServicePing monitoring (gitlab-org/gitlab!85778 - merged)
🗓 Milestone Planning
- The current milestone is progressing nicely, with all issues except one deliverable issue assigned to an engineer.
- The 15.2 issue board is updated and ordered by priority for your reference.
- If you are looking for more work, please feel free to pick from the 15.2 board, starting at the top of the list if possible.
- We are starting this week with the async estimations, for the unweighted issues.
🔮 Product
- I've invited a few groups to share their knowledge with us (example), please champion the same with folks you interact with outside of Product Intelligence group.
- I'm closing the May Think Big issue this Friday. If you have any ideas to contribute, please add them. We already have great comment threads in the issue with several opportunities we can pursue!
-
🍿 Sneak-peak into June Think Big! In our next session, we'll brainstorm opportunities to prevent new code from disrupting existing event instrumentation.
Edited by Alina Mihaila