I'm going to use JIRA/Greenhopper OnDemand on my Scrum agile project for story management and scheduling into sprints. What's the best place to put acceptance criteria? Should they just go in with the Description body, or should I create a new field?
We use an extra field "Acceptance criteria" because the description field is for understanding the user story.
The criteria geht the prefix (-) for not fullfilled and (/) for fullfilled. So we can visually check the progress of a story very easily.
When there are sub tasks, the sub tasks get the acceptance criteria and the user stories acceptance criteria are a brief summary of the total acceptance criteria divided in scections per sub task. When a sub task itself is an acceptance criterion this works well, too.
This way has stood the test of time in the last years.
We have done two things. The DONE criteria is actually mapped to a set of fields in Jira so that developers need not go anywhere else to get reminded about the stuff they need to finish for any Story. Also an additional transistion is added to 'Under Progress' state, which opens up a customized screen for the DONE criteria stuff. This transistion does not change the status, it goes back to 'Under Development' itself. So once all the DONE criteria is met, it is ready for a closure. Also this makes the status transparent to people.
Additionally a more descriptive explaination of each criteria is put down in Confluence and under each of the custom field created in Jira, the description has a link to this page in Confluence for each field.
This is the best option I have come across. You can either use the plugin or set it up yourself. Check the below page and it goes in depth about how to do this effectively.
Uggghh! Yet another paid add-on??!! As a 10-year user of TFS it's obvious Acceptance Criteria is a critical concept. TFS has it as a separate tab for each user story, so its clearly delineated from the Description. Everybody goes to a single place to document, review and update Acceptance Criteria. Having them buried in Jira as comments within everything else is a recipe for disaster (and missed requirements).
As a suggestion to this question, acceptence criterias should not be that difficult to use. Normally as Scrum Master , my expectation in story detail page is -
1- Explanation of the story.
2- A list where i can add acceptence criterias by just clicking a plus icon.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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!
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