2022 Q3 Console UI - Prepare Console for Handoff before Sept 9, 2022 for Platform Team Transition

[lhelmer]

Problem Statement

How might we make sure Platform teams picking up the work of Console UI after Q3 2022 are able to continue working on certain aspects of the Console?

Hypothesis or Bet

If we document the Console's process and implementation using Playbook documentation, we will prepare the Platform Teams for taking over this work.

We will know we're done when... ("Definition of Done")

Creating playbooks for:

• [x] Write documentation Catalog Onboarding Playbooks Epic 720
• [x] Write documentation for End User Playbook Epic 721 and 729
• [x] Write documentation for Health Metrics Playbook (GA) Epic 719
• [x] Write documentation for Design System Playbook Epic 718
• [x] Write documentation for Feature + Plugin Playbook Epic 513
• [x] Write documentation for Operations + Maintenance Playbook (Backstage, logging, hosting, etc) Epic 717

Complete before 9/9/2022

• [x] SSL certificate - As done as possible until Q4 #130
• [x] repo should be set as public open source policies - #11591
• [x] security.md file needs to point to policies - #172, #177, #13

Known Blockers/Dependencies

Testing may be limited if platform teams are unable to participate in giving feedback for our Playbook documentation.

Projected Launch Date

End of Q3 2022

Launch Checklist

Guidance (delete before posting)

This checklist is intended to be used to help answer, "is my Platform initiative ready for launch?". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given Platforminitiative. All links or explanations can be provided in Required Artifacts sections. The items that can be skipped are marked as such.

Keep in mind the distinction between Product and Initiative --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. VSP Product Terminology for details.

Is this service / tool / feature...

... tested?

• [x] User feedback of Console Plugin Playbook
• [x] User feedback of Operations and Maintenance Playbook
• [x] User feedback of Catalog Onboarding Playbook
• [x] User feedback of Console Health Metrics Playbook (GA)
• [x] User Feedback of Design System Playbook

... documented?

Documentation is the focus of this ticket. Below is the list

• Console Feaure + Plugin Playbook (multiple documents)
• Console Onboarding Playbook (multiple documents)
• Console Health Metrics/User Feedback Playbook (GA+Medallia) (multiple documents)
• Console Operations + Maintenance Playbook (multiple documents)
• Console Design System Playbook

Required Artifacts

Documentation

• PRODUCT_NAME: Console Product Playbooks
• Product Outline: link to Product Outline

Testing

See "Tested?" above

Measurement

There is no measurement for this initiative

[jchapin]

@lhelmer @ActualAbby it's possible to relate GitHub issues to each other simply by putting the URL after the checklist item. That will also automatically check the item off when the issue is closed. This is cleaner than re-tagging users.

[sdk-irl]

LInked epics for each Playbook. Still attaching tickets to sub epics