Create documentation in Confluence for CMS Collaboration Cycle Kickoff Step

[BlakeOrgan]

User Story or Problem Statement

Now that we have a solid starting point for the CMS Collab Cycle Kickoff Request as a part of ticket 15438, we need documentation that goes further into detail around this particular step of the CMS Collab Cycle that is only accessible for the CMS team and explains what our responsibilities are in this step of the process.

Description or Additional Context.

• Here is a link to Collaboration Cycle Kickoff documentation from Platform that we can use for guidance.
• Here is a link to a mural that Platform uses to determine which touchpoints to recommend that we can use as guidance.
• Here is a link to the CMS Team's documentation repo in Confluence. This is where we will need to house documentation relating to the CMS Collab Cycle that is only accessible by the CMS team.

Acceptance Criteria

• Confluence is updated with documentation for the kickoff step
• Confluence links out to the the kickoff ticket template that was updated in ticket 15438.

Team

Please check the team(s) that will do this work.

• CMS Team
• Public Websites
• Facilities
• Accelerated Publishing

[BlakeOrgan]

An internal draft of documentation has been created in our Confluence space that includes guidance on what the CMS team should do when a new collab cycle request comes through from a team that has submitted a request using the CMS Collaboration Cycle Request ticket template.

Note that this documentation will continue to be a work in progress as we continue to establish our governance processes around the CMS Collaboration Cycle. It is modeled after the Platform Collaboration Cycle internal documentation, but it will continue to be customized to fit the needs of the CMS teams as we see fit. Steps that might still need edits as we establish our processes are noted with a warning panel and will most likely require additional ticketed work that would be assigned to the appropriate practice areas.