{"id":5003229,"date":"2015-12-16T22:58:44","date_gmt":"2015-12-17T06:58:44","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&#038;p=5003229"},"modified":"2022-08-31T12:54:07","modified_gmt":"2022-08-31T19:54:07","slug":"version-control","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/version-control\/","title":{"rendered":"Version Control"},"content":{"rendered":"<div>\n<div>\n<p>Version control is not strictly speaking an Agile \u201cpractice\u201d insofar as it is now (fortunately) widespread in the industry as a whole.<\/p>\n<p>It must however be mentioned here for several reasons:<\/p>\n<ul>\n<li>Though they are rare, one still occasionally stumbles across teams with outdated version control tools or practices, and even teams who haven\u2019t adopted version control tools at all<\/li>\n<li>Version control is not merely \u201cgood practice\u201d but an enabler of a number of Agile practices, such as\u00a0<a href=\"https:\/\/agilealliance.org\/glossary\/continuous-integration\/\">continuous integration<\/a><\/li>\n<li>The Agile community leans toward particular types of tools and practices, namely the same as the Open Source community: systems that afford concurrent work (\u201cmerge\u201d model rather than \u201clock\u201d) and more recently favoring distributed over centralized models<\/li>\n<li>It is therefore beneficial for an Agile team to explicitly reflect on its version control policies and infrastructure, and ensure that they and its engineering practices work harmoniously together.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<div>\n<div><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Version control is not merely &#8220;good practice&#8221; but an enabler of a number of Agile practices, such as continuous integration<\/p>\n","protected":false},"author":8027401,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[906],"tags":[],"class_list":["post-5003229","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\/5003229","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\/8027401"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003229"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003229\/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=5003229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}