<?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 for Edge of Chaos | Agile Development Blog</title>
	<atom:link href="http://www.targetprocess.comcomments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.targetprocess.com/blog</link>
	<description>Scrum, Lean, Kanban, Extreme Programming, Complex Adaptive Systems</description>
	<pubDate>Wed, 10 Mar 2010 05:57:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on (fr)Agile Teams: Handle with Care by Randy Tangco</title>
		<link>http://www.targetprocess.com/blog/2010/03/fragile-teams-handle-with-care.html/comment-page-1#comment-1151</link>
		<dc:creator>Randy Tangco</dc:creator>
		<pubDate>Fri, 05 Mar 2010 15:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=898#comment-1151</guid>
		<description>What are some techniques or methods you can use to vaccinate the team from outside opinions?</description>
		<content:encoded><![CDATA[<p>What are some techniques or methods you can use to vaccinate the team from outside opinions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on (fr)Agile Teams: Handle with Care by Randy Tangco</title>
		<link>http://www.targetprocess.com/blog/2010/03/fragile-teams-handle-with-care.html/comment-page-1#comment-1150</link>
		<dc:creator>Randy Tangco</dc:creator>
		<pubDate>Fri, 05 Mar 2010 15:56:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=898#comment-1150</guid>
		<description>What are some suggestions to vaccinating the team from outside opinions?</description>
		<content:encoded><![CDATA[<p>What are some suggestions to vaccinating the team from outside opinions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Alex Radzie</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1149</link>
		<dc:creator>Alex Radzie</dc:creator>
		<pubDate>Wed, 03 Mar 2010 18:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1149</guid>
		<description>"What should be done to make developers really care?"&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;I think I know a better solution. Forget about developers, instead you should teach your UX people how to code. Just imagine, possibilities are endless. Not only can they create great user interfaces, they will also write user stories as they know problem domain so well, so no need for product owner. Now you can get rid of programmers too, who seem to be the weakest link. Usability experts themselves will be able to implement requirements. What a dream team of competent and creative people.&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Jokes aside, I&#39;ve reread your post with comments again. Your message sounds like developers can&#39;t bring business value to user stories only because they don&#39;t like working on user interface. And because of that they should be told what to do exactly.</description>
		<content:encoded><![CDATA[<p>&#8220;What should be done to make developers really care?&#8221;</p>
<p>I think I know a better solution. Forget about developers, instead you should teach your UX people how to code. Just imagine, possibilities are endless. Not only can they create great user interfaces, they will also write user stories as they know problem domain so well, so no need for product owner. Now you can get rid of programmers too, who seem to be the weakest link. Usability experts themselves will be able to implement requirements. What a dream team of competent and creative people.</p>
<p>Jokes aside, I&#39;ve reread your post with comments again. Your message sounds like developers can&#39;t bring business value to user stories only because they don&#39;t like working on user interface. And because of that they should be told what to do exactly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Colin Johnson</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1148</link>
		<dc:creator>Colin Johnson</dc:creator>
		<pubDate>Wed, 03 Mar 2010 03:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1148</guid>
		<description>There is a good report on Agile + UX on Jakob Nielsen&#39;s site:&lt;br&gt;&lt;br&gt;&lt;a href="http://www.useit.com" rel="nofollow"&gt;http://www.useit.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;It costs $149 but it is a great read at over 75 pages and describes the problem and some solutions better than the article above.</description>
		<content:encoded><![CDATA[<p>There is a good report on Agile + UX on Jakob Nielsen&#39;s site:</p>
<p><a href="http://www.useit.com" rel="nofollow">http://www.useit.com</a></p>
<p>It costs $149 but it is a great read at over 75 pages and describes the problem and some solutions better than the article above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Relax, Agile Development IS Growing Up by Valentin Tudor</title>
		<link>http://www.targetprocess.com/blog/2010/02/relax-agile-development-is-growing-up.html/comment-page-1#comment-1147</link>
		<dc:creator>Valentin Tudor</dc:creator>
		<pubDate>Mon, 01 Mar 2010 12:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=870#comment-1147</guid>
		<description>Should be a way for building an Agile CMMI :-)&lt;br&gt;These two models are not completely exclusive. An effective CMMI approach should have embedded Agile practices.&lt;br&gt;And reverse: some CMMI concerns could be introduced in an Agile process.</description>
		<content:encoded><![CDATA[<p>Should be a way for building an Agile CMMI <img src='http://www.targetprocess.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> <br />These two models are not completely exclusive. An effective CMMI approach should have embedded Agile practices.<br />And reverse: some CMMI concerns could be introduced in an Agile process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Olga</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1146</link>
		<dc:creator>Olga</dc:creator>
		<pubDate>Mon, 01 Mar 2010 11:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1146</guid>
		<description>Alex&#39; comment on developers being passionate is about something else. Put simply, it&#39;s all about work culture, tasks and goals. Developers are not slackers (mostly), and they do their job the way they should. Passion and care is not all the time about getting job done - you can&#39;t always be passionate. It might be that job is your passion. You might have some other passion - not the job you do. But it does not matter as soon as you do your job: if you&#39;re in this team - work is work. You just need to be plain professional, if you work as a developer in some company. What I&#39;m trying to say is - developers have tasks to write code and implement functional features. They haven&#39;t been told it&#39;s their job to care about UX and produce awesome user experience. It&#39;s about making a good UX a part of their job. Perhaps they should work in immediate collaboration with UX designers. It&#39;s about changing the culture of software development - traditionally, developers do not see it as their tasks to think about designs. Changing this culture is not about "passion" and "care". It&#39;s more than that.</description>
		<content:encoded><![CDATA[<p>Alex&#39; comment on developers being passionate is about something else. Put simply, it&#39;s all about work culture, tasks and goals. Developers are not slackers (mostly), and they do their job the way they should. Passion and care is not all the time about getting job done - you can&#39;t always be passionate. It might be that job is your passion. You might have some other passion - not the job you do. But it does not matter as soon as you do your job: if you&#39;re in this team - work is work. You just need to be plain professional, if you work as a developer in some company. What I&#39;m trying to say is - developers have tasks to write code and implement functional features. They haven&#39;t been told it&#39;s their job to care about UX and produce awesome user experience. It&#39;s about making a good UX a part of their job. Perhaps they should work in immediate collaboration with UX designers. It&#39;s about changing the culture of software development - traditionally, developers do not see it as their tasks to think about designs. Changing this culture is not about &#8220;passion&#8221; and &#8220;care&#8221;. It&#39;s more than that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Michael Dubakov</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1145</link>
		<dc:creator>Michael Dubakov</dc:creator>
		<pubDate>Mon, 01 Mar 2010 09:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1145</guid>
		<description>Yeah, I think you nailed the problem. &lt;br&gt;Now we should find a good solution. What should be done to make developers really care?</description>
		<content:encoded><![CDATA[<p>Yeah, I think you nailed the problem. <br />Now we should find a good solution. What should be done to make developers really care?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Alex Radzie</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1144</link>
		<dc:creator>Alex Radzie</dc:creator>
		<pubDate>Mon, 01 Mar 2010 09:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1144</guid>
		<description>"Most developers can’t create usable design."&lt;br&gt;&lt;br&gt;May be it&#39;s because your developers don&#39;t care about the product they are working on? What would happen if they were passionate about it?&lt;br&gt;&lt;br&gt;Here&#39;s the counter example from &lt;a href="http://thegeektalk.com/interviews/scott-chacon:" rel="nofollow"&gt;http://thegeektalk.com/interviews/scott-chacon:&lt;/a&gt;&lt;br&gt;&lt;br&gt;"At GitHub we don’t have a project tracker or todo list – we just all work on whatever is most interesting to us.  No standup meetings, burndown charts or points to assign. No chickens or pigs.  It’s sort of the open source software style of business – everyone itches thier own scratch.  Inexplicably, it works really well and keeps everyone engaged, new features appearing quickly and bugs fixed rather fast. No managers, directors, PMs or departments – and it’s the most agile, focused and efficient team I’ve ever worked with.  Maybe we should write a book about it."</description>
		<content:encoded><![CDATA[<p>&#8220;Most developers can’t create usable design.&#8221;</p>
<p>May be it&#39;s because your developers don&#39;t care about the product they are working on? What would happen if they were passionate about it?</p>
<p>Here&#39;s the counter example from <a href="http://thegeektalk.com/interviews/scott-chacon:" rel="nofollow"></a><a href="http://thegeektalk.com/interviews/scott-chacon" rel="nofollow">http://thegeektalk.com/interviews/scott-chacon</a>:</p>
<p>&#8220;At GitHub we don’t have a project tracker or todo list – we just all work on whatever is most interesting to us.  No standup meetings, burndown charts or points to assign. No chickens or pigs.  It’s sort of the open source software style of business – everyone itches thier own scratch.  Inexplicably, it works really well and keeps everyone engaged, new features appearing quickly and bugs fixed rather fast. No managers, directors, PMs or departments – and it’s the most agile, focused and efficient team I’ve ever worked with.  Maybe we should write a book about it.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Michael Dubakov</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1143</link>
		<dc:creator>Michael Dubakov</dc:creator>
		<pubDate>Mon, 01 Mar 2010 07:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1143</guid>
		<description>Did you read the comments thread? I am not saying that all developers can&#39;t design and care about UX much, I am saying that most of them do not care.</description>
		<content:encoded><![CDATA[<p>Did you read the comments thread? I am not saying that all developers can&#39;t design and care about UX much, I am saying that most of them do not care.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile + UX by Andrew Golik</title>
		<link>http://www.targetprocess.com/blog/2010/02/agile-ux.html/comment-page-1#comment-1142</link>
		<dc:creator>Andrew Golik</dc:creator>
		<pubDate>Sun, 28 Feb 2010 12:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.targetprocess.com/blog/?p=887#comment-1142</guid>
		<description>Oh, sure. The developers are downright silly so they can&#39;t design at high level at all. Furthermore they have to pair in order to just create something. It more looks like football, everybody knows how play well but football players know it hardly. It is a pity.</description>
		<content:encoded><![CDATA[<p>Oh, sure. The developers are downright silly so they can&#39;t design at high level at all. Furthermore they have to pair in order to just create something. It more looks like football, everybody knows how play well but football players know it hardly. It is a pity.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
