{"id":8012096,"date":"2016-05-26T18:28:41","date_gmt":"2016-05-27T01:28:41","guid":{"rendered":"https:\/\/test-agilealliance.pantheonsite.io\/?post_type=aa_glossary&p=8012096"},"modified":"2023-03-07T17:18:52","modified_gmt":"2023-03-08T01:18:52","slug":"frequent-releases","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/frequent-releases\/","title":{"rendered":"Frequent Releases"},"content":{"rendered":"
\n
\n

An Agile team frequently releases its product into the hands of end users, listening to feedback, whether critical or appreciative.<\/p>\n

Precisely how frequent is desirable varies according to the technical and business aspects of the context, but in general one release every four to six iterations would be considered a maximum.<\/p>\n

In favorable technical contexts, such as Web development, a more frequent rhythm of release can be achieved, such as every iteration. Some teams push this practice to its limit of continuous deployment<\/a>.<\/p>\n<\/div>\n<\/div>\n

Common Pitfalls<\/h2>\n
\n
\n
    \n
  • showing the latest version of the product to a project or product manager for \u201ctesting\u201d is not sufficient; nor is turning a version over to a quality assurance team; a \u201crelease\u201d in this sense should be at the least a beta version evaluated by representative users<\/li>\n
  • in some cases (such as embedded software) it will not be possible to arrange for frequent release to \u201call\u201d users; this should not be a pretext to give up on frequent release to \u201csome\u201d users (pilot sites, volunteer beta testers, etc.)<\/li>\n<\/ul>\n<\/div>\n<\/div>\n

    Expected Benefits<\/h2>\n
    \n
    \n

    Setting up for frequent releases \u201cfrom the early stages of the project\u201d is a cornerstone of Agile\u2019s risk reduction approach:<\/p>\n

      \n
    • it mitigates the well-known planning failure mode of discovering delays very late<\/li>\n
    • it validates the product\u2019s fit to its market earlier<\/li>\n
    • it provides earlier information about the quality and stability of the product<\/li>\n
    • it allows for a quicker return on the economic investment into the product<\/li>\n<\/ul>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      An Agile team frequently releases its product into the hands of end users, listening to feedback, whether critical or appreciative.<\/p>\n","protected":false},"author":12,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[906],"tags":[],"class_list":["post-8012096","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-technology"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/8012096","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\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8012096"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/8012096\/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=8012096"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8012096"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8012096"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}