Answer:
The correct answer is 3.
Team demos are accepted in place of a system demo to avoid redundancy.
Explanation:
1. System demo takes more than 15 minutes:
- While it’s important for system demos to be concise,
taking more than 15 minutes is not inherently an
anti-pattern. The duration should be sufficient to
cover all necessary aspects without rushing.
2. People from outside the Agile Release Train attend
the system demo:
- Involving stakeholders from outside the Agile Release Train (ART) can be beneficial as it provides broader feedback and ensures alignment with external expectations.
3. Team demos are accepted in place of a system demo
to avoid redundancy:
- This is an anti-pattern because the purpose of a system demo is to integrate and demonstrate the work of all teams within the ART. Relying solely on individual team demos can lead to a lack of integration and visibility of the overall progress and system functionality.
4. Different team members conduct the demo each
iteration:
- Having different team members conduct the demo can be a good practice as it promotes shared understanding and ownership of the work. It also helps in building presentation skills across the team.
- By ensuring that system demos are conducted properly, you can maintain transparency, alignment, and integration across the Agile Release Train.
