<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/350959.aspx</link><description /><dc:language>zh-CN</dc:language><lastUpdateTime>Fri, 06 Jun 2008 22:17:19 GMT</lastUpdateTime><ttl>60</ttl><item><dc:creator>elevenXL</dc:creator><title>应对敏捷项目中的干扰</title><link>http://blog.csdn.net/elevenXL/archive/2008/06/06/2518321.aspx</link><pubDate>Fri, 06 Jun 2008 22:17:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/06/06/2518321.aspx</guid><wfw:comment>comments/2518321.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/06/06/2518321.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2518321.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2518321</trackback:ping><description>干扰，正如它名字所显示的，是影响敏捷项目团队速度、减缓其前进的刹车闸。有些干扰是必需的，其他则不是。关键在于：要识别出影响工作进程的干扰，并尽量减少它对项目的负面影响...&lt;img src ="aggbug/2518321.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>什么是Scrum?</title><link>http://blog.csdn.net/elevenXL/archive/2008/05/25/2480674.aspx</link><pubDate>Sun, 25 May 2008 22:17:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/05/25/2480674.aspx</guid><wfw:comment>comments/2480674.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/05/25/2480674.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2480674.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2480674</trackback:ping><description>Scrum (英式橄榄球争球队), 软件开发模型是敏捷开发的一种，在最近的一两年内逐渐流行起来...&lt;img src ="aggbug/2480674.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/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/2320820.aspx</link><pubDate>Thu, 24 Apr 2008 07:48:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320820.aspx</guid><wfw:comment>comments/2320820.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/24/2320820.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2320820.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2320820</trackback:ping><description>在项目中，应用敏捷方法最重要的一部分就是管理团队所用的过程，但并不仅仅是过程，还包括其它方面：比如团队的开发、文化变迁的管理、相应的技术及管理工具，以及那些与项目有直接或者间接关系的敏捷建导师的合作...&lt;img src ="aggbug/2320820.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/12/2285446.aspx</link><pubDate>Sat, 12 Apr 2008 12:55:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/12/2285446.aspx</guid><wfw:comment>comments/2285446.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/12/2285446.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2285446.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2285446</trackback:ping><description>重构更多的是基于激情，把代码做为艺术品来雕琢。但是不少软件公司工作环境可以很快摧残这种热情...&lt;img src ="aggbug/2285446.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>ThoughtWorks专访：一个没有经理室的公司（图）</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/06/2254774.aspx</link><pubDate>Sun, 06 Apr 2008 15:31:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/06/2254774.aspx</guid><wfw:comment>comments/2254774.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/06/2254774.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2254774.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2254774</trackback:ping><description>我个人也非常喜欢这样的氛围，希望以后自己的工作地方也是如此，呵呵...&lt;img src ="aggbug/2254774.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>把握现在，掌控未来：2008 Java开发展望</title><link>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252526.aspx</link><pubDate>Sat, 05 Apr 2008 00:18:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252526.aspx</guid><wfw:comment>comments/2252526.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/04/05/2252526.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2252526.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2252526</trackback:ping><description>2007 充满了激荡人心的事件，动态语言的不断升温，JVM在开源社区不断发展以及Java社区的重要贡献者，Google的崛起等。问题是，这些预示了来年什么呢？安德鲁•格勒弗（Andrew Glover）准备了一些答案给那些打破砂锅问到底的Java开发者――现在，什么在2008接踵而至...&lt;img src ="aggbug/2252526.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/02/2140023.aspx</link><pubDate>Sun, 02 Mar 2008 21:35:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140023.aspx</guid><wfw:comment>comments/2140023.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/03/02/2140023.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2140023.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2140023</trackback:ping><description>随着敏捷开发过程流行，敏捷测试方法也开始受到更多的关注...&lt;img src ="aggbug/2140023.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/26/2123695.aspx</link><pubDate>Tue, 26 Feb 2008 22:15:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/02/26/2123695.aspx</guid><wfw:comment>comments/2123695.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/02/26/2123695.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2123695.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2123695</trackback:ping><description>第4章 测试

            烈火验真金，逆境磨意志。
                        ——卢修斯.塞尼加（公元前4－公元65）
...&lt;img src ="aggbug/2123695.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>如何用CRC模型来确定需求</title><link>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088247.aspx</link><pubDate>Mon, 11 Feb 2008 16:25:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088247.aspx</guid><wfw:comment>comments/2088247.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088247.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2088247.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2088247</trackback:ping><description>CRC(Class-Responsibility-Collaborator)卡建模是一种简单且有效的面向对象的分析技术。在一个OO(面向对象)开发项目中，包括用户、系统分析员和开发者在建模和设计过程中经常应用CRC卡建模，使整个开发团队普遍的理解形成一致...&lt;img src ="aggbug/2088247.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>elevenXL</dc:creator><title>CRC 卡的典型应用</title><link>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088055.aspx</link><pubDate>Mon, 11 Feb 2008 10:44:00 GMT</pubDate><guid>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088055.aspx</guid><wfw:comment>comments/2088055.aspx</wfw:comment><comments>http://blog.csdn.net/elevenXL/archive/2008/02/11/2088055.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>comments/commentRss/2088055.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=2088055</trackback:ping><description>一句话,CRC 是用来帮忙理清设计的思路,它不是 UML 图,也不是精确的类结构图。只要我们在处理这些卡
的时候不断的讨论,我们设计的思路将会变成非常清楚...&lt;img src ="aggbug/2088055.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>