<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: using agile and scrum the correct way</title>
	<atom:link href="http://www.theofficesurvivor.com/2010/02/using-agile-and-scrum-the-correct-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theofficesurvivor.com/2010/02/using-agile-and-scrum-the-correct-way/</link>
	<description>How To Survive in Office Politics</description>
	<lastBuildDate>Thu, 26 Aug 2010 18:38:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Hackadelic</title>
		<link>http://www.theofficesurvivor.com/2010/02/using-agile-and-scrum-the-correct-way/comment-page-1/#comment-57</link>
		<dc:creator>Hackadelic</dc:creator>
		<pubDate>Sun, 14 Mar 2010 10:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.theofficesurvivor.com/?p=540#comment-57</guid>
		<description>Nice post, I&#039;ve been practicing agile methods for years, and there is much truth in what you say.

A few thoughts:

I can confirm that often &quot;agility&quot; is taken absolutely wrong in the reality of &quot;daily business&quot; - by the management.

To effectively cope with changes flying in &quot;faster than the speed of light&quot; and with the reality that they are submitted ad-hoc, w/o formal specification, is one of the goals of agility (&quot;embrace change&quot;). In fact, the most prominent agile methods like XP or Scrum involve explicit practices to prevent from the chaos that would arise if all &quot;external&quot; changes would strike in unfiltered into the development process.

Management&#039;s task is be to balance protecting development from the chaos of ever changing requirements and allowing for changes in a controlled, organized manner.

Scrum for example allows for changes only at a start of a sprint, i.e. once every month. Anything else must be &quot;queued&quot; in the product backlog. This is essential. Claiming someone is doing Scrum w/o obeying this requirement is self-deception.

In reality (at least as I often observed it), management just loves to walk into the room and drop their newest ideas onto the team, or make last minute changes themselves. I guess it&#039;s because it is much easier, and much more comfortable, to just off-load your brain onto somebody else than to organize and prioritize your thoughts first. (That&#039;s why it&#039;s so great to have an assistant.)

Be that as it may, while external circumstances provide enough opportunity for chaos entering the development, it is often the own management that multiplies the chaos (sometimes because they don&#039;t want to lose face before a customer, but often enough out of an own premature impulse).

On the other hand, while it&#039;s fun to bash about management, there is clearly a certain share of responsibility (or lack of it) on the team to consequently demand a certain level of process stability and working conditions. They treat you like slaves? Don&#039;t let them. Stand together, and say &quot;No&quot; to grievance. They threat to fire you? They can&#039;t fire you all. They threat to fire one of you to make an example? Say that all of you will go if they do. What&#039;s the worst that can happen? If things are so bad, every other day in that job is one more day as a slave... People have fought wars and died to end slavery. Switching employers should be much easier.</description>
		<content:encoded><![CDATA[<p>Nice post, I’ve been practicing agile methods for years, and there is much truth in what you say.</p>
<p>A few thoughts:</p>
<p>I can confirm that often “agility” is taken absolutely wrong in the reality of “daily business” — by the management.</p>
<p>To effectively cope with changes flying in “faster than the speed of light” and with the reality that they are submitted ad-hoc, w/o formal specification, is one of the goals of agility (“embrace change”). In fact, the most prominent agile methods like XP or Scrum involve explicit practices to prevent from the chaos that would arise if all “external” changes would strike in unfiltered into the development process.</p>
<p>Management’s task is be to balance protecting development from the chaos of ever changing requirements and allowing for changes in a controlled, organized manner.</p>
<p>Scrum for example allows for changes only at a start of a sprint, i.e. once every month. Anything else must be “queued” in the product backlog. This is essential. Claiming someone is doing Scrum w/o obeying this requirement is self-deception.</p>
<p>In reality (at least as I often observed it), management just loves to walk into the room and drop their newest ideas onto the team, or make last minute changes themselves. I guess it’s because it is much easier, and much more comfortable, to just off-load your brain onto somebody else than to organize and prioritize your thoughts first. (That’s why it’s so great to have an assistant.)</p>
<p>Be that as it may, while external circumstances provide enough opportunity for chaos entering the development, it is often the own management that multiplies the chaos (sometimes because they don’t want to lose face before a customer, but often enough out of an own premature impulse).</p>
<p>On the other hand, while it’s fun to bash about management, there is clearly a certain share of responsibility (or lack of it) on the team to consequently demand a certain level of process stability and working conditions. They treat you like slaves? Don’t let them. Stand together, and say “No” to grievance. They threat to fire you? They can’t fire you all. They threat to fire one of you to make an example? Say that all of you will go if they do. What’s the worst that can happen? If things are so bad, every other day in that job is one more day as a slave… People have fought wars and died to end slavery. Switching employers should be much easier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
