Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

2 answers

2 accepted

2 votes
Answer accepted

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.

@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.

Thanks Kyle and Brittany

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

How do I mark as accepted?

Click the checkmark by the original answer. 

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

which is better?

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,018 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you