Build out documentation on team level roadmaps

[andreahewitt-odd]

Description

Now that we've moved to Zenhub for the overall platform roadmap, the overall roadmap we provided in Q2 doesn't do a great job of seeing team by team roadmaps.

To solve that painpoint, we need teams to leverage their space to build out team level roadmaps. Here's Service Design team's roadmap as an example.

Acceptance Criteria

• [ ] Documentation is written
• [ ] Documentation is socialized and PMs are given the opportunity to ask questions
• [ ] Each Platform team has a ticket in their backlog to build out their Q3 roadmap to practice
• [ ] Documentation is integrated into the playbook

Subject Areas

• [X] Product
• [ ] Design
• [ ] Engineering
• [ ] OCTO-DE

[andreahewitt-odd]

Page to draft ideas: https://vfs.atlassian.net/wiki/spaces/PMCP/pages/2281603357/WIP+-+Team+level+roadmaps

[little-oddball]

Would love to discuss this more. To me, the team roadmap should be a derivative of the overarching roadmap of the platform. Those initiatives shape the main focus of what the teams would be striving for but are laid out a little closer to home, from a work to be performed standpoint. This wouldn't be the minutia, which is handled more at the grooming and sprint planning level, but major focus blocks of an implementation of a specific item to be worked.

[andreahewitt-odd]

@little-oddball I have a rough draft here if you wanna check it out: https://vfs.atlassian.net/wiki/spaces/~534593234/pages/2332852886/Team+level+roadmaps

[andreahewitt-odd]

@raywangoctova @lhelmer @jwoodman5