I have a question regarding user stories and with agile in general. I read a few articles about user stories and there is a thing, that is not clear to me. For example in this article there is the following sentence:
User stories are a few sentences in simple language that outline the desired outcome. They don't go into detail.
However quite often a features cannot be implemented without details.
Let me give a few example.
An external service should be used in the current backend. The backend should call several endpoints of the external service.
There are important things like what endpoints should be called, what should be the content of the request, in what order endpoints should be called. So these are really technical details I admit and most probably communication/research needed to get the information regarding the external service. Who is responsible for that?
A new page added to the application. Here are also details that are important like the caption of the button, color codes, messages to the user (inforamtion,warning,error).
Who should define it, the story writer or the developer? Should this be part of the user story?
I also read a statement about user stories like,
"User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality."
I am really not against communication, but at the end of the day the outcome should be written somewhere in my opinion, because spoken communication is not permanent and the information can be lost.
So to summarize it, based on what I read, user stories are about what should be implemented and not about how. I think how is also important, because things can be done in good and bad way and the later it turns out, that something is bad, the more expensive is to correct it, but I couldn't find that how the information should be shared.