The correct answer is D - Use the team ' s historical velocity to calculate a range of features that can be delivered. Agile emphasizes forecasting over commitment, and this is achieved through empirical data such as velocity. Providing a range based on historical velocity allows for realistic planning while acknowledging uncertainty.
From the PMI Agile Practice Guide:
"Agile forecasting is based on empirical data. Teams use their past velocity to forecast how much work they can complete in a given time frame. This forecast is typically expressed as a range to account for variability." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning and Forecasting) Mike Griffiths supports this:
"Rather than commit to fixed scope, agile teams use historical velocity and prioritized backlogs to forecast delivery. Forecasts are probabilistic, not promises." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Estimation and Forecasting) Incorrect options:
* A violates agile's core value of responding to change over following a fixed plan.
* B delays valuable forecasting data.
* C implies commitment rather than forecast.
####################################

The correct answer is C - The Product Owner, since their vision is the basis for the acceptance criteria.
The Product Owner is responsible for defining the product backlog items, including their acceptance criteria.
They represent the customer and stakeholders, and ensure that the backlog items deliver business value.
During backlog refinement, the PO provides clarity to the team when questions arise.
From the PMI Agile Practice Guide:
"The product owner defines and prioritizes the product backlog and is responsible for ensuring user stories and acceptance criteria are clear and understood by the team." (PMI Agile Practice Guide, Section 5.2 - Backlog Refinement) Mike Griffiths states:
"The product owner is the central point for decisions related to backlog items. Their role is to ensure that requirements and acceptance criteria reflect the desired outcome and stakeholder expectations." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Value-Driven Delivery) Other options are incorrect:
* A (Sponsor) is too high-level and not involved in story-level discussions.
* B (Scrum Master) facilitates the process, not the requirements.
* D (Developer) implements the story but does not define acceptance.

The correct answer is A - Hold a meeting with the team and the Product Owner to develop the team charter, working agreement, guiding principles, and product vision. This collaborative approach fosters shared understanding, ownership, and alignment early in the project.
From the PMI Agile Practice Guide:
"The team chartering process includes developing working agreements, clarifying the product vision, defining team norms, and establishing the team ' s mission. Early alignment builds trust and commitment." (PMI Agile Practice Guide, Section 4.3 - Team Charter and Working Agreements) Mike Griffiths elaborates:
"A strong start includes co-creating team values, the product vision, and working agreements. Doing this together builds a strong foundation for delivery." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 2 - Agile Principles and Chapter 4 - Team Formation) Incorrect options:
* B separates the Product Owner from the team early on.
* C reverses the roles-vision should be owned by the Product Owner.
* D is helpful, but not a prerequisite for team alignment and success.

The correct answer is B - It prevents a wasteful buildup of requirements inventory that may never be processed. Rolling wave planning is a core agile planning practice where detailed planning is deferred until closer to execution. It aligns with lean principles by avoiding over-specification and prioritizing only near- term, high-value work.
From the PMI Agile Practice Guide:
"Rolling wave planning minimizes wasted effort by only detailing work that is near execution. Planning further ahead can result in rework or unused artifacts if requirements change or become irrelevant." (PMI Agile Practice Guide, Section 5.3 - Adaptive Planning and Rolling Wave Planning) Mike Griffiths writes:
"Agile avoids big upfront planning. Rolling wave planning reduces waste, improves responsiveness, and focuses on delivering the highest-value features first while leaving less valuable work unplanned until necessary." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Incorrect options:
* A is misleading; agile allows varying levels of detail, not fixed.
* C is a traditional (waterfall) planning mindset.
* D suggests fixed scope per release, which contradicts agility.
####################################

The correct answer is A - Conduct regular one-on-one meetings to review development features and trace them back to the product roadmap. Close collaboration between the agile leader (e.g., Scrum Master or Project Lead) and the Product Owner ensures alignment between the product strategy and development execution.
From the PMI Agile Practice Guide:
"Frequent and open collaboration between the Product Owner and agile project leader helps maintain alignment between delivery and business objectives. These discussions link work to roadmap-level planning." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths states:
"Agile leadership includes partnering with the Product Owner to ensure that work being done contributes to overall product goals. Roadmap alignment is critical." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Stakeholder Engagement) Incorrect options:
* B is more appropriate for the Product Owner, not the project leader.
* C implies waterfall-style communication.
* D oversteps the Product Owner's authority in setting feature priorities.