### Overview As per the [R&D Realignment](https://gitlab.com/gitlab-com/Product/-/issues/1698), this issue will serve as a tracker for the transition from Release:Release Management, Staff Product Designer to Verify:Testing & Runner, Staff Product Designer. There are also related issues that will serve as separate tasks. #### New allocation * 25%: Verify:Testing * 25%: Verify:Runner * 50%: Acting Product Design Manager, CI/CD ### Communication Plan & Timeline * Effective Date: 2020-11-18 * Announcement Date: 2020-11-03 #### New DRIs Product Designer duties for Release Management categories will move to the following DRIs: * @icamacho: Package will include Release Evidence * @icamacho: Release will include Release Orchestration and Pages * @mvrachni: Configure will include Secrets Management * @ameliabauerly: Monitor will include Runbooks See [Release Management UX](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/release-management/) for more information about categories. #### Timeline | Milestone | Description | | ------ | ------ | | [13.6](https://gitlab.com/groups/gitlab-org/-/milestones/53) | Wrap up Release Management work and hand over design deliverables to new DRIs | | [13.7](https://gitlab.com/groups/gitlab-org/-/milestones/54) | Transition into Verify:Testing & Runner. Take over [Verify:Testing](https://about.gitlab.com/handbook/engineering/development/ops/verify/testing/) and [Verify:Runner](https://about.gitlab.com/handbook/engineering/development/ops/verify/runner/) from Veethika. | | 13.7 | Veethika to transition back to Verify:Continuous Integration | #### November 2 - 6 * [x] Create transition issue * [x] Share issue with @vkarnes * [x] Share issue with relevant parties * [x] Make formal announcement on Slack (ci/cd and ops channels) and team calls #### November 9 - 18 * [x] Schedule syncs with Transition Parties. - @jreporter scheduled here https://gitlab.com/gitlab-com/Product/-/issues/1683 * [x] Transition any documents, open problem/solution validation. * [x] Transition any customer calls scheduled to PMs/Designers. * [x] Transition any design files and assets. * [x] Update team.yml and categories.yml * [ ] [Update Release Management UX page](https://gitlab.com/gitlab-com/people-group/Training/-/issues/927) #### November 19 * [x] Start attending Verify team calls. * [x] Schedule ramp up sessions with Verify PM and counterparts. ### Relevant links & resources * [Opportunity canvases](https://gitlab.com/gitlab-org/ux-research/-/issues/778) * [Competitive Analysis](https://gitlab.com/groups/gitlab-org/-/epics/2622) * [Figma: Release Management prototypes](https://www.figma.com/files/project/10643837/Stage-%E2%80%A2-Release-%E2%80%A2-Release-Managament) * [Dovetail: Release Management - topic calls](https://dovetailapp.com/projects/e921eddf-1800-4a69-a6fb-cc917e974f9d) * [Dovetail: Competitive Analysis - Launch Darkly](https://dovetailapp.com/projects/f1a6667e-ade3-4436-a022-78f1d166f1eb) * [Release Management UX Debt & UI Polish](https://gitlab.com/groups/gitlab-org/-/epics/3416) * [Usability of Releases](https://gitlab.com/groups/gitlab-org/-/epics/2355) * [Release (CD) UX YouTube channel](https://www.youtube.com/playlist?list=PL05JrBw4t0KoyqCjN4f79w0dYZusHLx15) * Current UX Backlog: See all [Ongoing Release Management UX work](https://gitlab.com/groups/gitlab-org/-/epics/2439) - I used this epic to collect issues that need UX and groom them together with PM/ENG. * https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/release-management/ * https://gitlab.com/gitlab-com/Product/-/issues/1683#relevant-documents