what is the point/value of adding comments to the user story.

[Sudha Avasarala]

The product owner quested, what is the values of adding comments to user story when all the team is sitting together and we constantly interact with each other. Who are we adding comments for and what values does it add  instead its wasting developers time.

If its technical work to what extent can we add comments?

[Kyle Moseley · Accepted solution]

Comments are good for those in the future who have to go back to the issue for information. Or anyone who wasn't in on the developers' conversation. It's like documentation in that regard.

[Brittany Wispell]

@Sudha Avasarala 

It's best to do the "documentation" during the sprint. Sometimes if the team waits till the end things can be easily over looked. This will cause gaps in your documentation. Also, your dev team will be focused on doing the next sprint rather than taking the time to do proper documentation at the end of the existing sprint. Leaving a quick comment is going to be the most time effective and help keep from gaps in documentation.

[Sudha Avasarala]

Thanks Kyle and Brittany

[Kyle Moseley]

You're welcome. If you found this helpful please mark the answer as Accepted.

[Sudha Avasarala]

How do I mark as accepted?

[Kyle Moseley]

Click the checkmark by the original answer. 

[Sudha Avasarala · Accepted solution]

Can they produce one document at the end of the sprint instead of adding comments everyday during the sprint?

which is better?

[Pratik Chhichhia]

I have seen scrum teams implementing this with a slight change of what you are saying here.
Having an implementation summary (document or in form of comments depends or sometimes both) dev team adds to each user story which comes at a very early stage of the sprint and not at the end of the sprint. 
The reason may be to get the implementation/approach verified by peers/architects to get their feedback during implementation itself.

Thanks! 

Pratik