Skip to content
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

Shift CMS Sprints into Platform's Sprint Structure #19589

Closed
3 tasks done
Tracked by #19554 ...
gracekretschmer-metrostar opened this issue Oct 23, 2024 · 3 comments
Closed
3 tasks done
Tracked by #19554 ...

Shift CMS Sprints into Platform's Sprint Structure #19589

gracekretschmer-metrostar opened this issue Oct 23, 2024 · 3 comments
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops

Comments

@gracekretschmer-metrostar
Copy link

gracekretschmer-metrostar commented Oct 23, 2024

User Story or Problem Statement

As a team within the product team, CMS sprint reporting and structures need to shift to be in alignment with the platform team's sprint structure.

Relevant Links

Steps for Implementation

  • Move the sprint plans to be in alignment with how platform team structures sprint plans
  • Confirm the path forward for the CMS monthly reports with Jason and Andrea
  • Pull in platform templates for initiatives, epics, and tasks.
  • Restructure existing epics and initiatives to be in alignment with platform.

Acceptance Criteria

  • All current CMS initiatives and epics are in the platforms structure.
  • CMS sprint plan structure is in alignment with platform team.
  • CMS initiatives, epics, and task templates are in alignment with the platform team.
@gracekretschmer-metrostar
Copy link
Author

@LisaLindsey I confirmed with Erika that we don't need to continue doing the current structure for sprint plans (for example) and can move to platform's format for future sprint plans.

@gracekretschmer-metrostar
Copy link
Author

Erika pushed back on some of these reporting structures, so Grace is going to sync with Jason to determine next steps.

@gracekretschmer-metrostar
Copy link
Author

@LisaLindsey I synced with Jason and Erika about how to move forward and reflected the decisions back into the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops
Projects
None yet
Development

No branches or pull requests

2 participants