How to mention field position in agile ?

Remember that in Scrum, you don't *need* to write user stories at all. The Scrum Guide doesn't mention them.

Every Sprint must result in a potentially usable increment of value being delivered. That's where the agility is, not in writing stories. A useful increment might encompass one of the features you mention, or a combination of them, or a sub-flow of one which the Product Owner thinks is valuable.

So how should I mention my requirement which I have given in first post ?..

> So how should I mention my requirement which I have given in first post ?..

From your reading of the Scrum Guide, do you think it might be a good idea to simply mention it in Product Backlog refinement, giving whatever information you have, and then allow the rest of the Scrum Team to provide their input?

Remember that refining Product Backlog items is a collaborative act, and an ongoing one, between the Product Owner who wants the value, and the Development Team who would deliver it. That's the most important thing.

So you mean Graphical user interfaces such as buttons should be mentioned in product backlog and nowhere else?

Okay...so after going through few online websites I got that you simply mention the requirements for buttons in prototype or wireframes. No need to mention in any document.

Also, in agile, wireframes or prototype is designed using pencil and paper instead of some tool because agile focuses on collaborative interaction so you expect inputs from client as well as your team. Hence , no time to use software.

Please correct me If I am wrong.

The approach you have just described is certainly a more agile one than trying to write user stories by yourself.

Thanks for your guidance.