<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>continuous delivery | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/continuous-delivery/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Oct 2026 09:49:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>continuous delivery | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>When Software Delivery Outruns the Pipeline: Rethinking CI/CD Throughput</title>
		<link>https://www.scrumexpert.com/knowledge/when-software-delivery-outruns-the-pipeline-rethinking-ci-cd-throughput/</link>
					<comments>https://www.scrumexpert.com/knowledge/when-software-delivery-outruns-the-pipeline-rethinking-ci-cd-throughput/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 19 Oct 2026 09:49:55 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<category><![CDATA[devops]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8879</guid>

					<description><![CDATA[With AI code generation, software developers create code faster than before. But how can the QA engineers and the CI/CD system absorb this increased workload? In this article, Sergei Cherednichenko suggests some approaches on how to deal with this situation. Author: Sergei Cherednichenko, https://linkedin.com/in/sergei-cherednichenko/ Software delivery teams produce changes faster than many continuous integration and continuous delivery (CI/CD) systems can comfortably absorb. The pressure appears in familiar places: pull-request queues grow, reviews become less thorough, flaky tests interrupt builds, merge conflicts remain unresolved, and resource-intensive validation slows the path to production. Across CircleCI projects, average throughput grew 59% year over year. For the median team, feature-branch throughput increased 15% while main-branch throughput declined 7%. Main-branch success rates fell to 70.8%, the lowest in over five years and well below CircleCI’s recommended 90% benchmark (Figure 1). DORA’s 2024 research found a similar pattern: increased artificial intelligence (AI) adoption was associated with an estimated 1.5% decrease in delivery throughput and a 7.2% reduction in delivery stability. AI-assisted development amplifies the problem by increasing the volume of code entering the system, but the larger issue is throughput: the delivery pipeline needs to control flow as carefully as it processes individual changes. (click on figure to enlarge) Figure 1. The delivery gap: year-over-year change in CI throughput by branch type. (Source: CircleCI, The 2026 State of Software Delivery.) Image courtesy of Sergei Cherednichenko. Distributed and data-streaming systems offer a useful model. When producers send work faster than consumers can process it, the system applies <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/when-software-delivery-outruns-the-pipeline-rethinking-ci-cd-throughput/" title="When Software Delivery Outruns the Pipeline: Rethinking CI/CD Throughput">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/when-software-delivery-outruns-the-pipeline-rethinking-ci-cd-throughput/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Book Review: Continuous Integration: Improving Software Quality and Reducing Risk</title>
		<link>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/</link>
					<comments>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 16:19:54 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8293</guid>

					<description><![CDATA[As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code. &#8220;Book Review: Continuous Integration: Improving Software Quality and Reducing Risk&#8221; is a book written by Paul Duvall, with Steve Matyas and Andrew Glover to help you improve the way you build and deliver software. After a initial presentation of the continuous integration (CI) concepts and objectives, the content of the book goes far beyond the simple “continuous build” aspect to cover all disciplines concerned by CI: risk management, configuration management, database evolution, software testing, inspections, deployment. It is clear that CI is just not installing a suite of tools, but is mainly changing software development practices and process. Each chapter is well-structured with practical examples related to real life situations. The book reach also nicely the objective of maintaining a balance between a somewhat tools- and language-neutral position, but still giving enough practical advice so that you could quickly adapt the advice to your own software development environment. Final appendixes give valuable information on CI resources and evaluating available CI tools. Reference: Continuous Integration: Improving Software Quality and Reducing Risk; Paul M. Duvall, Steve Matyas, Andrew Glover; Addison-Wesley Professional]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Leveraging Lifecycle Events Instead of Building Delivery Pipelines</title>
		<link>https://www.scrumexpert.com/videos/leveraging-lifecycle-events-instead-of-building-delivery-pipelines/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 02 Sep 2024 14:58:13 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8026</guid>

					<description><![CDATA[The world is moving to event-driven architecture. That is also true for the apps we are building, but also the platforms like k8s. They are heavily event-driven when it comes to reacting to new deployment/config or changes in workloads. Yet we still use classical automation with pre-defined workflows. GitOps is the way to go for cloud-native deployments. Its nature is to continuously reconcile the deployment state as specified in the desired state. With this, DevOps engineers have to add artificial event syncs to their pipelines to keep them operational. The Keptn Lifecycle Controllers main goal is to build a native and deployment-tool agnostic experience for delivering cloud-native applications by standardizing task executions and providing application health checks. This talk should give you an idea of how “pipeline-less” and cloud-native application delivery can be achieved and how the Keptn Lifecycle Controller helps you on this journey. Video producer: https://devopspro.lt/]]></description>
		
		
		
			</item>
		<item>
		<title>Continuous Delivery Optimized</title>
		<link>https://www.scrumexpert.com/videos/continuous-delivery-optimized/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 18 Apr 2023 14:36:24 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7464</guid>

					<description><![CDATA[This workshop explores the growing pains in Continuous Delivery and describe some strategies to cope with them. How do we address these growing pains? What are the next steps, beyond the CD beginner’s basic automation? How do we optimize our pipelines to meet our needs as these needs grow? The deployment pipeline is a central idea in Continuous Delivery. It represents the channel through which ideas inside your business flow to the outside world so that they can be delivered to your users in the form of working software. First steps in creating a working deployment pipeline are very rewarding. They help to improve the quality of the software that you create and usually lead to happier users. As teams mature in their adoption of Continuous Delivery though, the pipeline often begins to slow. We have more tests, we are testing more complex things, our software becomes more complex and more difficult to deploy. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Continuous Delivery and the Theory of Constraints</title>
		<link>https://www.scrumexpert.com/videos/continuous-delivery-and-the-theory-of-constraints/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 18 Oct 2021 09:27:40 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6798</guid>

					<description><![CDATA[How should you actually implement Continuous Delivery in Scrum projects? This video explains how easy it is for a Continuous Delivery implementation to be unsuccessful, how the Theory Of Constraints works, how to apply the Five Focussing Steps to Continuous Delivery, and how to home in on the constrained activities that are your keys to success. It includes tales of glorious failures and ignominious successes when adopting Continuous Delivery. Adopting Continuous Delivery takes time. You have a long list of technology and organizational changes to consider. You have to work within the unique circumstances of your organization. You are constantly surrounded by strange problems, half-baked theories, off the shelf solutions that just don’t work, and people telling you they’ve worked here for 23 years and Amazon is nothing to worry about. How do you identify and remove the major impediments in your build, testing, and operational activities? How do you avoid spending weeks, months, or years on far-reaching changes that ultimately have no impact on your time to market? The Theory of Constraints is a management paradigm that describes how to improve throughput in a homogeneous workflow. It can be applied to Continuous Delivery in order to locate, prioritize, and reduce constrained activities until a flow of release candidates to production is achieved. Video producer: https://www.agileonthebeach.co.uk/]]></description>
		
		
		
			</item>
	</channel>
</rss>
