{"id":5003172,"date":"2015-12-16T21:52:04","date_gmt":"2015-12-17T05:52:04","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&#038;p=5003172"},"modified":"2022-08-29T15:27:59","modified_gmt":"2022-08-29T22:27:59","slug":"definition-of-ready","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/definition-of-ready\/","title":{"rendered":"Definition of Ready"},"content":{"rendered":"<p>As in the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/definition-of-done\/\">\u201cDefinition of Done\u201d<\/a>, in the Definition of Ready, the team makes explicit and visible the criteria (generally based on the\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/invest\">INVEST<\/a>\u00a0matrix) that a user story must meet prior to being accepted into the upcoming iteration.<\/p>\n<h2>Also Known As<\/h2>\n<p>Just as completed items that fit the definition of \u201cdone\u201d are said to be \u201cDONE-done\u201d, items that fit the definition of ready are called \u201cREADY-ready\u201d.<\/p>\n<p>An etymological note for the terminally curious: this doubling of a word to call attention to something that is \u201creally\u201d ready or \u201creally\u201d done (as opposed to merely called ready or done, carelessly, without thinking twice about it) is known as \u201c<a href=\"http:\/\/en.wikipedia.org\/wiki\/Contrastive_focus_reduplication\">contrastive focus reduplication<\/a>\u201c.<\/p>\n<h2>Expected Benefits<\/h2>\n<ul>\n<li>avoids beginning work on features that do not have clearly defined completion criteria, which usually translates into costly back-and-forth discussion or rework<\/li>\n<li>provides the team with an explicit agreement allowing it to \u201cpush back\u201d on accepting ill-defined features to work on<\/li>\n<\/ul>\n<h2>Origins of Definition of Ready<\/h2>\n<p>By adding a \u201cdefinition of ready\u201d to the slightly older \u201cdefinition of done\u201d, Scrum appears to have all but reinvented previously existing concepts in process modeling, such as the ETVX framework first described in 1985, or the \u201cstandard task unit\u201d described by Jerry Weinberg.<\/p>\n<ul>\n<li>1985: the ETVX (for entry-task-validation-exit) framework described in \u201c<a href=\"http:\/\/dx.doi.org\/10.1147\/sj.242.0079\">A programming process architecture<\/a>\u201d anticipates Scrum\u2019s definitions of \u201cready\u201d and \u201cdone\u201d<\/li>\n<li>2008: while the first few\u00a0<a href=\"http:\/\/tech.groups.yahoo.com\/group\/scrumdevelopment\/message\/27437\">allusions<\/a>\u00a0to teams using a \u201cdefinition of ready\u201d date to the beginning of that year, the first\u00a0<a href=\"http:\/\/scrumftw.blogspot.com\/2008\/10\/ready-ready-definition-of-ready-for.html\">formal description<\/a>\u00a0seems to be from October, and is incorporated into \u201cofficial\u201d Scrum training material\u00a0<a href=\"http:\/\/scrum.jeffsutherland.com\/2009\/07\/ready-dynamic-model-of-scrum.html\">shortly thereafter<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Definition of Ready involves creating clear criteria that a user story must meet before being accepted into an upcoming iteration. This is typically based on the INVEST matrix.<\/p>\n","protected":false},"author":8084254,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[908],"tags":[805],"class_list":["post-5003172","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-process","tag-invest"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003172","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/8084254"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003172"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003172\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=5003172"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003172"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003172"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}