The correct answer is D - Break non-functional requirements into those that can be delivered in the given sprint. Agile teams apply the principle of incremental and iterative delivery not only to functional requirements but also to non-functional ones. Large or complex work-including non-functional requirements-should be decomposed into smaller, manageable items.
From the PMI Agile Practice Guide:
"Work items, including non-functional requirements, should be split to fit within a sprint's capacity. Teams use story-splitting techniques and prioritize parts that provide the most value or enable further development." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning and Story Sizing) Mike Griffiths reinforces:
"If a user story or requirement is too large for a sprint, it should be broken down. Even performance and security requirements can often be delivered incrementally." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Incorrect options:
* A ignores important non-functional quality attributes.
* B is not in line with agile's sustainable pace and team stability.
* C deflects ownership without attempting a solution.

In Agile, one of the key principles is to provide continuous feedback and integration throughout the development process, ensuring that components are tested, integrated, and iterated upon regularly. By separating the work into three teams that work independently and only integrate at the end, the strategy risks delaying feedback and potentially causing integration problems. This approach could lead to significant issues when the components are eventually integrated, as they may not work together as expected due to lack of ongoing collaboration and integration. Therefore, working in parallel with proper continuous feedback and integration is crucial in Agile to minimize risks and ensure smooth delivery.

The correct answer is A - Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.
Sprint reviews are designed to showcase the completed product increment to stakeholders and receive feedback. The primary goal is to validate that the work delivered provides value to the customer-not to present technical details. Demonstrating working software is one of the core tenets of Agile.
From the PMI Agile Practice Guide:
"Sprint reviews are working sessions designed to elicit feedback and foster collaboration. Teams demonstrate completed work and adjust the backlog based on stakeholder input." (PMI Agile Practice Guide, Section 5.3 - Value Delivery) Mike Griffiths confirms:
"The output of every iteration should be potentially shippable product. The sprint review is for stakeholders to see that output and provide feedback to inform future development." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 2 - Value-Driven Delivery) Other options explained:
* B may be helpful, but it doesn't solve the immediate issue of misaligned sprint reviews.
* C misunderstands the purpose of the sprint review-it's not about architecture.
* D changes the audience instead of correcting the approach.