Monthly Dev Section PI Review : September
📖 References
🎯 Intent
We are organizing for and regularly reviewing Performance Indicators (PIs) in order to enable a dialog between ourselves (all of R&D) about most effective use of our R&D efforts towards the most impactful improvements.
As a communication tool, Performance Indicators are only as useful as the range of the audience. As a result we should:
- store PI metrics, funnels, growth models, status and next steps handbook first (avoid content only living in slides)
- expose our product groups to PI metrics regularly
- communicate transparently about adjustments to PIs within our groups
- reference PIs in planning issues and prioritization discussions
Additional data that we review:
- Error Budgets
- Security Burndown and compliance to our SLA
- S1/S2 SUS impacting burndown
- Issue Type Prioritization table to review how we are spending our time
PM responsibility
- Open an MR against the dev_section.yml. Review the following metrics and update the yaml attributes.
- Group's focus
- Analyze monthly user activity
- Lesson Learned
EM Responsibility
- Open an MR against the dev_section.yml. Review the following metrics for the most recent calendar month and update the yaml attributes.
- Error Budgets
- Security Burndown
- Reliability
- Review the Issue Type Detail and Merge Request Type Detail charts.
- Did we make the right investments in Engineering, UX, and Quality?
- Explain trends if any exist (e.g. spending 50% of investment in one area).
UX Responsibility
- Review and report on:
- S1/S2 overdue SUS impacting issues. Add report to PI monthly meeting agenda.
QEM Responsibility
- Review and report on:
- S1/S2 OCBA - Open Customer Bug Age
✅ Tasks
⭕ Opening Tasks
-
Adjust issue title - @justinfarris -
Set a due date to this issue as 3 business days prior to the scheduled review - @justinfarris -
Link state of the data issue - @justinfarris -
Add a retrospective thread to this issue - @justinfarris
⭐ Performance Indicator YAML Updates
Each product stage or group should update the Performance Indicators YAML file with the following changes to yaml attributes. Product Managers
- Update your
health:
andinstrumentation:
levels - Update any
urls:
to reference stage/group direction or handbook pages for the rationale, growth model and funnel - Update any
urls:
to reference additional Sisense dashboards for more details - Update
health:
reasons:
withInsight -
prefixed comments about insights gained from the last month of data - Update
health:
reasons:
withImprovement -
prefixed comments about planned improvements to reach your goals over the next month - If there have been recent updates to the definition, rationale, growth model, funnel highlight those and include those as
reasons:
underhealth:
- If you don't have a defined metric, rationale, growth model or funnel in the handbook reference issues for creating those and provide status on blockers in the
reasons:
underinstrumentation:
.
⭐ Expectations for Product and Engineering
- Ensure your graph is refreshed
- Ensure your graph looks correct and if it's not, understand why and change it
- Have a comprehensive understanding of your graphs (understand history, challenges with the data, etc) and document directly in the .yml file
- Ensure there are no graph labeling or title errors
- Ensure you have a target set and you know how that target was set. If you can't have a target, in the target field, please explain why you don't have a target and when you would expect to have one.
Group Updates
Section
-
Section TMAU - @justinfarris
Manage
-
Overall Manage Review @uchetta @m_gill | MR -
Authentication and Authorization -
Import and Integrate -
PM @m_frankiewicz -
EM @wortschi | MR
-
-
Foundations -
PM @cdybenko - MR -
EM @samdbeckham - MR
-
Plan
-
Overall Plan Review @mushakov @johnhope -
Project Management -
PM @gweaver | MR -
EM @donaldcook
-
-
Product Planning -
PM @amandarueda | MR -
EM @kushalpandya | MR
-
-
Optimize -
PM @hsnir1 | MR -
EM @blabuschagne | MR
-
-
Knowledge -
PM @mmacfarlane | MR -
EM @johnhope | MR
-
Create
-
Overall Create Review @derekferguson @dsatcher -
Source Code -
PM @derekferguson -
EM @sean_carroll
-
-
Code Review -
Editor
Quad Review
Section
-
Overall Section Review - -
Engineering - @timzallmann -
Quality - @at.ramya -
UX - @tauriedavis -
UX - @mvanremmerden
-
Manage
-
Overall Stage Review - -
Engineering - @m_gill https://gitlab.com/internal-handbook/internal-handbook.gitlab.io/-/merge_requests/3424 -
Quality - @at.ramya -
UX - @chrismicek
-
Plan
Create
-
Overall Stage Review - -
Engineering - @dsatcher -
Quality - @at.ramya -
UX - @andyvolpe
❌ Closing Tasks
-
Make adjustments to the template based on the retrospective thread - @justinfarris -
Activate on any retrospective thread items - @justinfarris
Edited by Urvi Chetta