<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.6" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for The Software Management Blog</title>
	<link>http://www.redblack3.com/blog</link>
	<description>Optimizing Software Development</description>
	<pubDate>Sat, 04 Sep 2010 21:56:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.6</generator>

	<item>
		<title>Comment on Provisioning CouchDB with EC2 - New Video from Andy Glover @ Beacon50 by J Chris A</title>
		<link>http://www.redblack3.com/blog/?p=41#comment-82985</link>
		<pubDate>Mon, 02 Nov 2009 00:01:16 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=41#comment-82985</guid>
					<description>You can get the latest 0.10 release from the couchio AMIs Jan and I prepared.

http://hosting.couch.io/ami/

aptitude should be using the new version of CouchDB soon as well.</description>
		<content:encoded><![CDATA[<p>You can get the latest 0.10 release from the couchio AMIs Jan and I prepared.</p>
<p><a href="http://hosting.couch.io/ami/" rel="nofollow">http://hosting.couch.io/ami/</a></p>
<p>aptitude should be using the new version of CouchDB soon as well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on On the Way to Agile Transparency: Climbing the Big Wall by Alex Forbes</title>
		<link>http://www.redblack3.com/blog/?p=7#comment-73578</link>
		<pubDate>Fri, 27 Mar 2009 19:57:43 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=7#comment-73578</guid>
					<description>A really good post. Would like to tweet this up and consider adding your blog to the http://blog.accurev.com blogroll.

Well said.

Alex</description>
		<content:encoded><![CDATA[<p>A really good post. Would like to tweet this up and consider adding your blog to the <a href="http://blog.accurev.com" rel="nofollow">http://blog.accurev.com</a> blogroll.</p>
<p>Well said.</p>
<p>Alex
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Distributed Agile Development by Mark</title>
		<link>http://www.redblack3.com/blog/?p=17#comment-73085</link>
		<pubDate>Wed, 25 Mar 2009 21:00:19 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=17#comment-73085</guid>
					<description>A great tool to use for the Mirrored Offshore team model is Accurev, as it allows you complete flexible control of the development process and to grant more and more control to the offshore team as necessary. 

See StreamBrowser, Reparenting and Offshore Development with AccuRev.

Mark</description>
		<content:encoded><![CDATA[<p>A great tool to use for the Mirrored Offshore team model is Accurev, as it allows you complete flexible control of the development process and to grant more and more control to the offshore team as necessary. </p>
<p>See StreamBrowser, Reparenting and Offshore Development with AccuRev.</p>
<p>Mark
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Agile 103: Continuous Integration and Agile Development by Sixsuffices</title>
		<link>http://www.redblack3.com/blog/?p=26#comment-69084</link>
		<pubDate>Wed, 04 Mar 2009 12:13:13 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=26#comment-69084</guid>
					<description>I started looking at Agile practices from a software client's point of view. The advantages of this way of working for the commissioners and end users are just amazing - collaboration, responding to change etc etc. 

In terms of CI, the best output for users is the reliability of the end product, the fact that you can get your hands on the working code earlier in the project and that there is no horrible surprises that need fixed right at the end.
fyi our team used a handy gadget from agilehardware.com that notified the team on the state of the build.</description>
		<content:encoded><![CDATA[<p>I started looking at Agile practices from a software client&#8217;s point of view. The advantages of this way of working for the commissioners and end users are just amazing - collaboration, responding to change etc etc. </p>
<p>In terms of CI, the best output for users is the reliability of the end product, the fact that you can get your hands on the working code earlier in the project and that there is no horrible surprises that need fixed right at the end.<br />
fyi our team used a handy gadget from agilehardware.com that notified the team on the state of the build.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on User Experience in Agile by Levent Gurses&#8217; Journal &#187; Agile 102: Continuous Integration Explained</title>
		<link>http://www.redblack3.com/blog/?p=13#comment-10091</link>
		<pubDate>Tue, 30 Oct 2007 17:39:27 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=13#comment-10091</guid>
					<description>[...] A second variation of the diagram can happen when successful completion of the functional tests triggers a second deployment to another machine. Since the CI server knows it is a good build, this time it deploys to a user acceptance machine, targeting the customer directly. The advantage of redundant deploys is that semi-independent teams such the User Experience (UE) have a machine that always runs the latest good build. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A second variation of the diagram can happen when successful completion of the functional tests triggers a second deployment to another machine. Since the CI server knows it is a good build, this time it deploys to a user acceptance machine, targeting the customer directly. The advantage of redundant deploys is that semi-independent teams such the User Experience (UE) have a machine that always runs the latest good build. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Agile 101: What is Continuous Integration? by Levent Gurses&#8217; Journal &#187; Agile 102: Continuous Integration Explained</title>
		<link>http://www.redblack3.com/blog/?p=18#comment-10090</link>
		<pubDate>Tue, 30 Oct 2007 17:38:39 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=18#comment-10090</guid>
					<description>[...] One of the points in What is Continuous Integration (CI)? was the importance of having reliable automated build scripts and executing them often. CI can be seen as a natural extension of the Automated Builds practice since in most cases it relies on the presence of a set of ABS. A well-designed CI system encapsulates other sub-practices such as Continuous Builds, Continuous Database Integration, Continuous Unit Testing, Continuous Deployment, Continuous Functional Testing, Continuous Notifications, and Continuous Reporting. All of these are designed to shorten the time between the problem discovery and the problem solution. Agile teams can rely not only on the time-saving nature of automated asynchronous builds, but also on the timely and accurate feedback as a result of this type of CI. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] One of the points in What is Continuous Integration (CI)? was the importance of having reliable automated build scripts and executing them often. CI can be seen as a natural extension of the Automated Builds practice since in most cases it relies on the presence of a set of ABS. A well-designed CI system encapsulates other sub-practices such as Continuous Builds, Continuous Database Integration, Continuous Unit Testing, Continuous Deployment, Continuous Functional Testing, Continuous Notifications, and Continuous Reporting. All of these are designed to shorten the time between the problem discovery and the problem solution. Agile teams can rely not only on the time-saving nature of automated asynchronous builds, but also on the timely and accurate feedback as a result of this type of CI. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Agile Monkeys Gone Wild by Willy-Peter Schaub : Scrum - a day at the zoo</title>
		<link>http://www.redblack3.com/blog/?p=12#comment-64</link>
		<pubDate>Wed, 28 Feb 2007 19:55:50 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=12#comment-64</guid>
					<description>[...] http://www.jacoozi.com/blog/?p=12. A colleague of mine pointed us to the article and a thread of email started growing, debating whether or not the content could be related to our implementation of the Agile Scrum methodology in some of our projects. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href="http://www.jacoozi.com/blog/?p=12." rel="nofollow">http://www.jacoozi.com/blog/?p=12.</a> A colleague of mine pointed us to the article and a thread of email started growing, debating whether or not the content could be related to our implementation of the Agile Scrum methodology in some of our projects. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on ROI of Agile Development by 126682 Blog Verification</title>
		<link>http://www.redblack3.com/blog/?p=21#comment-62</link>
		<pubDate>Wed, 28 Feb 2007 04:53:12 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=21#comment-62</guid>
					<description>&lt;strong&gt;126682 Blog Verification...&lt;/strong&gt;

126682...</description>
		<content:encoded><![CDATA[<p><strong>126682 Blog Verification&#8230;</strong></p>
<p>126682&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Continuous Refactoring and ROI by Tyner Blain</title>
		<link>http://www.redblack3.com/blog/?p=11#comment-56</link>
		<pubDate>Tue, 27 Feb 2007 08:10:33 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=11#comment-56</guid>
					<description>&lt;strong&gt;Product Life Cycle and the ROI of Agile Development...&lt;/strong&gt;

The product life cycle is a description of the presence or behavior of a product in the marketplace over time.  The framework for description is a function of the sales volume of the product versus time.  Over time, products are created and introduced,...</description>
		<content:encoded><![CDATA[<p><strong>Product Life Cycle and the ROI of Agile Development&#8230;</strong></p>
<p>The product life cycle is a description of the presence or behavior of a product in the marketplace over time.  The framework for description is a function of the sales volume of the product versus time.  Over time, products are created and introduced,&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on User Experience in Agile by Levent Gurses&#8217; Journal &#187; Agile 101: What is Continuous Integration?</title>
		<link>http://www.redblack3.com/blog/?p=13#comment-37</link>
		<pubDate>Mon, 19 Feb 2007 07:42:45 +0000</pubDate>
		<guid>http://www.redblack3.com/blog/?p=13#comment-37</guid>
					<description>[...]  Bookmark at:StumbleUpon &#124; Digg &#124; Del.icio.us &#124; Dzone &#124; Newsvine &#124; Spurl &#124; Simpy &#124; Furl &#124; Reddit &#124; Yahoo! MyWebShare and Enjoy:These icons link to social bookmarking sites where readers can share and discovernew web pages. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;]  Bookmark at:StumbleUpon | Digg | Del.icio.us | Dzone | Newsvine | Spurl | Simpy | Furl | Reddit | Yahoo! MyWebShare and Enjoy:These icons link to social bookmarking sites where readers can share and discovernew web pages. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
