Ops Section PI Review : September
📖 References
🎯 Intent
✅ Tasks
⭕ Opening Tasks
-
Set a due date to this issue as 2 business days prior to the scheduled review to make time for Leadership async review - @kencjohnston -
Add a restrospective thread to this issue - @kencjohnston -
Update the Meeting Notes with the timing and this Prep Issue -
Coordinate with KT on this issue regarding when the content will be ready for leadership review -
Put a block on your calendar for Section Leader Review - @kencjohnston -
Review the update actions and ensure they are accurate per the Data definitions - @kencjohnston
✔ Other Tasks
-
Check remaining follow ups from last review - @kencjohnston
⭐ Performance Indicator YAML Updates
Each product stage or group should update the Ops Section Performance Indicators YAML file inline with the Data properties for all PIs each month, including:
- Update your
health:
bothlevel:
andreason:
with your progress and likelihood of reaching yourtarget:
- Review your
definition:
to include both what specifically is being measured and the rationale for why you chose that measurement - Review your
target:
to ensure it is updated, appropriate, ambitious and highlights why you have the expected growth rate, particularly in relation to GitLab's UMAU growth rate. - Update your
health:
level andimplementation:
status - Update any
funnel:
to reference stage/group direction or handbook page for the growth model and funnel - Update any
urls:
to reference additional Sisense dashboards for more details - Update
lessons:
learned:
withInsight -
prefixed comments about insights gained from the last month of data - Update
lessons:
learned:
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:
underimplementation:
.
Note - These instructions are based off of current understanding of the values defined in the Data section for Performance Indicator pages. They may change.
Group Updates
-
Update Section Wide - @kencjohnston - MR - www-gitlab-com!90898 (merged) -
Update Verify:Pipeline Execution - @jreporter - MR -
Update Verify:Pipeline Authoring - @dhershkovitch - MR -
Update Verify:Runner - @DarrenEastman - MR -
Update Verify:Testing - @jheimbuck_gl - MR -
Update Package - @trizzi - MR -
Update Release - @kbychu - MR -
Update Configure - @nagyv-gitlab - MR -
Update Monitor - @abellucci - MR
📦 Pre-Meeting Tasks
-
Consider pre-recording an overview - @kencjohnston -
Ask questions in the doc - @kencjohnston -
Ping KT to confirm content is ready for review in the doc -
Share the upated PI handbook page in the #ops-section and #product Slack channels 2 business days in advance of the review and encourage async participation - @kencjohnston
🌃 Post-Meeting Tasks
-
Capture actions discussed in the review in the follow-up actions section
❌ Closing Tasks
-
Create issues for any uncompleted follow-up-actions -
Make adjustments to the template based on the retrospective thread - @kencjohnston -
Add a highlights comment and share in Slack - @kencjohnston -
Update the link in Exciting Things to the new highlights comment - @kencjohnston
Follow Up Actions
-
ACTION @
Edited by Kenny Johnston