This question belongs to the Process domain because it concerns agile delivery criteria and product completion rules. PMI's Disciplined Agile glossary defines the definition of done (DoD) as the criteria for accepting a feature or story as finished. PMI also notes that work that does not meet the team's definition of done is considered unfinished and does not count as delivered value. Therefore, the correct response is that items are complete when they satisfy the definition of done.
Option B is incorrect because the scrum master does not act as the formal approver of completed scope.
Option C is weaker because a demo may provide feedback, but completion is determined by meeting the agreed DoD, not just by demonstration approval. Option D is also incorrect because not every sprint outcome is automatically production-ready unless it meets the established definition of done and release criteria. PMI- aligned agile practice emphasizes shared quality criteria, transparency, and clear acceptance standards. That makes the DoD the best and most accurate answer for defining when deliverables are complete.

Trend analysis is a mathematical technique that uses historical results to predict future outcomes1. It is a project management quality control tool that tracks variances in cost and schedule performance2. In agile projects, trend analysis can help monitor the velocity, quality, and scope of the project deliverables3. A project risk register tracking tool and an issues log are two sources of historical data that can be used for trend analysis. A project risk register tracking tool records the identified risks, their probability, impact, and response strategies. An issues log records the issues that have occurred, their status, and resolution. By extracting data from these two sources, an agile project manager can perform a trend analysis of all the risks that the project has monitored over the past 12 months and provide insights to the project sponsor. The other options are not relevant to trend analysis. Sharing the annual report with the sponsor may not provide enough detail on the risks and their trends. Organizing a stakeholder meeting to brainstorm on general project risks may not reflect the actual data and outcomes of the project. Referring the sponsor to the contract document may not address the sponsor's request for trend analysis. References: 1: Trend analysis - Wikipedia3, 2: Trend Analysis [Technique] - Project Management Knowledge4, 3: Agile Project Management For Dummies Cheat Sheet - dummies

According to the PMBOK Guide, 6th edition, section 12.2.2.4, the project manager should use procurement documentation to define and manage the contractual relationships with the suppliers. Procurement documentation includes the contract, the statement of work, the procurement management plan, and the source selection criteria. The project manager should ensure that the project team, including the business analyst, is aware of the terms and conditions of the contract and the scope of work that the supplier is expected to deliver. Any changes or additions to the scope should be formally requested and approved through the change control process, as described in section 4.6. The PMI-PBA Guide, section 6.3.3.1, also supports this approach, as it states that the business analyst should follow the change management plan and the requirements management plan to manage changes to the requirements and to communicate them to the relevant stakeholders, including the suppliers. References:
* PMBOK Guide, 6th edition, section 12.2.2.4 and 4.6
* PMI-PBA Guide, section 6.3.3.1
According to the PMBOK Guide, 6th edition, section 12.2.2.4, the project manager should use procurement documentation to define and manage the contractual relationships with the suppliers. Procurement documentation includes the contract, the statement of work, the procurement management plan, and the source selection criteria. The project manager should ensure that the project team, including the business analyst, is aware of the terms and conditions of the contract and the scope of work that the supplier is expected to deliver. Any changes or additions to the scope should be formally requested and approved through the change control process, as described in section 4.6. The PMI-PBA Guide, section 6.3.3.1, also supports this approach, as it states that the business analyst should follow the change management plan and the requirements management plan to manage changes to the requirements and to communicate them to the relevant stakeholders, including the suppliers. References:
* PMBOK Guide, 6th edition, section 12.2.2.4 and 4.6
* PMI-PBA Guide, section 6.3.3.1