<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx</link><description>I got an email today pointing out an article on Dr. Dobbs that discusses the change in mindset required to be part of an agile team as well as the roles on the team. This got me thinking about the changes I've made in how I think about software in order</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds: May 24, 2006 PM edition</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#606583</link><pubDate>Thu, 25 May 2006 03:12:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:606583</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>团队中你我他的角色？</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#606850</link><pubDate>Thu, 25 May 2006 09:53:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:606850</guid><dc:creator>lilei105</dc:creator><description>刚才在MSDN Blog上看到一位仁兄Michael Puleio写的关于Agile Development的文章，颇有见地。与MS2的同学“奇文共欣赏，疑义相与析”&lt;br&gt;在MS2的项目团队里，很多时候大家也是以Agile面貌工作的。令我感触最深的两点是Share...</description></item><item><title>re: Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#606982</link><pubDate>Thu, 25 May 2006 13:39:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:606982</guid><dc:creator>v-henlee</dc:creator><description>hey, Michael, I guess you don't have any idea of Chinese, hah, feel easy, I just recommended your post to the intern students in MSR Asia</description></item><item><title>re: Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#611131</link><pubDate>Wed, 31 May 2006 00:23:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:611131</guid><dc:creator>Francis Cheung</dc:creator><description>The points you've made apply to almost every team I've worked on, Agile or not. 
&lt;br&gt;
&lt;br&gt;Agreeing to Disagree is a tough topic. Knowing when to stop convincing others that we are right and trust someone else's solution, takes a leap of faith and respect that usually takes much time to earn. Easier said than done, but necessary none-the-less.</description></item><item><title>re: Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#621556</link><pubDate>Thu, 08 Jun 2006 07:50:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:621556</guid><dc:creator>Aaron Feng</dc:creator><description>&lt;a rel="nofollow" target="_new" href="http://aaronfeng.blogspot.com/2006/06/agile-transition.html"&gt;http://aaronfeng.blogspot.com/2006/06/agile-transition.html&lt;/a&gt;</description></item><item><title>Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#622867</link><pubDate>Fri, 09 Jun 2006 00:22:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:622867</guid><dc:creator>Geek Noise</dc:creator><description /></item><item><title>Legerity</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#624041</link><pubDate>Fri, 09 Jun 2006 20:02:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:624041</guid><dc:creator>Eighty-Twenty</dc:creator><description /></item><item><title>re: Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#629710</link><pubDate>Tue, 13 Jun 2006 19:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:629710</guid><dc:creator>Jason</dc:creator><description>The agile team I'm working on has a different approach to knowledge sharing. &amp;nbsp;From one iteration to the next, if there's something you've worked on a lot in one iteration, you're banned from working on it in the next. &amp;nbsp;Obviously, you end up pairing with the person working on that piece in the following iteration, but it really fights the tendency for people to specialize.</description></item><item><title>re: Roles in an Agile Team</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#630192</link><pubDate>Wed, 14 Jun 2006 03:04:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:630192</guid><dc:creator>mpuleio</dc:creator><description>Jason, that sounds like a pretty good way to ensure that no one gets &amp;quot;siloed&amp;quot; into only working on one part of the system. &amp;nbsp;</description></item><item><title>Links</title><link>http://blogs.msdn.com/mpuleio/archive/2006/05/24/606561.aspx#7764563</link><pubDate>Mon, 18 Feb 2008 06:22:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7764563</guid><dc:creator>Marco Dorantes' WebLog</dc:creator><description>&lt;p&gt;Favorites Build Providers for Windows Forms Curso del.icio.us-adev Dr. Dobbs Web 2.0 and the Engineering&lt;/p&gt;
</description></item></channel></rss>