<?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: From Software Development to Problem Solving	</title>
	<atom:link href="https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/</link>
	<description></description>
	<lastBuildDate>Tue, 28 Apr 2015 14:01:27 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: scrumxp		</title>
		<link>https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/#comment-26781</link>

		<dc:creator><![CDATA[scrumxp]]></dc:creator>
		<pubDate>Thu, 05 Mar 2015 06:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2399#comment-26781</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/#comment-26780&quot;&gt;David Halonen&lt;/a&gt;.

The say &quot;garbage in = garbage out&quot; is always true in software development. Using a framework like Scrum, the Product Owner should be the source of good requirements. Agile does not solve the case when you build the &quot;wrong&quot; software, it should just make it easier to spot that you go in the wrong direction with its shorter delivery and feedback cycles.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/#comment-26780">David Halonen</a>.</p>
<p>The say &#8220;garbage in = garbage out&#8221; is always true in software development. Using a framework like Scrum, the Product Owner should be the source of good requirements. Agile does not solve the case when you build the &#8220;wrong&#8221; software, it should just make it easier to spot that you go in the wrong direction with its shorter delivery and feedback cycles.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David Halonen		</title>
		<link>https://www.scrumexpert.com/knowledge/from-software-development-to-problem-solving/#comment-26780</link>

		<dc:creator><![CDATA[David Halonen]]></dc:creator>
		<pubDate>Thu, 05 Mar 2015 02:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2399#comment-26780</guid>

					<description><![CDATA[lots to consider here. For example, agile seems to fail badly at analyst &#038; design. Who needs to think? Why?]]></description>
			<content:encoded><![CDATA[<p>lots to consider here. For example, agile seems to fail badly at analyst &amp; design. Who needs to think? Why?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
