<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Eleven的专栏 - </title><link>category/316881.aspx</link><description /><dc:language>zh-CN</dc:language><lastUpdateTime>Thu, 24 Apr 2008 07:50:44 GMT</lastUpdateTime><ttl>60</ttl><item><dc:creator>elevenXL</dc:creator><title>去除隔间，增进沟通</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320828.aspx</link><pubDate>Thu, 24 Apr 2008 07:51:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320828.aspx</guid><wfw:comment>comments/2320828.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320828.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2320828.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2320828</trackback:ping><description>“很明显，这些就是开发软件的人……而且他们被忽略了。”&lt;img src ="aggbug/2320828.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>将架构作为语言：一个故事</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320814.aspx</link><pubDate>Thu, 24 Apr 2008 07:45:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320814.aspx</guid><wfw:comment>comments/2320814.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320814.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2320814.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2320814</trackback:ping><description>通常，架构要么是在Word文档中描述的一些软件系统中无形的、概念性的方面，要么就完全是由技术驱动的（“我们使用了一个XML架构”）。这两种方式都很糟糕：前者很难派上用场，而后者架构上的概念被技术宣传所掩盖...&lt;img src ="aggbug/2320814.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>需求分析：将技术语言和业务语言统一</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252518.aspx</link><pubDate>Sat, 05 Apr 2008 00:09:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252518.aspx</guid><wfw:comment>comments/2252518.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252518.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2252518.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2252518</trackback:ping><description>需求分析工作离不开这样两个人群：业务人员和技术人员。而他们两者说话的语言是不一样的：一个谈业务，一个说技术。需求分析的目标就是使两者在软件项目上说一种语言，将两者“捆绑”得最贴合，项目成功的可能性就越大...&lt;img src ="aggbug/2252518.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>优秀团队是要让团队成长，而非喘息</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/02/2243139.aspx</link><pubDate>Wed, 02 Apr 2008 08:07:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/02/2243139.aspx</guid><wfw:comment>comments/2243139.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/02/2243139.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2243139.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2243139</trackback:ping><description>在AgileJournal上最近的一篇文章中，Doug Shimp和Samall Hazziez（3Back的合伙人，Preferred Professionals Business Group的高级合伙人）一道，讲述了是什么使高效的“优秀团队”茁壮成长。&lt;img src ="aggbug/2243139.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>介绍敏捷开发的七种主流武器</title><link>http://blog.csdn.net/elevenXL/archive/2008/03/31/2232331.aspx</link><pubDate>Mon, 31 Mar 2008 10:48:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/31/2232331.aspx</guid><wfw:comment>comments/2232331.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/31/2232331.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2232331.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2232331</trackback:ping><description>敏捷开发包括一系列的方法，主流的有如下七种...&lt;img src ="aggbug/2232331.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>敏捷项目管理-迭代功能卡和停车场图 </title><link>http://blog.csdn.net/elevenXL/archive/2008/03/26/2218323.aspx</link><pubDate>Wed, 26 Mar 2008 07:33:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/26/2218323.aspx</guid><wfw:comment>comments/2218323.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/26/2218323.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2218323.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2218323</trackback:ping><description>敏捷项目管理是以迭代和功能为推动力的。功能的推动性表现在它将计划和执行的主要重点从任务转变为产品功能。这是与传统项目管理以任务为推动力的重要一个区别...&lt;img src ="aggbug/2218323.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>开源软件历史十大杰出人物</title><link>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173127.aspx</link><pubDate>Wed, 12 Mar 2008 14:43:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173127.aspx</guid><wfw:comment>comments/2173127.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173127.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2173127.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2173127</trackback:ping><description>GPL 的发明人。No.6 Michael Tiemann，G++（GNU C++ 编译器）的作者，Cygnus 公司创始人，RedHat CTO。No.9 谈到 OpenSource 就不能不提到 ESR，Eric S. Raymond， 《The Art of UNIX Programming》、《大教堂与市集》的作者，老牌 Unix 黑客，黑客道行话的收集者，OSI 的创始人，OpenSource 的鼓手...&lt;img src ="aggbug/2173127.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>2008 Jolt  Award 大奖获奖名单</title><link>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173117.aspx</link><pubDate>Wed, 12 Mar 2008 14:42:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173117.aspx</guid><wfw:comment>comments/2173117.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/12/2173117.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2173117.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2173117</trackback:ping><description>震撼大奖获得者：《代码之美》...&lt;img src ="aggbug/2173117.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>一个优秀的系统分析员应该具备的三个素质  </title><link>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140211.aspx</link><pubDate>Sun, 02 Mar 2008 22:29:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140211.aspx</guid><wfw:comment>comments/2140211.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140211.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2140211.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2140211</trackback:ping><description>都在谈论中印之间的软件大战，其实没有可争论的，我们相差太远！但并不是我们的程序员技不如人，而是缺少系统分析员，特别是高素质的系统分析员...&lt;img src ="aggbug/2140211.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>软件开发人员的组织与分工</title><link>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140076.aspx</link><pubDate>Sun, 02 Mar 2008 21:42:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140076.aspx</guid><wfw:comment>comments/2140076.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140076.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2140076.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2140076</trackback:ping><description>大型软件项目需要很多人的能力合作，花费一年或数年的时间才能完成。为了提高工作效率，保证工作质量，软件开发人员的组织、分工与管理是一项十分重要和复杂的工作...&lt;img src ="aggbug/2140076.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>在开发过程中怎样利用单元和功能测试</title><link>http://blog.csdn.net/elevenXL/archive/2008/03/01/2137975.aspx</link><pubDate>Sat, 01 Mar 2008 21:44:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/01/2137975.aspx</guid><wfw:comment>comments/2137975.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/01/2137975.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2137975.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2137975</trackback:ping><description>功能测试要在有效地情况下掌握用户的需求。而传统的开发者是在使用的过程中发现需求的。通常，人们赞同使用项目工程并且花费相当的时间去重新定制它们...&lt;img src ="aggbug/2137975.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>《敏捷软件开发（原则、模式与实践）》前三章笔记</title><link>http://blog.csdn.net/elevenXL/archive/2008/02/12/2088652.aspx</link><pubDate>Tue, 12 Feb 2008 08:41:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/02/12/2088652.aspx</guid><wfw:comment>comments/2088652.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/02/12/2088652.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2088652.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2088652</trackback:ping><description> 《敏捷软件开发（原则、模式与实践）》
（美）Robert C.Martin 著
        邓辉 译
        孟岩 审
...&lt;img src ="aggbug/2088652.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>软件工程中10个最重要的理念</title><link>http://blog.csdn.net/elevenXL/archive/2008/01/28/2070346.aspx</link><pubDate>Mon, 28 Jan 2008 17:36:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/01/28/2070346.aspx</guid><wfw:comment>comments/2070346.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/01/28/2070346.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2070346.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2070346</trackback:ping><description>1.软件开发最终是由人来执行和完成而不是机器...&lt;img src ="aggbug/2070346.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>敏捷开发最佳实践:Model Storming  </title><link>http://blog.csdn.net/elevenXL/archive/2007/11/27/1904167.aspx</link><pubDate>Tue, 27 Nov 2007 14:33:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2007/11/27/1904167.aspx</guid><wfw:comment>comments/1904167.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2007/11/27/1904167.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/1904167.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=1904167</trackback:ping><description> 你可能需要为使用白板制定一种协议，特别当要擦掉一些东西的时候。你的团队文化同样对你的成功有着举足轻重的作用，团队必须可以接受其他人要求帮助，并且可以让其他人一起建模...&lt;img src ="aggbug/1904167.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>Agile 敏捷建模思想</title><link>http://blog.csdn.net/elevenXL/archive/2007/11/26/1903530.aspx</link><pubDate>Mon, 26 Nov 2007 23:22:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2007/11/26/1903530.aspx</guid><wfw:comment>comments/1903530.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2007/11/26/1903530.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/1903530.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=1903530</trackback:ping><description>AM的价值观包括了XP的四个价值观：沟通、简单、反馈、勇气，此外，还扩展了第五个价值观：谦逊...&lt;img src ="aggbug/1903530.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>