Is "what browser do we have to support" in SCRUM an impediment or a user story? The PO defined a user story, roughly saying: "As an employee want to use functionality X in our web interface". The functionality is well defined and for internal use in a large company, but during planning the dev-team asks: what is our minimum browser, because this influences estimations. Neither the dev-team nor the PO know what the pre-installed browser in the target company is and declare that an impediment. Is it now the SM's task to figure this out by contacting the target company the feature is built for, because for the PO this is "a technical detail I don't care about", or is it the SM's task to let the PO know that his user story is not precise enough and ask the PO to contact the target company?

This a requirement, and therefore the Product Owner shall figure it out by contacting the target company. While waiting for the answer, the team **can** start thinking about a solution which is kind of browser independent, or can get some data about the most popular browser in the domain and start working on it. These last two ideas are not approved by the Scrum framework, because according to it, the team shouldn't do anything which hasn't been approved by the Product Owner or the customer, in order to avoid waste creation.