The correct answer is C - Training in areas of weakness.
Velocity can be improved when the team removes skill-based bottlenecks. If some members struggle due to lack of knowledge or technical gaps, their productivity-and the team ' s velocity-will be impacted.
Targeted training helps the team overcome these weaknesses and deliver more efficiently.
PMI Agile Practice Guide:
"Improving technical and team skills through training and mentoring increases team performance and agility.
Learning is a continuous improvement activity that directly impacts delivery capacity." (PMI Agile Practice Guide, Section 6.4 - Developing People and Teams) Mike Griffiths adds:
"Velocity is driven by team capabilities. When teams address their weakest areas-through training, pairing, or knowledge sharing-they improve quality and throughput." (PMI-ACP Exam Prep, Chapter 4 - Team Performance) Other options:
* A supports communication but doesn't directly impact skill-based bottlenecks.
* B helps with planning but not necessarily performance.
* D describes the work cadence, not a practice that enhances velocity.

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.
####################################

Since PO Integration (Item #3) currently lacks user stories and estimated story points, the project team needs to break it down into smaller user stories or tasks before moving forward. This will allow the team to:
Assess dependencies and integration requirements more effectively.
Prioritize and deliver in smaller, testable increments.
Improve estimation accuracy using techniques like planning poker.
Ensure alignment with agile principles of incremental and iterative delivery.

The correct answer is B - Suggest the Product Owner prioritize the work items by feature to maximize value.
In Agile, the Product Owner is responsible for backlog prioritization. When multiple stakeholders have differing priorities, it is the Product Owner's job to evaluate business value and ROI to determine which features deliver the most value and should be addressed first.
From the PMI Agile Practice Guide:
"The Product Owner works closely with stakeholders to ensure that the most valuable work is prioritized in the backlog. When multiple stakeholders have competing interests, the Product Owner helps mediate and prioritize based on value delivery." (PMI Agile Practice Guide, Section 3.4 - Value-Based Prioritization) Mike Griffiths adds:
"Agile avoids trying to define all requirements up front. Instead, the backlog is groomed regularly, and the Product Owner ensures that the team is working on the highest value features." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Value-Driven Delivery) Other options are less effective:
* A contradicts Agile principles by suggesting complete upfront requirement definition.
* C puts responsibility on the customer instead of the empowered Product Owner.
* D implies a waterfall approach by requiring clarity before starting.
##################################################

The first step for a new Scrum Master is to gain context and alignment. According to the PMI Agile Practice Guide (Section 2.3: Agile Mindset), agile leaders must understand the product vision and goals to provide proper support to the team and align delivery efforts with organizational objectives.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) emphasizes that new leaders should start by understanding stakeholder expectations, enterprise context, and business drivers before making operational decisions like backlog setup or sprint planning.
* Option B is correct: understanding the project vision provides critical context.
* Option A is premature without first understanding the broader organizational objectives.
* Option C (sprint 0) can be useful but should follow alignment on vision and context.
* Option D skips necessary discovery and planning.