<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Continuous Delivery</title>
	<atom:link href="http://continuousdelivery.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://continuousdelivery.com</link>
	<description>Jez Humble&#039;s work blog</description>
	<lastBuildDate>Mon, 09 Jan 2012 16:13:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Continuous Delivery: The Value Proposition by St Francis de Assisi the patron saint of Software Craftsmanship &#124; experience craftsmanship</title>
		<link>http://continuousdelivery.com/2010/10/continuous-delivery-the-value-proposition/comment-page-1/#comment-2047</link>
		<dc:creator>St Francis de Assisi the patron saint of Software Craftsmanship &#124; experience craftsmanship</dc:creator>
		<pubDate>Mon, 09 Jan 2012 16:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=239#comment-2047</guid>
		<description>[...] We bow to the philosophy of keeping our software simple (the code and the experience) and doing the minimum amount of work required to put the software in the hands of our users so we can inspect-and-adapt, or in the words of The Lean Startup the Build-Measure-Learn feedback loop (if you are thinking in this direction then I also encourage you to immerse yourself in continuous delivery). [...]</description>
		<content:encoded><![CDATA[<p>[...] We bow to the philosophy of keeping our software simple (the code and the experience) and doing the minimum amount of work required to put the software in the hands of our users so we can inspect-and-adapt, or in the words of The Lean Startup the Build-Measure-Learn feedback loop (if you are thinking in this direction then I also encourage you to immerse yourself in continuous delivery). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On DVCS, continuous integration, and feature branches by On DVCS, continuous integration, and feature branches</title>
		<link>http://continuousdelivery.com/2011/07/on-dvcs-continuous-integration-and-feature-branches/comment-page-1/#comment-2012</link>
		<dc:creator>On DVCS, continuous integration, and feature branches</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:51:20 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=401#comment-2012</guid>
		<description>[...] Dit artikel is afkomstig van een externe website. Bron: http://continuousdelivery.com/2011/07/on-dvcs-continuous-integration-and-feature-branches/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit artikel is afkomstig van een externe website. Bron: <a href="http://continuousdelivery.com/2011/07/on-dvcs-continuous-integration-and-feature-branches/" rel="nofollow">http://continuousdelivery.com/2011/07/on-dvcs-continuous-integration-and-feature-branches/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams by Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams</title>
		<link>http://continuousdelivery.com/2011/12/organize-software-delivery-around-outcomes-not-roles/comment-page-1/#comment-2011</link>
		<dc:creator>Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=485#comment-2011</guid>
		<description>[...] Dit artikel is afkomstig van een externe website. Bron: http://continuousdelivery.com/2011/12/organize-software-delivery-around-outcomes-not-roles/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit artikel is afkomstig van een externe website. Bron: <a href="http://continuousdelivery.com/2011/12/organize-software-delivery-around-outcomes-not-roles/" rel="nofollow">http://continuousdelivery.com/2011/12/organize-software-delivery-around-outcomes-not-roles/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Continuous Delivery is set text for Agile Engineering Practices course at Oxford University by Continuous Delivery is set text for Agile Engineering Practices course at Oxford University</title>
		<link>http://continuousdelivery.com/2011/07/continuous-delivery-is-set-text-for-agile-engineering-practices-course-at-oxford-university/comment-page-1/#comment-2010</link>
		<dc:creator>Continuous Delivery is set text for Agile Engineering Practices course at Oxford University</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=381#comment-2010</guid>
		<description>[...] Dit artikel is afkomstig van een externe website. Bron: http://continuousdelivery.com/2011/07/continuous-delivery-is-set-text-for-agile-engineering-practice... [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit artikel is afkomstig van een externe website. Bron: <a href="http://continuousdelivery.com/2011/07/continuous-delivery-is-set-text-for-agile-engineering-practice.." rel="nofollow">http://continuousdelivery.com/2011/07/continuous-delivery-is-set-text-for-agile-engineering-practice..</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Make Large Scale Changes Incrementally with Branch By Abstraction by Make Large Scale Changes Incrementally with Branch By Abstraction</title>
		<link>http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstraction/comment-page-1/#comment-2009</link>
		<dc:creator>Make Large Scale Changes Incrementally with Branch By Abstraction</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=323#comment-2009</guid>
		<description>[...] Dit artikel is afkomstig van een externe website. Bron: http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstract... [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit artikel is afkomstig van een externe website. Bron: <a href="http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstract.." rel="nofollow">http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstract..</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Strategic vs Utility Services by Strategic vs Utility Services</title>
		<link>http://continuousdelivery.com/2011/01/strategic-vs-utility-services/comment-page-1/#comment-2008</link>
		<dc:creator>Strategic vs Utility Services</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=274#comment-2008</guid>
		<description>[...] Dit artikel is afkomstig van een externe website. Bron: http://continuousdelivery.com/2011/01/strategic-vs-utility-services/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Dit artikel is afkomstig van een externe website. Bron: <a href="http://continuousdelivery.com/2011/01/strategic-vs-utility-services/" rel="nofollow">http://continuousdelivery.com/2011/01/strategic-vs-utility-services/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Strategic vs Utility Services by Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams</title>
		<link>http://continuousdelivery.com/2011/01/strategic-vs-utility-services/comment-page-1/#comment-2007</link>
		<dc:creator>Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=274#comment-2007</guid>
		<description>[...] continuous delivery. This is true, which means that you only want to incur this extra cost for the part of your service portfolio that is strategic. The additional cost in this case is paid back many times by the benefit of getting to market [...]</description>
		<content:encoded><![CDATA[<p>[...] continuous delivery. This is true, which means that you only want to incur this extra cost for the part of your service portfolio that is strategic. The additional cost in this case is paid back many times by the benefit of getting to market [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Make Large Scale Changes Incrementally with Branch By Abstraction by On DVCS, continuous integration, and feature branches</title>
		<link>http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstraction/comment-page-1/#comment-2006</link>
		<dc:creator>On DVCS, continuous integration, and feature branches</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=323#comment-2006</guid>
		<description>[...] branch-by-abstraction to make complex or larger scale changes to to your application incrementally while keeping the [...]</description>
		<content:encoded><![CDATA[<p>[...] branch-by-abstraction to make complex or larger scale changes to to your application incrementally while keeping the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Continuous Delivery vs Continuous Deployment by Strategic vs Utility Services</title>
		<link>http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/comment-page-1/#comment-2005</link>
		<dc:creator>Strategic vs Utility Services</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=138#comment-2005</guid>
		<description>[...] very expensive to rev hardware. These arguments are the reason why I am very careful to distinguish continuous delivery from continuous deployment. Continuous delivery is about keeping your systems production-ready throughout development, so that [...]</description>
		<content:encoded><![CDATA[<p>[...] very expensive to rev hardware. These arguments are the reason why I am very careful to distinguish continuous delivery from continuous deployment. Continuous delivery is about keeping your systems production-ready throughout development, so that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Continuous Delivery vs Continuous Deployment by Continuous Delivery: The Value Proposition</title>
		<link>http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/comment-page-1/#comment-2004</link>
		<dc:creator>Continuous Delivery: The Value Proposition</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://continuousdelivery.com/?p=138#comment-2004</guid>
		<description>[...] boss to implement continuous delivery. One of the big technical memes of the last year has been continuous deployment &#8211; the practice of releasing every good version of your software, often multiple times a day. [...]</description>
		<content:encoded><![CDATA[<p>[...] boss to implement continuous delivery. One of the big technical memes of the last year has been continuous deployment &#8211; the practice of releasing every good version of your software, often multiple times a day. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.504 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-01-31 00:17:16 -->

