According to the Professional in Business Analysis (PMI-PBA)® Guide, an impediment is anything that prevents the team from delivering value or achieving its goals. An impediment can be internal or external, technical or non-technical, and can affect the quality, scope, schedule, cost, or risk of the project. In this scenario, the product owner has presented the backlog to the team, and the team has raised concerns over implementing some of the features due to various impediments. The project manager should suggest that the product owner ensure that the impediments are captured and prioritized based on the highest valued features. This would help the product owner to address the most critical impediments first, and to align the backlog with the project objectives and stakeholder expectations. This would also help the team to focus on delivering the most valuable features, and to overcome the impediments with the support of the product owner and the project manager. Estimating the financial impact of the impediments and requesting additional funding, beginning to remove the impediments starting with the easiest ones first, or capturing the impediments and informing management that their assistance is needed are actions that should be taken after the impediments are captured and prioritized, not before. These actions do not address the root cause of the situation, which is the misalignment between the backlog and the team’s capabilities. References: (Professional in Business Analysis Reference Materials source and documents)

Professional in Business Analysis (PMI-PBA)® Guide, Chapter 6, Section 6.3.1.2

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 9, Section 9.2.2.2

The Standard for Project Management – Seventh Edition, Chapter 3, Section 3.2.2.2