Should functional requirements be written as acceptance criteria within the "issue" or user story? If not, why.

Should functional requirements be written as acceptance criteria within the "issue" or user story?  If not, why.

1 answer

Personally, yes, functional requirements should be written as acceptance criteria within the issue. Best way to get the team to ensure they are all executed is to put them in the team's workflow. The team is using JIRA to track their work so put the acceptance criteria there as well. If you document them somewhere else, it may work as well but the team will then have information scattered around and may forget about some criteria before closing the issue.

Some people document their acceptance criteria in the description field of the issue (the wiki renderer allows checkmark icons). Other use third party add-on such as Checklist (shameless plug here smile). The nice thing about these add-ons is that they nicely format the criteria and some actually allow you to prevent the team to resolve/close the issue before all the items in the list are checked.

Hope that helps

Yves

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,911 views 19 22
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you