In Scrum, who should be detailing fine details of tasks?

[Richard Martin]

Here's the scenario. The user story is: Management would like the credit card payment options on the site disabled since the process is not currently compliant with our insurance company's requirements. This includes access to the page and all references across the site.

It has the basic elements of who is asking, what they want, and why. It even contains additional information relevant to the definition of done.

What I'm not clear on here is who's role is it to FIND the references across the site? Should the Product Owner find those spots and detail them? The Scrum Master? The developer? We have a small team with only a couple of developers and the IT Director essentially serving the role of Product Owner (that's me).

[Bill Sheboy]

Hi @Richard Martin -- Welcome to the Atlassian Community!

How your team normally refines requests may guide your answer.

For example, I have worked with product owners who were exceptional in the product space and did not know what to look for in application code.  Others have been quite knowledgeable in all areas of their supported applications, and so could survey such a need quickly via the UI/UX.  Others could search source code to find answers from another view.

For a Scrum team, they could need the answer at least during refinement, and certainly during sprint planning.  And with your small team it will help to understand the scope/scale of work before sprints start...So however you can do that, try it, evaluate the results, and experiment to improve.

Kind regards,
Bill