<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://bloggingabout.net/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>Dan Bunea</title><link>http://bloggingabout.net/blogs/danbunea/default.aspx</link><description>My insight into the business of software development from an agile perspective</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>CHAPTER 4: Learning and adapting</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/04/25/chapter-4-learning-and-adapting.aspx</link><pubDate>Fri, 25 Apr 2008 08:28:15 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458468</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458468</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/04/25/chapter-4-learning-and-adapting.aspx#comments</comments><description>4. Learning and Adapting Introduction Software development is a continuous learning activity between the customer who knows the business domain and the developers who know the software. Since the software product needs to combine the two areas of knowledge...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/04/25/chapter-4-learning-and-adapting.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458468" width="1" height="1"&gt;</description></item><item><title>CHAPTER 3 (continued) : 3.4 Collaborating</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/04/17/chapter-3-continued-3-4-collaborating.aspx</link><pubDate>Thu, 17 Apr 2008 09:51:47 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458231</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458231</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/04/17/chapter-3-continued-3-4-collaborating.aspx#comments</comments><description>3.4 Collaborating Introduction One of the values of the agile manifesto states: “Customer collaboration over following a contract” being completed then in the principles by: “ Business people and developers must work together daily throughout the project...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/04/17/chapter-3-continued-3-4-collaborating.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458231" width="1" height="1"&gt;</description></item><item><title>CHAPTER 3: Communicating and Collaborating</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/04/11/chapter-3-communicating-and-collaborating.aspx</link><pubDate>Fri, 11 Apr 2008 07:06:21 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458193</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458193</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/04/11/chapter-3-communicating-and-collaborating.aspx#comments</comments><description>3.1 Introduction Communication is considered to be the main factor in a project’s success or failure. Alistair Cockburn calls software development “a game of communication and invention”, in his book “Agile Software Development”, where a big part is dedicated...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/04/11/chapter-3-communicating-and-collaborating.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458193" width="1" height="1"&gt;</description><category domain="http://bloggingabout.net/blogs/danbunea/archive/tags/agile+mini+book/default.aspx">agile mini book</category></item><item><title>CHAPTER 2: Agile methodologies</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/04/04/chapter-2-agile-methodologies.aspx</link><pubDate>Fri, 04 Apr 2008 08:25:40 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458145</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458145</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/04/04/chapter-2-agile-methodologies.aspx#comments</comments><description>2.1 Introduction What is a methodology? A methodology for software is a set of related rules, principles and practices that, once put in practice, can help deliver valuable software, to the client on time, over and over again. Your methodology is everything...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/04/04/chapter-2-agile-methodologies.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458145" width="1" height="1"&gt;</description></item><item><title>CHAPTER 1: Problems and causes with the way we develop software</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/03/28/chapter-1-problems-and-causes-with-the-way-we-develop-software.aspx</link><pubDate>Fri, 28 Mar 2008 12:37:43 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458100</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458100</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/03/28/chapter-1-problems-and-causes-with-the-way-we-develop-software.aspx#comments</comments><description>Troughout this chapter I will try to show briefly how the software industry went from one extreme to another, in the processes used to develop software. If at first chaos was the main problem, then the software industry went straight into the other extreme...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/03/28/chapter-1-problems-and-causes-with-the-way-we-develop-software.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458100" width="1" height="1"&gt;</description></item><item><title>The agile mini book - a 6 week series</title><link>http://bloggingabout.net/blogs/danbunea/archive/2008/03/21/the-agile-mini-book-a-6-week-series.aspx</link><pubDate>Fri, 21 Mar 2008 14:51:05 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:458070</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=458070</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2008/03/21/the-agile-mini-book-a-6-week-series.aspx#comments</comments><description>About 2 years, ago, I spoke with someone about writing an agile mini book. I wrote the book, but things changed, and it wasn&amp;#39;t published. Now I decided, to publish it, chapter by chapter, week by week so for the next 6 weeks this is what can be expected...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2008/03/21/the-agile-mini-book-a-6-week-series.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=458070" width="1" height="1"&gt;</description></item><item><title>Lucene indexes as agile databases</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/10/21/lucene-indexes-as-agile-databases.aspx</link><pubDate>Sun, 21 Oct 2007 20:06:43 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:405001</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=405001</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/10/21/lucene-indexes-as-agile-databases.aspx#comments</comments><description>Download Source code Introduction In product development, as opposed to bespoke project development where each client gets its own software, you deliver the same software to each client. This has some advantages: single development stream, with multiple...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/10/21/lucene-indexes-as-agile-databases.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=405001" width="1" height="1"&gt;</description><category domain="http://bloggingabout.net/blogs/danbunea/archive/tags/lucene+agile+database/default.aspx">lucene agile database</category></item><item><title>Testing drag'n'drop with WatiN</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/03/28/testing-drag-n-drop-with-watin.aspx</link><pubDate>Wed, 28 Mar 2007 11:35:27 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221138</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221138</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/03/28/testing-drag-n-drop-with-watin.aspx#comments</comments><description>Many of the recent Web 2.0 applications require drag and drop functionality. Sometimes it is useful, sometimes it is just marketing, but if you have to do it and at the same time you want to write all your code test first (TDD), a new problem arises:...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/03/28/testing-drag-n-drop-with-watin.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221138" width="1" height="1"&gt;</description></item><item><title>Test First Web Applications: TDDing a Castle MonoRail application with C# and Selenium</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/02/23/test-first-web-applications-tdding-a-castle-monorail-application-with-c-and-selenium.aspx</link><pubDate>Fri, 23 Feb 2007 08:36:42 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221139</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221139</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/02/23/test-first-web-applications-tdding-a-castle-monorail-application-with-c-and-selenium.aspx#comments</comments><description>Published on InfoQ.com Download Source code Introduction TDD samples are mostly based on very simple unit tests. But how could we do something like building a web application test first. What we need to do Let&amp;#39;s say that we need to write test first...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/02/23/test-first-web-applications-tdding-a-castle-monorail-application-with-c-and-selenium.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221139" width="1" height="1"&gt;</description><category domain="http://bloggingabout.net/blogs/danbunea/archive/tags/TDD+test+first+Castle+MonoRail+ActiveRecord/default.aspx">TDD test first Castle MonoRail ActiveRecord</category></item><item><title>Model View Presenter - is testing the presenter enough?</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/01/24/model-view-presenter-is-testing-the-presenter-enough.aspx</link><pubDate>Wed, 24 Jan 2007 15:13:52 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221140</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221140</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/01/24/model-view-presenter-is-testing-the-presenter-enough.aspx#comments</comments><description>Source code: Download Lately, I have noticed that the Humble Dialog Box or Model View Presenter are gaining more and more acceptance among software developers, especially in agile communities, because of its benefits regarding the very good separation...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/01/24/model-view-presenter-is-testing-the-presenter-enough.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221140" width="1" height="1"&gt;</description></item><item><title>Ajax Scaffolding with Castle MonoRail and C#</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/01/23/ajax-scaffolding-with-castle-monorail-and-c.aspx</link><pubDate>Tue, 23 Jan 2007 14:21:36 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221141</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221141</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/01/23/ajax-scaffolding-with-castle-monorail-and-c.aspx#comments</comments><description>Download Sources, and view demos Goal Let&amp;#39;s say we need to write an application very fast, that can do the basic CRUD operations for a Product. Ruby on rails ( www.rubyonrails.org ) came up with the excellent idea of scaffolding, and the idea was...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/01/23/ajax-scaffolding-with-castle-monorail-and-c.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221141" width="1" height="1"&gt;</description><category domain="http://bloggingabout.net/blogs/danbunea/archive/tags/castle+ajax+prototype+scaffolding+generator/default.aspx">castle ajax prototype scaffolding generator</category></item><item><title>Ajax Scaffolding generator with Monorail: a VS.NET 2005 addin</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/01/18/ajax-scaffolding-generator-with-monorail-a-vs-net-2005-addin.aspx</link><pubDate>Thu, 18 Jan 2007 14:24:02 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221142</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221142</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/01/18/ajax-scaffolding-generator-with-monorail-a-vs-net-2005-addin.aspx#comments</comments><description>Download the VS 2005 addin In my previous article, I explained how by modifying Marc Andre Cournoyer&amp;#39;s generator, we made it generate Ajax based, scaffolding code for Castle MonoRail. In the meantime, my colleague Gabi Munteanu, managed to put together...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/01/18/ajax-scaffolding-generator-with-monorail-a-vs-net-2005-addin.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221142" width="1" height="1"&gt;</description><category domain="http://bloggingabout.net/blogs/danbunea/archive/tags/castle+ajax+prototype+scaffolding+generator/default.aspx">castle ajax prototype scaffolding generator</category></item><item><title>To obtain good code, writing tests and code is faster then code alone</title><link>http://bloggingabout.net/blogs/danbunea/archive/2007/01/12/to-obtain-good-code-writing-tests-and-code-is-faster-then-code-alone.aspx</link><pubDate>Fri, 12 Jan 2007 05:38:33 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221143</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221143</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2007/01/12/to-obtain-good-code-writing-tests-and-code-is-faster-then-code-alone.aspx#comments</comments><description>A few weeks ago on the TestDrivenDevelopment mailing list, Ron Jeffies, one of the XP gurus stated that &amp;quot;in order to obtain good code, writing tests and code is faster then just code&amp;quot;. To find out if this is true or not let&amp;#39;s make a small...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2007/01/12/to-obtain-good-code-writing-tests-and-code-is-faster-then-code-alone.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221143" width="1" height="1"&gt;</description></item><item><title>Agile adaptive planning and fast delivery sample</title><link>http://bloggingabout.net/blogs/danbunea/archive/2006/11/27/agile-adaptive-planning-and-fast-delivery-sample.aspx</link><pubDate>Mon, 27 Nov 2006 18:34:07 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221144</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221144</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2006/11/27/agile-adaptive-planning-and-fast-delivery-sample.aspx#comments</comments><description>After seeing that there are very many people that find it hard to see how agile handles adaptive planning, letting the customer not know from the beginning what he wants, I wanted to develop a mini sample to show these concepts in practice. A small agile...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2006/11/27/agile-adaptive-planning-and-fast-delivery-sample.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221144" width="1" height="1"&gt;</description></item><item><title>How TDD improves development speed and is very cost effective</title><link>http://bloggingabout.net/blogs/danbunea/archive/2006/11/26/how-tdd-improves-development-speed-and-is-very-cost-effective.aspx</link><pubDate>Sun, 26 Nov 2006 02:31:25 GMT</pubDate><guid isPermaLink="false">813b6dfd-644e-4573-a816-eebab56ba0d0:221145</guid><dc:creator>Becoming Agile</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://bloggingabout.net/blogs/danbunea/rsscomments.aspx?PostID=221145</wfw:commentRss><comments>http://bloggingabout.net/blogs/danbunea/archive/2006/11/26/how-tdd-improves-development-speed-and-is-very-cost-effective.aspx#comments</comments><description>When it comes to automated tests the first impression everyone (including myself) thinks that that would certainly increase the amount of time a certain feature is developed in. However as I started to practice TDD, Test First Programming, increasing...(&lt;a href="http://bloggingabout.net/blogs/danbunea/archive/2006/11/26/how-tdd-improves-development-speed-and-is-very-cost-effective.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://bloggingabout.net/aggbug.aspx?PostID=221145" width="1" height="1"&gt;</description></item></channel></rss>