This page is intended to serve as the initial drafting place of our ACS DoR documentation. Ultimately, this documentation will be hosted directly on http://agilecoachingsoftware.com until such time as a more dynamic documentation solution is required.
Getting Started with Definition of Ready
What is a “Definition of Ready?”
A Definition of Ready (DoR) helps you determine if a ticket is actionable by your team. Generally, tickets meet the “Definition of Ready” if they meet a certain agreed-upon standard. Tickets which meet the standard are ready to be pulled in by the team. Tickets that don’t meet the standard must first be updated to satisfy that standard before they are ready to be worked.
How does a “Definition of Ready” help my team?
Tickets that meet the DoR lead to more accurate planning and faster execution. If the team begins work on a ticket which is not yet ready, waste is not far behind. By implementing a Definition of Ready, we prevent waste while providing a basis for future measurement and comparison.
How is the “Definition of Ready” calculated and implemented?
The AgileCoach DoR application implements a very simple Definition of Ready for Jira Cloud. Tickets meet the Definition of Ready provided that values are present for the following fields:
Description
Story Points
Epic Link
If each of these values are present, the ticket meets the DoR. If any value is missing, the ticket does not meet the DoR.
DoR status is computed after each update, and the DoR status of a given ticket is accessible via two pathways: the individual issue view, and the “Issues” tab.
Which issue types are considered eligible for the Definition of Ready?
At this time, three issue types are not considered eligible for Definition of Ready standards:
Epics
Bugs
Sub-task issue types
All other issue types, including custom issue types which are not sub-task types, are eligible for Definition of Ready standards.
Can “Definition of Ready” be customized?
Not at this time, but if there is user demand for customization features, we will add them to our roadmap.
Definition of Ready: Issue View
Click on an individual issue to view the Definition of Ready status within the issue’s Context Fields.
“AgileCoach: DoR” IssueGlance
Navigate to an issue. On the right-side Context Field menu, you’ll see AgileCoach: DoR. The Definition of Ready status will be displayed as a lozenge.
NOT READY - ticket does not meet the Definition of Ready.
READY - ticket meets the Definition of Ready.
N/A - ticket type is not eligible for Definition of Ready.
“Definition of Ready Fields” Panel
For a given issue, the Definition of Ready Fields panel indicates which crieria are met, and which are not met. Use this tab to figure out why your issue isn’t ready.
