<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">
<channel rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell">

    <title>TalkBMC - Agile Engineering</title>
  <link>http://talk.bmc.com</link>
  <description></description>
  <image rdf:resource="logo.jpg"/>
  <sy:updatePeriod>daily</sy:updatePeriod>
  <sy:updateFrequency>1</sy:updateFrequency>
  <sy:updateBase>2007-09-24T12:55:00Z</sy:updateBase>
  <items>
    <rdf:Seq>
        
          
              <rdf:li resource="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/Demos"/>
          
          
              <rdf:li resource="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/release-planning"/>
          
          
              <rdf:li resource="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/staying-releasable"/>
          
          
              <rdf:li resource="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/importance-of-prioritization"/>
          
          
              <rdf:li resource="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/agile-changed-my-life-twice"/>
          
        
   </rdf:Seq>
  </items>
</channel>


<item rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/Demos">
<title>Demos</title>
<link>http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/Demos</link>
<description>Demos are a cornerstone of &lt;a href="http://www.bmc.com/BMC/Common/CDA/hou_Page_Generic_NoNav/0,3623,10158798_39462
618,00.html"&gt;Agile development&lt;/a&gt;.  You do work for a couple of weeks.  Then you show off what you've done.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>wbodwell</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-11-07T16:53+00:00</dc:date>
</item>


<item rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/release-planning">
<title>Release Planning</title>
<link>http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/release-planning</link>
<description>&lt;a href="http://www.bmc.com/products/attachments/Ideal_Security_Patch_Process_White_Paper.pdf"&gt;Release Planning&lt;/a&gt; looks on the surface to be waterfall-like.  But if you look a little closer, it is really quite different.  It can make a huge difference in bringing the team together (particularly for large organizations involving multiple Agile teams).</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>wbodwell</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-11-06T13:43+00:00</dc:date>
</item>


<item rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/staying-releasable">
<title>Staying Releasable</title>
<link>http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/staying-releasable</link>
<description>Staying releasable is a key focus for &lt;a href="http://www.bmc.com/BMC/Common/CDA/hou_Page_Generic_NoNav/0,3623,10158798_39462
618,00.html"&gt;Agile development&lt;/a&gt;.  You attack the work incrementally (typically in two week iterations).  You learn from that work and you make adjustments with what you attack in the following iteration.  By approaching things incrementally and staying releasable, your dates become much more predictable.  You also introduce the opportunity to cut intermediate drops for customers or internal users to get more feedback.  But what does it mean to stay releasable?  And how do you achieve it?</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>wbodwell</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-30T18:44+00:00</dc:date>
</item>


<item rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/importance-of-prioritization">
<title>The Importance of Prioritization</title>
<link>http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/importance-of-prioritization</link>
<description>Agile development has many aspects, but the two I focus the most on are prioritization and releasability.  In many ways, they're the hardest to get right.  But, the better you get at these, the more you'll get out of Agile.  In this blog entry, I'll focus on prioritization.  I'll save releasability for next time.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>wbodwell</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-23T09:48+00:00</dc:date>
</item>


<item rdf:about="http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/agile-changed-my-life-twice">
<title>Agile Changed My Life (Twice)</title>
<link>http://talk.bmc.com/blogs/blog-bodwell/walter-bodwell/agile-changed-my-life-twice</link>
<description>How Agile development methodologies changed my life at Evity and BMC Software.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>ymangum</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-09-27T10:31+00:00</dc:date>
</item>


</rdf:RDF>



