PO Onboarding
All new POs will go through PO Onboarding before they are officially the PO of their first component. PO Onboarding is led by Jonathan. Onboarding includes the following meetings and additional administrative updates:
-
PO Orientation
-
PO Curriculum
-
Introduction to PO Jira Automations
-
link:https://docs.google.com/presentation/d/1z0SImhb9aruL0_oDwrKuPbaMA--joQdS29tVU28HzuY/edit#slide=id.g15ede409963_0_149PO Onboarding Curriculum: Release Management]
-
Component Handoff Ceremony
-
Official PO Start Date
Slack Updates
POs will be added to the appropriate PO group for the project that they’re on. These groups are used to communicate upcoming meetings, get information for planning, and to communicate with one another.
-
CES: cesproductowners
-
CKM: ckmproductowners
-
SPL: tas-productowners
-
SRE: sreproductowners
You will also be added to an additional PO specific Slack channel: #va-product-owners
Calendars / Events
Please add the Product Owner calendar. This includes all PO events. Below are links to the associated Slack list for that PO call:
-
For all VA POs: PO Topics
-
Project specific meetings (see calendar(s) for most up to date list)
-
CKM PO Planning
|
Jonathan will review which events to attend and when during orientation. |
Jira Updates
-
POs are added to another group in Crowd with additional permissions:
-
CES: TASS-Admins
-
CKM, SRE: NGSS-Admins
-
SPL
-
VAOS: VAOSR-Admins
-
VCAS: VCAS-Admins
-
VSP: VSP-Admins
-
Acheron: ACH-Admins
-
Audit: AUD-Admins
-
-
-
Backlog items for that component are transferred to the PO’s backlog by the PM.
-
PM adds a new widget for the PO and their component(s) on their project’s Flexline Findings dashboard. See the Flexline Finding Process for more details
-
SPL dashboard - needs to be updated to be PO specific.
-
The PO is added as the owner of the component in the appropriate Jira workspace: