To address a program showing separate Feature branches rather than a true System Demo, which practice should be reviewed?

The practice that should be reviewed in this scenario is Continuous Integration. In the context of SAFe, Continuous Integration is crucial because it ensures that different feature branches are regularly integrated into a shared codebase. This allows for the creation of a true System Demo, where all features work together as a complete system rather than as separate entities.

When Continuous Integration is properly implemented, it facilitates automatic builds and testing, making it easier to detect issues early and resolve them before they affect the integrated system. This practice supports the overall goal of delivering a cohesive product increment that includes contributions from various teams, allowing stakeholders to see how features function together in real-time during system demonstrations.

If Continuous Integration is lacking, teams might work in isolated feature branches without timely integration, resulting in a fragmented system demonstration that fails to represent the product's complete functionality. Thus, reviewing and strengthening the Continuous Integration practice will help ensure that the program showcases a unified System Demo rather than separate feature branches.