Which guideline is considered an anti-pattern for the success of the system demo?

Inviting team members to the system demo is essential for several reasons. First, their presence fosters collaboration and collective ownership of the work being demonstrated. Team members have firsthand knowledge of the product increments and can provide detailed insights and context that can be critical for stakeholders to understand the functionality and value being presented.

By not inviting team members, a gap can form between those who built the increments and those who are evaluating them, potentially leading to misunderstandings regarding the product's capabilities. Additionally, this practice can diminish team morale and engagement, as contributors may feel disconnected from the feedback and validation process of their work.

Thus, excluding team members from the demo can undermine the overall effectiveness of the demo, hinder communication, and reduce the chances of getting valuable immediate feedback that could improve the product and inform future iterations.

In contrast, the other choices are related to various aspects of system demos that can be improved upon, but they do not represent the same level of fundamental misalignment with SAFe principles as excluding team members. Each of those alternatives can lead to suboptimal outcomes, but they do not create the same immediate barrier to successful collaboration within the team.