<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Process on about:rileycsillag fka drewcsillag</title>
		<link>https://riley.thecsillags.com/categories/process/</link>
		<description>Recent content in Process on about:rileycsillag fka drewcsillag</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 26 Sep 2014 12:39:00 -0400</lastBuildDate>
		
			<atom:link href="https://riley.thecsillags.com/categories/process/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Doing Agile Wrong</title>
				<link>https://riley.thecsillags.com/posts/2014-09-26-doing-agile-wrong/</link>
				<pubDate>Fri, 26 Sep 2014 12:39:00 -0400</pubDate>
				<guid>https://riley.thecsillags.com/posts/2014-09-26-doing-agile-wrong/</guid>
				<description>&lt;p&gt;While I&amp;rsquo;m often at odds with software frameworks (libraries are to be&#xA;preferred over frameworks, generally), I&amp;rsquo;ve found that process&#xA;frameworks can be very good indeed, when done right.  Implementors of&#xA;agile methodologies ironically can fall into the trap of doing it&#xA;wrong.&lt;/p&gt;&#xA;&lt;!-- more --&gt;&#xA;&lt;p&gt;Why ironic?  Well let&amp;rsquo;s look at the agile manifesto from the&#xA;&lt;a href=&#34;http://www.agilemanifesto.org/&#34;&gt;agile manifesto website&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Individuals and interactions over processes and tools&lt;/li&gt;&#xA;&lt;li&gt;Working software over comprehensive documentation&lt;/li&gt;&#xA;&lt;li&gt;Customer collaboration over contract negotiation&lt;/li&gt;&#xA;&lt;li&gt;Responding to change over following a plan&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;What I&amp;rsquo;ve heard is that in many companies they prescribe: &amp;ldquo;We do agile&#xA;&lt;em&gt;this&lt;/em&gt; way&amp;rdquo;, &lt;em&gt;which breaks the first statement of agile&lt;/em&gt;.  On the&#xA;other hand, when agile is done right, if you have many teams, you&#xA;should have many variants of agile processes.  If you are going to&#xA;prescribe something, it&amp;rsquo;s best to prescribe the framework, i.e. the&#xA;manifesto, rather than it&amp;rsquo;s particular implementation.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
