Velocity is a measure of the amount of work a team can complete in a given iteration. It is calculated by dividing the total number of story points completed by the team by the duration of the iteration. Velocity can vary from iteration to iteration due to various factors such as team size, complexity of work, technical issues, etc. Therefore, it is not advisable to use a single iteration's velocity as a baseline for future planning. Instead, the project manager should ask the product owner to look at a minimum of four to eight iterations and use the average or median velocity as a more reliable indicator of the team's performance. This way, the product owner can replan the velocity for the next iteration based on the team's current performance and adjust the scope and schedule accordingly. This is consistent with the agile principle of responding to change over following a plan and the PMI-PBA practice of planning and monitoring the business analysis approach. References:
* PMBOK Guide, 6th edition, page 18, section 1.2.3.2
* Agile Practice Guide, page 36, section 3.3.2
* PMI-PBA Exam Content Outline, page 9, task 1.1
* PMI-PBA Certification Exam Prep Guide, page 63, section 3.2.1