<?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>Part 3: Lessons I learned as a Project Manager Converting to Agile</title><link>http://blogs.technet.com/b/port25/archive/2010/01/20/part-3-lessons-i-learned-as-a-project-manager-converting-to-agile.aspx</link><description>by saraford on January 20, 2010 01:29pm 
 
 In my previous post , I discussed how "not designing the full 100 percent is a true blessing in disguise" that enables Course Correction in an Agile team. In this post, you'll learn how the CodePlex team puts</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>