FY24 Q3 - Delivery:Orchestration Retro action tracker

This issue is a working issue to allow us to track progress against our retro actions throughout Q3.

Retro issue - FY24 Q2 Retro - Delivery:Orchestration (#19509 - closed)

The actions

1. Record (privately, or in a demo/Delivery weekly sync) and share at least one demo per epic. The goal is to become more proactive at knowledge-sharing content in an async-friendly format.
2. Make time every week to watch the Grand Review and read the project statuses on Release Velocity (&170) - and ask clarifying questions on the epic/issue. The goal is to prioritize time each week to review available Delivery Group information to stay informed.
3. Proactively reach out to collaborate with @swiskow on a delivery project or improvement (this may be by helping Sam with one of his tasks or bringing him into OKR work. Or, if time allows, starting a new Delivery Group improvement). The goal is to continue building effective working practices with Sam. I'm leaving this one generic because time or project constraints may require different ways of working. Let's try some things and out see what works best.

Progress tracker

Use this section to share actions & wins against our actions:

• Demo recorded and shared for Experimentation to reduce downtime of Dedicated... (&1092 - closed) - Demo
• Demo recorded and shared for Update Delivery tools and processes to support ... (&1039 - closed) - Demo
• Demo recorded and shared for Reduce Security release preparation to less tha... (&1061 - closed) - Demo
• Demo recorded and shared for Automate combining bug fixes and security fixes... (&1073 - closed) - Demo
• Setup PM office hours & post in #g_delivery (slack)
• ...
• ...