{"id":130,"date":"2007-01-16T04:24:59","date_gmt":"2007-01-16T04:24:59","guid":{"rendered":"http:\/\/quinert.com\/stblog\/?p=130"},"modified":"2007-01-16T04:24:59","modified_gmt":"2007-01-16T04:24:59","slug":"models-of-software-development","status":"publish","type":"post","link":"http:\/\/www.software-testing.com.au\/blog\/2007\/01\/16\/models-of-software-development\/","title":{"rendered":"Models of software development"},"content":{"rendered":"<p>After an email exchange with <a href=\"http:\/\/xndev.blogspot.com\/\"><b>Matt Heusser<\/b><\/a>, Matt has <a href=\"http:\/\/xndev.blogspot.com\/2007\/01\/agile-metrics-ii.html\"><b>posted my comments<\/b><\/a> on how our work tools sometimes influence our behaviour on projects.  That&#8217;s because these work tools are based on models of how someone believe software should be developed.  Perhaps more importantly, the tools that I&#8217;ve seen are usually designed to ensure that the team conforms to a process, not to ensure that the right things have been done.<\/p>\n<p>The tool that I feel most strongly influenced the agile process in a former employer, is the workflow tool.  Workflow tools are typically linear flow tools.  I believe that the use of these kinds of tools (in our case, JIRA, but you can substitute most bug tracking tools if you like,) strongly reinforced a linear model of software development.  I&#8217;m not aware of any tools that <i>don&#8217;t<\/i> model software development this way, but am quite happy to be shown to be incorrect.<\/p>\n<p>If you don&#8217;t want your team throwing their work &#8220;over the wall&#8221;, check that your tools model development the way <i>you<\/i> think it should be done.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After an email exchange with Matt Heusser, Matt has posted my comments on how our work tools sometimes influence our behaviour on projects. That&#8217;s because these work tools are based on models of how someone believe software should be developed. Perhaps more importantly, the tools that I&#8217;ve seen are usually designed to ensure that the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,16,29,32,33,42],"tags":[],"class_list":["post-130","post","type-post","status-publish","format-standard","hentry","category-agile","category-humanising-work","category-software-development","category-systems-thinking","category-teamwork","category-xp"],"_links":{"self":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/comments?post=130"}],"version-history":[{"count":0,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/posts\/130\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/categories?post=130"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.software-testing.com.au\/blog\/wp-json\/wp\/v2\/tags?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}