{"id":8017803,"date":"2015-08-07T10:57:49","date_gmt":"2015-08-07T17:57:49","guid":{"rendered":"https:\/\/test-agilealliance.pantheonsite.io\/?post_type=aa_research_paper&#038;p=8017803"},"modified":"2023-08-29T09:36:16","modified_gmt":"2023-08-29T16:36:16","slug":"explaining-agility-with-a-process-theory-of-change","status":"publish","type":"aa_research_paper","link":"https:\/\/agilealliance.org\/resources\/research-papers\/explaining-agility-with-a-process-theory-of-change\/","title":{"rendered":"Explaining Agility with a Process Theory of Change"},"content":{"rendered":"\n<p>While Agile approaches have been widely adopted, our theoretical understanding of their foundations and impacts remains limited. This is due to conflating two entirely different meanings of \u201cAgile.\u201d We therefore unpack these two meanings and present our tentative understanding as a process theory. The theory posits that agility emerges from a dialectic interplay between recognizing and responding to needs for changes. Meanwhile, rather than directly affecting success, agility moderates the negative effects of the need for change on success. Viewing agility this way helps address the research-practice gap by highlighting the need for skepticism of methods and practices, and by suggesting practically relevant research questions.<\/p>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-28f84493 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<p class=\"has-text-align-left\"><strong>Michael Wufka<\/strong><br>Department of Computing Science and Information Systems<br>Douglas College<br>New Westminster, Canada<br>wufkam@douglascollege.ca<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<p class=\"has-text-align-left\">Paul Ralph<br>Department of Computer Science<br>University of Auckland<br>Auckland, New Zealand<br>paul@paulralph.name<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>While Agile approaches have been widely adopted, our theoretical understanding of their foundations and impacts remains limited. This is due to conflating two entirely different meanings of \u201cAgile.\u201d We therefore [&hellip;]<\/p>\n","protected":false},"author":6000331,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[],"tags":[],"content_source":[186],"class_list":["post-8017803","aa_research_paper","type-aa_research_paper","status-publish","hentry","content_source-agile2015"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper\/8017803","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_research_paper"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/6000331"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8017803"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_research_paper\/8017803\/revisions"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8017803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8017803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8017803"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8017803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}