robably the most important responsibility of the product owner is to manage the product backlog, which is the evolving (usually growing) list of requirements for the project. New requirements can be proposed by customers and stakeholders at any point during the project. This is one of the characteristics of agile projects that make them different from traditional projects that can have strict change management processes.

However, agile project teams don't accept all new requirements proposed by customers. The product owner must prioritize these new inputs vs. the requirements that are already in the product backlog. Some new inputs may be good additions to the project that make the overall result better. Some new inputs won't rise to that standard and may not be included in the project at all.

What experience do you have with telling customers "no?" Do you have any best practices for dealing with this situation?