You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Has anyone in the community explored using any of the Atlassian tools to manage a repository (or something similar) of standard Acceptance Criteria elements?
I'm the Scrum Master on a team currently using Jira and Confluence and I'd like to help them develop a standard set of criteria for certain types of work that we use consistently.
For example: anything that we are building to integrate with other systems will always need to meet some basic criteria as a starting point.
Similarly, reports will usually have to meet the same criteria, so rather than reinvent the wheel, if we had a standard set that we started with (not limited to) that we could pull in, I think it would go a long way toward consistency and quality across requests, and over a short time, provide a much more thorough set.
In my world, we'd be able to cross-reference many types of work with standard or previous criteria and ensure that we aren't overlooking anything.
Maybe I'm overthinking it, but it seems like these tools could really help build a mini database or repository that could save a lot of time reinventing the wheel every iteration. Just curious if anyone else has ever approached it this way or found a way to captialie of the tools we are already using.
TIA,
Marianne Miller