<?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>Agile &amp; Scrum Articles | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/category/knowledge/articles/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Oct 2026 09:53: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>Agile &amp; Scrum Articles | 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>The Agile Job Seeker</title>
		<link>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/</link>
					<comments>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 21 Sep 2026 15:14:04 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8845</guid>

					<description><![CDATA[How do you approach a job search with an Agile mind? In this article Mark Haynes discusses how to plan your quest for a new job using the Scrum framework and concepts like sprints or user stories.. Author: Mark Haynes, https://www.linkedin.com/in/donald-mark-haynes-csm-745a609/ Think small and incrementally. Keep the big picture in mind, but focus on tasks you can accomplish in a few hours a day. Concentrate on one doable task at a time. Give yourself small assignments, then work them to completion, and move on to the next. Don’t obsess over things that will take months, or anything you have already accomplished. If you need to revisit it, then do that as a separate task. The job search, skill assessment, and skill development are all interrelated. Don’t get trapped rationalizing that you need more experience before you apply. Ask: How do I get experience? This is an excellent time to conduct a skills assessment and create a career development plan. Create a list of targeted skills. Think tools, techniques, and experience. Look for opportunities to pursue them. Constantly changing goals will lead to a spiral of self-doubt and indecision as you hit roadblocks. Pick a path. If you choose multiple paths, then work on them separately. Where do you start? It doesn’t matter. What matters is that you start now. There are jobs available, even in a bad economy. When is it a good time to look for a job? Always. You need market data. It gives a perspective on what <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/the-agile-job-seeker/" title="The Agile Job Seeker">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Eleventh Commandment of Software Development</title>
		<link>https://www.scrumexpert.com/knowledge/the-eleventh-commandment-of-software-development/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 06 Aug 2026 17:52:49 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8826</guid>

					<description><![CDATA[During my software development career, I have seen a good deal of software development approaches or methodologies used in different organizations. When a new and supposedly better approach is promoted, some people tend to adopt it with an attitude that could sometimes be close to a religious zeal. Software companies have noticed this and they now employ “product evangelists”. As a consequence, new believers are often rejecting completely what has been done previously. They adopt a “us against them” attitude, especially when the new approach is still a small movement fighting against an established methodology. This has been the same for Agile, the latest approach on the block, even if the words of the Manifesto for Agile Software Development (“while there is value in the items on the right, we value the items on the left more.”) try to avoid this “forget the past” situation. Most agile coaches agree also that it is more important to make choices according to the context than to apply a prescriptive checklist, but for some people it is easier to follow blindly a model than to absorb a philosophy. You know the proverb: “Give a man a fish, and he will eat for a day. Teach him how to fish and he will eat forever”. It is however easier to learn how to work with JUnit than to create efficient unit testing cases. Pure agilists quickly fond their “enemy”: the Waterfall, a dinosaur of software process that should be lead to extinction, buried with <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/the-eleventh-commandment-of-software-development/" title="The Eleventh Commandment of Software Development">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Sacred Agile: Religious Approaches to Software Development</title>
		<link>https://www.scrumexpert.com/knowledge/sacred-agile-religious-approaches-to-software-development/</link>
					<comments>https://www.scrumexpert.com/knowledge/sacred-agile-religious-approaches-to-software-development/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 12 May 2026 16:19:04 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[change]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8737</guid>

					<description><![CDATA[You know that when you deal with this type of topic, you are writing about a touchy subject. When I write that Agile has sometimes been sacralized, my aim is not to hurt any religious or philosophical belief, but rather to see how men behave when adopting new ideas. Raised as a catholic, what will follow is mainly comparison of the respective adoption patterns of Christian and Agile, but I think that it might apply to other philosophical and technological approaches. Ultimately, my conviction is that the values you are trying to respect in your daily personal and professional life are more important than what you claim to be. And sometimes laughing a little bit at ourselves can help to put things in perspective. The year zero of the Agile movement is linked to the creation of the Agile Manifesto and its 12 principles. Like the 10 commandments, they should regulate the life of the Agilists. Like all texts, the Manifesto is subject to interpretation (exegesis) and to translation choices for non-native English persons, like me. This leads naturally to many different “flavors” of Agile based somewhat on differences as theoretical as theological quarrels. Some of the early Agile approaches, like the oriental Christian churches of the beginning of the Christian era, are now mostly forgotten. I doubt that there are still many practitioners of Feature Driven Development or the Crystal methodology. Agilists, initially considered by traditional project management followers as “cowboys” or “anarchists”, quickly also devised a name for <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/sacred-agile-religious-approaches-to-software-development/" title="Sacred Agile: Religious Approaches to Software Development">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/sacred-agile-religious-approaches-to-software-development/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>How Software Testing Supports Better Performance</title>
		<link>https://www.scrumexpert.com/knowledge/how-software-testing-supports-better-performance/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 29 Apr 2026 20:37:31 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8729</guid>

					<description><![CDATA[Have you ever asked yourself why some apps, websites, and software tools feel smooth, fast, and easy to use from the first click? The answer often comes back to software testing. It plays a quiet but very useful role in making software work in a clean, stable, and comfortable way. When testing is done with care, the final product feels more polished, more responsive, and more ready for daily use. That is why software testing is closely linked with better performance for Scrum teams. How Testing Builds A Strong Base For Performance Good performance starts with a strong base. Software testing helps create that base by checking each part in a careful and practical way. When teams test features step by step, they get a clear idea of how the software is performing in normal use. This makes the whole system more balanced and more dependable. Performance is not only about speed. It is also about smooth flow, stable response, and easy movement from one screen to another. Testing helps support all of this. It gives developers useful feedback so they can shape the software in a better way before it reaches users. Testing Helps Software Run Smoothly When software is tested early and regularly, it becomes easier to keep everything running in a clean manner. Each function gets reviewed properly, and this supports better response time. A button click, a page open, a search result, or a payment step can all feel more natural when testing has been done <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/how-software-testing-supports-better-performance/" title="How Software Testing Supports Better Performance">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>How Software Quality Assurance Supports Long-Term Product Success</title>
		<link>https://www.scrumexpert.com/knowledge/how-software-quality-assurance-supports-long-term-product-success/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 28 Apr 2026 21:53:17 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8727</guid>

					<description><![CDATA[Have you ever used an app or website and felt happy because everything worked in a smooth and simple way? That good feeling does not happen by chance. Behind that easy experience, there is usually a strong quality process. Software quality assurance helps products stay useful, stable, and trusted for a long time. It supports Scrum teams in building software that people enjoy using again and again. When a product works well from the start and keeps improving over time, users feel comfortable with it. They trust it more. They return to it more often. This is one of the main reasons quality assurance matters for long-term product success. It is not only about checking errors. It is also about helping Agile teams build a product that stays strong as user needs grow. Quality assurance supports a product at every stage. It helps teams review features, check user flows, test performance, and confirm that updates fit the original purpose of the product. With this kind of steady support, software can stay clear, useful, and dependable for years. Why Quality Assurance Matters For Long-Term Success A successful product is not only one that launches well. A successful product is one that keeps serving people in a useful way over time. Quality assurance helps make that possible by giving structure to the full development process. When teams test early and review often, they understand the product better. They can see how each feature connects with the full user experience. This makes future <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/how-software-quality-assurance-supports-long-term-product-success/" title="How Software Quality Assurance Supports Long-Term Product Success">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>How Continuous Validation in Scrum Improves Content Readiness for AI Search</title>
		<link>https://www.scrumexpert.com/knowledge/how-continuous-validation-in-scrum-improves-content-readiness-for-ai-search/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 09 Apr 2026 15:37:28 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8719</guid>

					<description><![CDATA[The era of traditional search is rapidly fading into the past, giving way to smart algorithms and generative responses. Simply filling a website with keywords to rank high is no longer enough. Modern systems analyze the depth, veracity, and structure of content with the meticulousness of an experienced QA engineer. The team of experts at Netpeak is confident that agile methodologies are what enable the creation of such high-quality content. An agile approach transforms chaotic text writing into a streamlined production cycle with measurable results. Scrum as the Foundation of Data Quality Implementing Scrum methodology into the content creation process is a game-changer for the entire marketing team. Instead of endlessly preparing one massive piece of content, the team works in short, clear, and effective sprints. This allows for constant testing of hypotheses and checking data readiness at each intermediate stage. AI search requires impeccable logic, the absence of factual errors, and the avoidance of so-called &#8220;hallucinations&#8221; in texts. Short content development cycles enable editors and optimizers to quickly adjust the data structure. To achieve the ideal result, the team completes the following list of tasks within each work sprint: Fact-checking. Checking technical page markup. Analyzing readability for algorithms. Testing query responses. Validating the structure of all headings. Assessing the relevance of link mass. Verifying the uniqueness of each paragraph. Continuous validation within each sprint ensures that every piece of information passes a rigorous filter. Testers and editors now work together to identify weaknesses even before publication. This rhythm minimizes <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/how-continuous-validation-in-scrum-improves-content-readiness-for-ai-search/" title="How Continuous Validation in Scrum Improves Content Readiness for AI Search">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Scrum Values and Principles: Why They Matter for Team Success</title>
		<link>https://www.scrumexpert.com/knowledge/scrum-values-and-principles-why-they-matter-for-team-success/</link>
					<comments>https://www.scrumexpert.com/knowledge/scrum-values-and-principles-why-they-matter-for-team-success/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 15:07:41 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8711</guid>

					<description><![CDATA[Many teams adopt Scrum after hearing its benefits. They organize sprints, standups, boards, and wait for improvements. It happens occasionally. Often, something is off. Though meetings occur, little changes. Despite the process, the team isn&#8217;t working better. The answer is usually that the structure is there, but the values are not. This essay discusses those principles, why they matter more than the procedure, and how to embed them in your team. The Five Scrum Values Explained Simply Scrum relies on dedication, attention, openness, respect, and boldness. These words are uninspiring for a wall poster. They define Scrum team members&#8217; daily behavior. Committed people work hard and keep their promises. You don&#8217;t have to work overtime or agree to everything. It involves being honest about your skills and using them. Focus means giving your full attention to current work. Scrum teams sprint for a purpose. Focus on a few things well rather than trying to do everything. Openness is sharing facts, issues, and criticism. Hidden problems cannot be tackled by a team. Openness enables early problem detection. Respect means trusting teammates&#8217; abilities and efforts. It affects how people communicate, criticize, and resolve disagreements. Courage may be most intriguing. It requires the bravery to express an uncomfortable opinion, raise a problem, disagree with a decision, or admit faults. Without bravery, the other four virtues are hard to follow. A simple illustration of how these values work together: imagine a developer who notices a problem mid-sprint but stays quiet because they are afraid <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/scrum-values-and-principles-why-they-matter-for-team-success/" title="Scrum Values and Principles: Why They Matter for Team Success">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/scrum-values-and-principles-why-they-matter-for-team-success/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>The Cone of Uncertainty in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/the-cone-of-uncertainty/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 30 Mar 2026 12:00:53 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[product backlog]]></category>
		<category><![CDATA[requirements]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=815</guid>

					<description><![CDATA[Uncertainty in the Product Backlog is a big risk for the schedule of a Scrum project. How clever your estimations might be, Agile has to consider them using the notion of &#8220;cone of uncertainty&#8221;. The problem when trying to plan in Scrum is that the full scope of the release in Agile software development can be quite hard to estimate. This is due to the fact that the requirements are intentionally not well-know early on in the process. Confounding this problem is that frequently the release date is a hard deadline. This means that an Agile team must perform an unknown amount of work in a fixed amount of time. The &#8220;Cone of Uncertainty&#8221; describes the reduction of the uncertainty about scope after each Scrum sprint. It is only at the end of an Agile project that you eliminate the uncertainty and know the exact amount of scope is known. In anticipation of scope problems in project management, the software development schedule should be aligned to address the highest priority feature sets and features in early iterations. You defer lower priority feature sets and features to later iterations. To reduce the Cone of Uncertainty and the risks around missing a release deadline further, the requirements lead (product owner) and the Scrum team should actively defer low priority features from all feature sets to later sprints. These are the key considerations and decision points for reducing the Cone of Uncertainty in Agile: Primary goal: reduce dangerous uncertainty (feasibility, integrations, regulatory risk) <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/the-cone-of-uncertainty/" title="The Cone of Uncertainty in Scrum">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>How Software Testers Help with Requirements in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/being-a-software-tester-in-scrum/</link>
					<comments>https://www.scrumexpert.com/knowledge/being-a-software-tester-in-scrum/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 10 Mar 2026 12:00:01 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[requirements]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1634</guid>

					<description><![CDATA[As many testers have, I struggled in my first year on a Scrum team. How do I write tests without a spec? How do I know when I am done with software testing when there is no test plan? This article shows the important contributions that software testers on Agile teams can make in the requirements gathering activities of feature and user stories creation. Author: Dave McNulla, https://dmcnulla.wordpress.com/ Agile is not a process. It&#8217;s a set of values that are intended to help people develop software more quickly with better quality. If we value people and how we work together over tools and processes, we can figure out a way to get the job done better. If we value working software over great documentation, then we have a better chance at delivering working software. If we work with the customer instead of creating a rigid contract, then the software will be more like what the customer can use. If we value making the right changes over following a plan, then we have a better chance of getting past what the plan failed to account. There are also 12 key principles to support these values. Even with those values, and with the somewhat specific principles, they leave the door wide open to how a team does agile. Scrum is a way to develop software that uses the agile values and principles with some guidelines to help. The saying &#8220;it is hard by the yard but a cinch by the inch&#8221; &#8211; <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/being-a-software-tester-in-scrum/" title="How Software Testers Help with Requirements in Scrum">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/being-a-software-tester-in-scrum/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
	</channel>
</rss>
