Create new, simplified visual of Collab Cycle touchpoints

[shiragoodman]

User Story

As a VFS team member, I want to visually see what touchpoints are in the Collab Cycle and how to flow through them so that I am able to meet the expectations of Platform.

Assignee: Peer Reviewer:

Description

With the introduction of the new PO Sync and the Architecture intent (along with the planned Engineering & Security track) we need to create a helpful visual aid for VFS teams to understand what touchpoints exist in the Collab Cycle, what track they're on (if any) and what phase of development they should occur in.

What features do we want to have included?

• ppl attending
• touchpoints
• track
• required?
  • still confusion on what's optional and what actually is required

Impacted Artifacts

Live pages

Drafted pages

Tasks

• [ ] Placeholder task

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] Placeholder AC

Team Notification

• [ ] Slack post on #platform-governance-team
• [ ] Presentation at Weekly Initiative Meeting
• [ ] No notification needed

How to prepare this issue

Refinement

• [ ] Ticket has user story, description, tasks, and acceptance criteria
• [ ] Ticket has been sized
• [ ] Once all above items are checked, add the 'Ready' label.

  Planning

  If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• [ ] Ticket has been discussed as a team at Planning
• [ ] Ticket has been assigned to appropriate initiative or quarterly epic
• [ ] Ticket has been assigned to a Sprint
• [ ] Ticket has been moved to the Planned pipeline in the Governance team board
• [ ] Ticket as an assignee and peer reviewer

[shiragoodman]

Shira's rough concept

[shiragoodman]

Comments from team on Shira's design:

• Don't like the 3rd column (Additional Services)
• CMS, Analytics and Contact Center can fit it whenever
• aligns with my idea of simplifying
• good start
• talk about phases and the phase names
• looks really "waterfall-y" - how can we make it more agile-looking?
• indicate required touchpoints with an asterisk? something small/easy. bold border or text.
• Do we want to indicate that steps can be repeated?
• from a dev perspective, blurring of the phases. sometimes you're testing and developing at the same time.
• agree with 3rd track. a little confusing.
• This is much easier to digest immediately than what came before.