When an epic meets the GO criteria for no-go, where does the epic move to?

When an epic meets the GO criteria for no-go, it moves to the Portfolio Backlog. This is because the Portfolio Backlog primarily contains items that require further refinement or are awaiting prioritization based on strategic objectives and alignment with organizational goals. When an epic does not meet the necessary criteria to proceed, it's still essential to keep it tracked within the Portfolio Backlog for potential future reassessment or refinement.

In the Portfolio Backlog, epics can be reviewed periodically to determine if conditions have changed or if new information has emerged that might justify revisiting the decision. This allows for adaptability in the decision-making process, ensuring that the organization can pivot or adjust its approach as needed.

In contrast, moving the epic to other locations like the Team Backlog or Development Queue would not be appropriate since those areas are reserved for work that is actively being pursued or developed. The Retirement List typically serves for items that are considered no longer valuable or relevant, which isn't the case if an epic is simply not ready to proceed at this time. Thus, retaining the epic in the Portfolio Backlog for future consideration is the most suitable option.