<?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 testing | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/software-testing/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>Agile testing | 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>Test Management Tools Plugins for Jira</title>
		<link>https://www.scrumexpert.com/tools/test-management-tools-plugins-for-jira/</link>
					<comments>https://www.scrumexpert.com/tools/test-management-tools-plugins-for-jira/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 07 Jul 2026 14:19:25 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Tools]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[Agile testing]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8799</guid>

					<description><![CDATA[A test management plugin for Jira will add to Jira the testing capabilities that project management tool does not provide natively. The core features of the test management Jira plugins should be to create test plans and test cases, organize them into test cycles, execute them, maintain traceability with Jira issues and provide test execution reports. Jira alone has no software testing features. It does not provide test case entity, no execution history, and no coverage reporting. The test management plugins add these features, providing a ready-to-use test management structure and reducing manual work. They help Agile teams avoid creating confusion in Jira with custom issue types or maintaining external synchronization with software tests plans and execution results. The most important features that you should look for in Jira Test Management plugins are: • Centralized test case repository: a dedicated place to create, organize, and maintain test cases instead of forcing them into Jira issue types. • Tracking test execution: the ability to run tests, record pass/fail results, and maintain execution history across cycles or releases. • Traceability to Jira issues: you should be able to link test cases and executions to user stories, epics, and defects for end‑to‑end coverage. • Organizing test cycles and test plans: group tests into cycles for sprints, releases, or regression suites. • Test reporting &#038; dashboards: coverage reports, execution summaries, traceability matrices, and release readiness indicators. • Native Jira experience: tests should appear inside Jira UI and workflows, minimizing context switching for teams already <a class="mh-excerpt-more" href="https://www.scrumexpert.com/tools/test-management-tools-plugins-for-jira/" title="Test Management Tools Plugins for Jira">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/tools/test-management-tools-plugins-for-jira/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</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>
		<item>
		<title>DevOps for Students: Integrating Software Testing into Continuous Integration and Deployment</title>
		<link>https://www.scrumexpert.com/knowledge/devops-for-students-integrating-softwae-testing-into-continuous-integration-and-deployment/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 25 Apr 2024 14:56:59 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[devops]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7847</guid>

					<description><![CDATA[DevOps is the integration of automation with Agile development methods to increase productivity while reducing software lifecycle costs and times. An intermediary acts as a link between developers and operations, encouraging teamwork and providing greater customer focus. Coding bootcamps are a great way to learn DevOps. For further information, you can view the page on buy bachelor thesis. Finding Testing Needs DevOps practices allow collaboration between testing and development teams. This leads to better software. DevOps does not replace traditional testing techniques, however to optimize its efficiency a group must understand the testing requirements of its team and devise effective strategies. It will help them to utilize the best tools, while also taking into consideration key issues, such as data management and maintenance of automation. Developers should only make minor changes to ensure testing runs as efficiently and as fast as possible. This helps QA do less work and allows developers to move onto other features faster. DevOps is a collaborative process that requires two teams to work together to ensure tests are properly designed and can run on different environments. Do You Have Questions About DevOps and Its Impact on Your Career? Consider enrolling in a course or certification. DevOps is a culture and mindset that can be taught in introductory courses. They also cover tools and technologies such as Jenkins and Kubernetes. Test Tools Identification There are a number of tools available to assist with the software integration, monitoring and distribution processes. DevOps software tools are designed to <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/devops-for-students-integrating-softwae-testing-into-continuous-integration-and-deployment/" title="DevOps for Students: Integrating Software Testing into Continuous Integration and Deployment">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Agile Project Management Techniques in Oracle Database Environments</title>
		<link>https://www.scrumexpert.com/knowledge/agile-project-management-techniques-in-oracle-database-environments/</link>
					<comments>https://www.scrumexpert.com/knowledge/agile-project-management-techniques-in-oracle-database-environments/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 12 Apr 2024 16:45:28 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7835</guid>

					<description><![CDATA[In the rapidly evolving world of software development and database management, agility is not just a buzzword; it&#8217;s a strategic imperative. Oracle Database environments are robust, powerful, and capable of handling significant data loads with complex structures. However, integrating Agile project management techniques into such environments can be incredibly beneficial, leading to more responsive, flexible, and timely database solutions. Leveraging Oracle DBA services and database support services within an Agile framework ensures that databases are not just robust but also adaptable to the changing needs of businesses. Agile Project Management for Database Management Systems In the dynamic field of software development, Agile Project Management (APM) has emerged as the de facto approach for ensuring smooth, efficient, and responsive workflows. A key area where Agile&#8217;s principles prove invaluable is database management systems (DBMS). Understanding and effectively leveraging the principles of APM can significantly impact how efficiently a database is designed, developed, and managed over its lifecycle. Agile encourages iterative development, which, in the context of DBMS, means improving the system progressively over time. This approach allows teams to respond swiftly to changes, whether these arise due to evolving business needs, changes in end-user requirements, or updates in technology standards. Moreover, Agile promotes greater transparency between developers, stakeholders, and end-users. Regular communication, a foundation of Agile, ensures that functional requirements and expectations are mapped, potential issues or misunderstandings can be addressed promptly, and the risk of significant discrepancies or complex problems in advanced stages is reduced. Embracing Change with Oracle DBA Services <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/agile-project-management-techniques-in-oracle-database-environments/" title="Agile Project Management Techniques in Oracle Database Environments">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/agile-project-management-techniques-in-oracle-database-environments/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Effective Project Management in Game Development</title>
		<link>https://www.scrumexpert.com/knowledge/effective-project-management-in-game-development/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 28 Mar 2024 14:27:09 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7823</guid>

					<description><![CDATA[In video game development, project management is essential as it ensures that projects are completed on time, on budget, and with the desired quality. Let&#8217;s take a look at how Agile project management can help the gaming industry today and in the future. Key Elements of Successful Project Management in Gaming Successful project management in the gaming industry requires attention to several key elements. First of all, it is very important to clearly define the scope and goals of the project. This lays the foundation for the entire development process. Creating a detailed project plan provides the team with a roadmap to follow and helps to manage resources efficiently. Another important element is the distribution of responsibilities among all team members. This ensures that everyone knows their specific tasks and contributions. Setting realistic timelines and milestones helps manage the project and ensures that it is completed on time. Regular monitoring of progress is necessary to keep track of the project and identify any deviations or issues that may arise. Making the necessary adjustments and changes as needed is an integral part of project management, as it provides flexibility and adaptability to unforeseen circumstances. Finally, effective communication is a key factor in game development projects. Open and transparent communication guarantees clarity, cooperation, and alignment between all team members. Effective Communication Strategies for Game Development Project Management Effective communication strategies are important for hidden object game developers. In complex projects, clear and open lines of communication play a crucial role in the <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/effective-project-management-in-game-development/" title="Effective Project Management in Game Development">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>6 Soft Skills To Focus On When Hiring QA Engineers for a Scrum Team</title>
		<link>https://www.scrumexpert.com/knowledge/6-soft-skills-to-focus-on-when-hiring-qa-engineers-for-a-scrum-team/</link>
					<comments>https://www.scrumexpert.com/knowledge/6-soft-skills-to-focus-on-when-hiring-qa-engineers-for-a-scrum-team/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 20 Feb 2023 16:03:26 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7392</guid>

					<description><![CDATA[No matter what project you are running, it is essential to ensure your quality assurance (QA) specialists are the perfect fit. Popular apps like NerdWallet, MyFitnessPal, and Under Armour rely on QA experts to build and test applications that meet user needs. However, when it comes to Agile projects using Scrum, there is a need to recruit top-level QA engineers with the right skills to engage effectively during a sprint before anything has been built. It is essential to focus on the must-have soft skills for quality assurance specialists that can help them perform agile testing. This article will provide valuable insights to make the hiring process easier and more cost-effective. Author: Dzmitry Seachouk, Lead of manual QA at Solvd, Inc. 1. Systematic Thinking As the team works through the testing and stabilization activities, Quality Assurance (QA) personnel should take the lead in planning, organizing, and involving the whole team in the testing work. This is similar to the role of the Scrum Master (SM) in keeping people motivated. Since many software developers don’t enjoy the testing work, it is the responsibility of the QAs and the SM to make the testing vision and goals visible to the team and to help to maintain a high level of motivation. By doing so, the team will be better equipped to perform their tasks and reach their goals. That&#8217;s why systematic thinking is essential for QA Engineers in Scrum teams. A particular skill set defines systematic thinkers in the quality assurance area <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/6-soft-skills-to-focus-on-when-hiring-qa-engineers-for-a-scrum-team/" title="6 Soft Skills To Focus On When Hiring QA Engineers for a Scrum Team">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/6-soft-skills-to-focus-on-when-hiring-qa-engineers-for-a-scrum-team/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>4 Reasons Why Scrum Needs Testers From Day 1</title>
		<link>https://www.scrumexpert.com/knowledge/4-reasons-why-scrum-needs-testers-from-day-1/</link>
					<comments>https://www.scrumexpert.com/knowledge/4-reasons-why-scrum-needs-testers-from-day-1/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 21 May 2019 07:48:54 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=5740</guid>

					<description><![CDATA[In a Scrum team, there are three roles: Product Owner, Development Team and Scrum Master. There is no explicit mention of software testers and some could question if testing specialists are really necessary in Scrum teams. After working on several projects, Eric Delahaye has found that they are and shares with us four reasons why they should be included as soon as the first Sprint Planning. Author: Eric Delahaye, Hexacta, https://www.hexacta.com/ While it is true that in theory The Scrum Guide points out that “Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis”, those of us who work in this Agile world know that Scrum itself, in an organic way, know that involving all roles that make a development possible is the key to success. Scrum recognizes the importance of each member (not only developers) as part of the team. So, what actually happens to software testers if Scrum suggests that an Agile team is fully capable of performing different tasks while being responsible for quality? Are they really necessary? Thanks to the results we have achieved in several projects, I have no doubt that THEY ARE, and they are absolutely necessary from day 1 from the first Sprint Planning! There are many ways to face testing in an Agile team that works with Scrum, especially when there are one or many testers. After years of working with this methodology, we have implemented a practice that <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/4-reasons-why-scrum-needs-testers-from-day-1/" title="4 Reasons Why Scrum Needs Testers From Day 1">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/4-reasons-why-scrum-needs-testers-from-day-1/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Example Mapping Introduction</title>
		<link>https://www.scrumexpert.com/videos/introducing-example-mapping/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 12 Mar 2018 16:37:55 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[Agile testing]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=5000</guid>

					<description><![CDATA[Before including a user story in a Scrum sprint, it is important to clarify and confirm its acceptance criteria.In recent years, lots of Agile software development teams have been using a simple collaborative technique called Example Mapping to break down user stories. It was conceived co-founder of Cucumber, Matt Wynne, who wrote the seminal post introducing the practice &#8220;Introducing Example Mapping&#8220;. In this video, the creator of Cucumber, Aslak Hellesoy, introduces Example Mapping and Aslak and Steve Tooke take questions from attendees. As Matt puts it, &#8220;Example Mapping helps you zoom in and focus on the smallest pieces of behavior inside your story. By mapping it out you can tease apart the rules, find the core of the behavior you want, and defer the rest until later. With this level of scrutiny, example mapping acts like a filter, preventing big fat stories from getting into your sprint and exploding.&#8221; Video producer: https://cucumber.io/]]></description>
		
		
		
			</item>
		<item>
		<title>Tips for Testing Software Quality in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/tips-for-testing-software-quality-in-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 06 Mar 2018 14:38:21 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Agile testing]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=4985</guid>

					<description><![CDATA[How do you manage software quality in Scrum? In traditional waterfall projects, teams will try to detect bugs in the final software testing activities like integration and acceptance tests. With the short timeframe of Scrum sprints, this approach does not work for Agile projects. In his book Scrum Product Ownership, Robert Galen provides some guidance on how to build quality software with one fundamental tip: you don&#8217;t test quality! I spend a great deal of time coaching various teams in their agile adoption journeys and make this point in every introductory class. But, inevitably after we&#8217;re done sprinting, I hear team members, cross-functional stakeholders, and executives talking about testing and quality as if they were synonymous. Read my lips. You don&#8217;t test quality. By the time you get to testing, it&#8217;s too late. Your quality has already been instantiated into your code. Instead you build quality into your DNA and work habits by individually adopting some of these values: Build quality into your stories by sitting down with actual customers and precisely understanding their challenges and usage Make your product backlogs transparent and easily available to everyone. Encourage questions and feedback. Listen deeply to your stakeholders and understand their priorities and needs. Build quality into your code by collaborating and pairing while performing more formal code reviews whenever possible, particularly on the more complex sections or areas where you&#8217;re in unfamiliar territory. If you encounter some horrible pre-existing code hacks, consistently endeavor to re-factor and improve or simplify them. Always <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/tips-for-testing-software-quality-in-scrum/" title="Tips for Testing Software Quality in Scrum">[...]</a>]]></description>
		
		
		
			</item>
	</channel>
</rss>
