Which technique helps POs collaborate with Agile teams and stakeholders to determine the economic impact of potential work items?

The technique that helps Product Owners (POs) collaborate with Agile teams and stakeholders to determine the economic impact of potential work items is known as the cost of delay. This method quantifies the potential financial impact of delaying features or tasks, allowing POs to prioritize work based on its economic value. By understanding the cost of delay, POs can make informed decisions about which items should be addressed first, ensuring that the team focuses on delivering maximum value as quickly as possible. This approach not only improves collaboration among team members and stakeholders but also aligns the prioritization process with the organization's overall financial goals, making it a crucial strategy in Agile practices.

The other techniques, while valuable in their own right, serve different purposes. Feature prioritization is a broader category that includes various methods to rank features without specifically focusing on their economic impact. Impact mapping is used to visualize how different product features contribute to higher-level business goals, though it doesn’t directly quantify economic impacts. User story mapping helps to organize and visualize the user’s journey through a product but does not specifically address the financial implications of delaying work items. Thus, focusing on the cost of delay supports a more economically-driven decision-making process among Agile teams.