The correct answer is B - Align with stakeholder expectations and releasable product increments.
In Agile, sprint or iteration reviews provide an opportunity for the team to present completed work and validate it against stakeholder expectations. Demonstrations should showcase working, potentially shippable increments that align with business goals and value delivery.
From the PMI Agile Practice Guide:
"The purpose of iteration reviews is to showcase a working product increment. The review should focus on what was completed and how it aligns with stakeholder expectations and business objectives." (PMI Agile Practice Guide, Section 3.5 - Iteration Review) PMBOK Guide further reinforces this point:
"The team should deliver functional product increments that are valuable to stakeholders. These should be validated for alignment with scope and business value." (PMBOK Guide, 6th Edition, Section 5.5 - Validate Scope) Mike Griffiths notes:
"Product demonstrations should confirm stakeholder needs are being met. The team's focus should be on verifying value delivery, product completeness, and stakeholder alignment." (Mike Griffiths, Chapter 3 - Value-Driven Delivery / Stakeholder Feedback) Why other options fall short:
* A is valuable context, but doesn't directly ensure demonstration success.
* C reflects team improvement but is not the purpose of a product demo.
* D speaks to collaboration, not validation of stakeholder alignment.