<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Ramblings of a Microsoft.com PM : Development Methodologies</title><link>http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx</link><description>Tags: Development Methodologies</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Documentation in an agile world ... how much is enough, and how do you decide?</title><link>http://blogs.technet.com/jim_scardelis/archive/2007/02/20/documentation-in-an-agile-world-how-much-is-enough-and-how-do-you-decide.aspx</link><pubDate>Wed, 21 Feb 2007 02:15:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:655334</guid><dc:creator>Jim Scardelis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jim_scardelis/comments/655334.aspx</comments><wfw:commentRss>http://blogs.technet.com/jim_scardelis/commentrss.aspx?PostID=655334</wfw:commentRss><description>This morning, I was looking through one of the stack of trade magazines that seems to find its way to my mailbox and read a very interesting article on software documentation that I wanted to share with you. In the article, (“ Documentation Strategies...(&lt;a href="http://blogs.technet.com/jim_scardelis/archive/2007/02/20/documentation-in-an-agile-world-how-much-is-enough-and-how-do-you-decide.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=655334" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/General/default.aspx">General</category><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx">Development Methodologies</category></item><item><title>Changes... (been busy)</title><link>http://blogs.technet.com/jim_scardelis/archive/2006/05/29/430893.aspx</link><pubDate>Tue, 30 May 2006 08:34:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:430893</guid><dc:creator>Jim Scardelis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jim_scardelis/comments/430893.aspx</comments><wfw:commentRss>http://blogs.technet.com/jim_scardelis/commentrss.aspx?PostID=430893</wfw:commentRss><description>I've been kind of slow posting since a number of things have been in flux back at the office. Over the last few weeks: We had a re-org in the Microsoft.com space. Some of the chips haven't finished falling yet, I think, but essentially my team moved out...(&lt;a href="http://blogs.technet.com/jim_scardelis/archive/2006/05/29/430893.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=430893" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/General/default.aspx">General</category><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Deployment+Automation/default.aspx">Deployment Automation</category><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx">Development Methodologies</category></item><item><title>Development methodologies &amp; microsoft.com development teams</title><link>http://blogs.technet.com/jim_scardelis/archive/2006/04/14/425274.aspx</link><pubDate>Fri, 14 Apr 2006 20:40:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425274</guid><dc:creator>Jim Scardelis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jim_scardelis/comments/425274.aspx</comments><wfw:commentRss>http://blogs.technet.com/jim_scardelis/commentrss.aspx?PostID=425274</wfw:commentRss><description>There are a couple of variations on agile development methodologies in use in the groups that develop applications for Microsoft.com. Most groups utilize the old traditional Waterfall approach, which can be summarized as: Initiate the project -- Sell...(&lt;a href="http://blogs.technet.com/jim_scardelis/archive/2006/04/14/425274.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=425274" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx">Development Methodologies</category></item><item><title>MSCOM Release Checklists..</title><link>http://blogs.technet.com/jim_scardelis/archive/2006/04/04/424245.aspx</link><pubDate>Tue, 04 Apr 2006 20:27:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424245</guid><dc:creator>Jim Scardelis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jim_scardelis/comments/424245.aspx</comments><wfw:commentRss>http://blogs.technet.com/jim_scardelis/commentrss.aspx?PostID=424245</wfw:commentRss><description>The MSCOM Ops team just put a good description of Operations interacts with our software development life cycle (SDLC) process up on their blog . It's a good read. Included therein are a couple of versions of the documents that my team uses to track the...(&lt;a href="http://blogs.technet.com/jim_scardelis/archive/2006/04/04/424245.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=424245" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/General/default.aspx">General</category><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx">Development Methodologies</category></item><item><title>Agile?</title><link>http://blogs.technet.com/jim_scardelis/archive/2006/03/23/423032.aspx</link><pubDate>Fri, 24 Mar 2006 05:47:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423032</guid><dc:creator>Jim Scardelis</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/jim_scardelis/comments/423032.aspx</comments><wfw:commentRss>http://blogs.technet.com/jim_scardelis/commentrss.aspx?PostID=423032</wfw:commentRss><description>The use of Agile software development methodologies, such as MSF for Agile Development holds a lot of promise. However, 1st generation agile methodologies can be problematic when developing software for deployment in online systems, as they do not always...(&lt;a href="http://blogs.technet.com/jim_scardelis/archive/2006/03/23/423032.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=423032" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/jim_scardelis/archive/tags/Development+Methodologies/default.aspx">Development Methodologies</category></item></channel></rss>