nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

unknown

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?

Accepted answers

Kyle Moseley

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.

unknown

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

which is better?

All comments

Kyle Moseley

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.

unknown

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

which is better?

Brittany Wispell

@[deleted]

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.

unknown

Thanks Kyle and Brittany

Kyle Moseley

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

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software