<?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: Agile Design and Embedded</title>
	<atom:link href="http://www.renaissancesoftware.net/blog/archives/81/feed" rel="self" type="application/rss+xml" />
	<link>http://www.renaissancesoftware.net/blog/archives/81</link>
	<description>Blogging about Agile Development, especially embedded.  Follow me on twitter: jwgrenning</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:09:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jim Gfesser</title>
		<link>http://www.renaissancesoftware.net/blog/archives/81/comment-page-1#comment-939</link>
		<dc:creator>Jim Gfesser</dc:creator>
		<pubDate>Thu, 23 Dec 2010 20:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=81#comment-939</guid>
		<description>Hi James,

I totally agree with you on agile and embedded software development.

Long story short...
In one of my previous jobs, one of the groups I was in was extremely focused on getting all the documentation just perfect, totally the waterfall method. It would take many months just to get most of the requirements written. They had to be perfect and all-inclusive.

This seemed very unusual to me and some of the other team members. So I started wondering if this was really how software was supposed to be developed. I had heard about agile and started reading about it. I also listened to some podcasts about it. It&#039;s like a lightbulb when on inside my head - agile really seems like the better way to make quality software.

I understand that when developing safety-critical software that lives depend on, you need to be very thorough, and you need to know what you&#039;re doing, but there have to be better ways than waterfall. Agile looks like it&#039;s a good way to do that.

Being an embedded software developer myself, I&#039;m interested in seeing how agile and embedded can work together.</description>
		<content:encoded><![CDATA[<p>Hi James,</p>
<p>I totally agree with you on agile and embedded software development.</p>
<p>Long story short&#8230;<br />
In one of my previous jobs, one of the groups I was in was extremely focused on getting all the documentation just perfect, totally the waterfall method. It would take many months just to get most of the requirements written. They had to be perfect and all-inclusive.</p>
<p>This seemed very unusual to me and some of the other team members. So I started wondering if this was really how software was supposed to be developed. I had heard about agile and started reading about it. I also listened to some podcasts about it. It&#8217;s like a lightbulb when on inside my head &#8211; agile really seems like the better way to make quality software.</p>
<p>I understand that when developing safety-critical software that lives depend on, you need to be very thorough, and you need to know what you&#8217;re doing, but there have to be better ways than waterfall. Agile looks like it&#8217;s a good way to do that.</p>
<p>Being an embedded software developer myself, I&#8217;m interested in seeing how agile and embedded can work together.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

