-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding New Accelorated Publishing Team #17506
Comments
gracekretschmer-metrostar
added
Epic
Issue type
Needs refining
Issue status
CMS Team
CMS Product team that manages both editor exp and devops
labels
Mar 13, 2024
35 tasks
We need to answer the question of how we want to represent AP work? For this sprint, we will keep AP + CMS together. |
30 tasks
Look into adding work into to both AP and CMS teams. |
31 tasks
28 tasks
Meeting recordings and notes here: https://docs.google.com/document/d/1LbJHlxeTk04VssN2VqiLINvZjHTkN9AQlJ1x6ZQpw88/edit?usp=sharing |
35 tasks
7 tasks
24 tasks
22 tasks
26 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Accelerated Publishing (AP) is a team that is implementing a new system (NextBuild) that will replace CMS' content build. The existing AP team will be ending their contract on 5/1 and be replaced by a new AP team, run by Oddball. As the new AP team comes onboard, the CMS Team needs to help support their onboarding and learning process.
User Story or Problem Statement
How may we retain as much knowledge and momentum from the outgoing AP team for the new AP team?
Affected users and stakeholders
Hypothesis
Through the CMS supporting the onboarding of the new AP team, they will gain knowledge about CMS through the AP team that will empower them to better show up in their roles on the CMS team.
Acceptance Criteria
Team
Please check the team(s) that will do this work.
CMS Team
Public Websites
Facilities
User support
Accelerated Publishing
Tasks
The text was updated successfully, but these errors were encountered: