Evaluate and Modify Epic Workflow: EVSS PCIU Migration

[AshleyGuerrant]

Issue Description

During Sprint 15 (2024), this PR was being reviewed and there was a cascading effect because of changes that need to be made based on PR feedback and migration responsibilities for VFS teams.
As a result, the EVSS PCIU Migration: Remove calls to PCIU in global Pre-fill epic needs to be updated with what is learned from the PR feedback and VFS obligations. Although we migrated the base classes for VA Profile, certain parts of the codebase are owned exclusively by the VFS teams. It is their responsibility to handle the migration of these specific components.

The initiative is not fully blocked, and work can still continue on some of the tickets. The primary blocker is waiting on the VFS teams to migrate and test the components they own and we do not have any say over prioritization or sprint planning on their end.

An outline of the updated workflow has started on the EVSS PCIS Migration Workflow documentation.

Tasks

• Add ticket links to each step in the EVSS PCIS Migration Workflow documentation.
• Add PR links to any step that has a closed or open PR associated with it in the EVSS PCIS Migration Workflow documentation.
• For all tickets in the epic that are open, in the ticket title renumber them sequentially in the order that they need to be completed.
• For any ticket that can be worked on in parallel, in the ticket title label them with the same numeric but add a unique alpha (ex: 5a, 5b, 5c, etc.)
• Change the status of any ticket that currently cannot be worked on to "Blocked" and post a comment with a link to the ticket(s) that are blocking it.
• For all tickets in the epic that are open, add additional details in the Issue Description that provide background as to why the work is necessary and how that specific ticket relates to the larger body of work.
• Write up any new tickets that have been identified as necessary, after the learnings from the PR feedback, and attach them to the epic.

Acceptance Criteria

• A outline of the updated workflow, that numbers each step and has links to each associated ticket (and PR if one is associated to it).
• Renumbered tickets attached to the epic, that reflect the sequential order of each step and denote any tickets that can be worked on in parallel.
• Any ticket that cannot currently be worked on has the status of "Blocked" and a link to the ticket(s) that is blocking it is posted as a comment.
• Each open ticket includes background as to why the work is necessary and how that specific ticket relates to the larger body of work.
• New tickets are written up, so that the epic fully reflects all of the work that is known at this time to be necessary to complete the initiative.

---

Validation

• The epic is fully updated so that it reflects all of the work that is known at this time to be necessary to complete the initiative.
• The Product Manager has the documentation necessary to create a comprehensive milestone and estimated timeline document (see example here.

[AshleyGuerrant]

Sprint reporting note: This ticket needs to be injected into Sprint 16. Further details are provided in the issue description.

[RachalCassity]

Updated workflow and updated ticket numbering.

[AshleyGuerrant]

Excellent, thanks @RachalCassity!
@LindseySaari & I will review the workflow documentation and discuss during the PCIU meeting tomorrow. Moving this ticket to "in review" status.

[AshleyGuerrant]

Standup note: documentation is complete and has been reviewed. Closing this ticket.