[SPIKE] CMS Collab Cycle - Discovery for QA

[gracekretschmer-metrostar]

User Story or Problem Statement

Determine if/how CMS can leverage the existing collab cycle for QA standards and where the CMS team wants to add their own QA standards into the process.

Steps for Implementation

• Review current Platform Collab Cycle
• Review the Collab Cycle that was being used in the CMS team
• Meet with Platform QA lead and Sitewide/Facilities Accessibility team
• Produce report detailing findings, next steps, and recommendations

Acceptance Criteria

• We have a direction to move forward with integrating into the Platform Collab Cycle from the QA standpoint.
• We have communicate changes to impacted teams (facilities and PW).

[gracekretschmer-metrostar]

Note to self: get this ticket refined and have it mirroring the collab cycle accessibility review: #17442

[gracekretschmer-metrostar]

Due date: have completed by DC offsite trip in June

[keisterj-oddball]

@gracekretschmer-metrostar Can you give this page a read when you have time? These are my findings and suggestions for a first pass with CMS QA in the collab cycle.

[gracekretschmer-metrostar]

Next steps:

1. Refining the confluence page, based upon feedback from Erika and Grace.
2. Getting review from Shira/Governance team.
3. Move content into Github (need to determine where).
4. Present to work to sitewide teams.

[keisterj-oddball]

Next steps:

1. Refining the confluence page, based upon feedback from Erika and Grace. - ✅
2. Getting review from Shira/Governance team. - Pending
3. Move content into Github (need to determine where). - ✅
   CMS Collab Cycle README
4. Present to work to sitewide teams. - ✅

[gracekretschmer-metrostar]

Thanks, Jon! I am going to get the Governance Team's review represented in a new ticket and I consider this closed. Great work!