The team aims for a work pace that they would be able to sustain indefinitely.<\/p>\n
This entails a firm refusal of what is often considered a \u201cnecessary evil\u201d in the software industry \u2013 long work hours, overtime, or even working nights or weekends. As such this \u201cpractice\u201d is really more of a contract negotiated between the team and their management.<\/p>\n
The term \u201csustainable pace\u201d, more general, was proposed by Kent Beck himself in replacement of the original \u201c40-hour week\u201d denomination for this Extreme Programming<\/a> practice.<\/p>\n The Agile mindset views recourse to overtime, other than on an exceptional basis, as detrimental to productivity rather than enhancing it. Overtime tends to mask schedule, management, or quality deficiencies; the Agile approach favors exposing these deficiencies as early as possible and remedying their underlying causes, rather than merely treating the symptoms.<\/p>\n There is a consensus that research in manufacturing industries generally shows<\/a> that overtime has a detrimental impact on productivity.<\/p>\n Some caveats apply when transposing this to software development; one review<\/a> considers the research in this area inconclusive; even defining the term \u201cproductivity\u201d is problematic<\/a> in the context of knowledge work; few studies appear to have been conducted that apply specifically to overtime among knowledge workers.<\/p>\n Several<\/a> articles<\/a> and industry presentations<\/a> have made a strong case against overtime in the software development context, and provide further references to published academic research.<\/p>\n","protected":false},"excerpt":{"rendered":" The team aims for a work pace that they would be able to sustain indefinitely.<\/p>\n","protected":false},"author":8027401,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[890],"tags":[859],"class_list":["post-5003331","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-people","tag-xp"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003331","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=5003331"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003331\/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=5003331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Expected Benefits<\/h2>\n
Academic Publications<\/h2>\n