<?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 Videos | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/category/videos/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 02 Nov 2026 19:22:16 +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 Videos | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Agile Team Adaptability: When Is It Time to Change?</title>
		<link>https://www.scrumexpert.com/videos/a-talk-on-adaptability-when-is-it-time-to-change/</link>
					<comments>https://www.scrumexpert.com/videos/a-talk-on-adaptability-when-is-it-time-to-change/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 02 Nov 2026 19:17:59 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[feature1]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8890</guid>

					<description><![CDATA[Working in software development means everything around us is in a constant state of change. Tools, requirements, process, maybe even team members! When things around you change, do you scream, “Why are we always Changing things?” or “What if we just wait?”. Or do you instead embrace it and ride the wave of change and innovation? The ability to recognize and adapt to change as it is happening can make or break the success of yourself, your team, or your organization. Think you’re adaptable? How do you know? We’ve all heard of IQ, but what about… AQ? Not just another acronym, your AQ represents a concrete score of your Adaptability Quotient. Come learn how you can be more aware of your own adaptability, and respond to our complex, ever-changing world. In this session, This presentation explains AQ in real-world terms, and show us how to measure, test, and most importantly, develop our adaptability. You will learn tools and practices to help you and your Agile teams effectively roll with the random chaos that life throws your way. Video producer: https://gotochgo.com/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/a-talk-on-adaptability-when-is-it-time-to-change/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Autonomy &#038; Self-Organization: From Buzzword to Business Value</title>
		<link>https://www.scrumexpert.com/videos/autonomy-self-organization-from-buzzword-to-business-value/</link>
					<comments>https://www.scrumexpert.com/videos/autonomy-self-organization-from-buzzword-to-business-value/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 09 Oct 2026 15:07:29 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[feature1]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8875</guid>

					<description><![CDATA[This presentation demystifies autonomy and self-organization in Scrum teams, exploring their real-world applications and benefits. You will gain the clarity and confidence to explain how autonomous teams function effectively in organizations. You will also be armed with arguments to steer endless autonomy debates back toward what really matters—creating value that drives Agile organizations forward. Autonomy: a word that excites some, frustrates others, and often leaves organizations divided. But what does autonomy truly mean in practice, and how can it deliver measurable value for Scrum teams? Is it the key to success, or just another management headache? Beyond the theory, this video dives into practical insights, addressing common challenges and questions drawn from years of client work and training sessions. From fostering accountability to improving collaboration between autonomous teams, this session equips you with the tools and mindset to make autonomy work—not just as a concept, but as a driver of success. Key Takeaways: 1. The Truth About Autonomy: Gain a clear, actionable understanding of autonomy and self-organization, and the tangible value they bring. 2. Practical Collaboration Tips: Tips and tricks to enhance cooperation and alignment between autonomous teams. 3. Facilitating Ownership: Discover how to cultivate responsibility and engagement in teams and employees. 4. Debate with Confidence: Equip yourself with compelling arguments to refocus autonomy discussions on outcomes and value. Video producer: https://ndcoslo.com/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/autonomy-self-organization-from-buzzword-to-business-value/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Product Owner Triangle of Tension: Wants, Needs &#038; Feasibility</title>
		<link>https://www.scrumexpert.com/videos/the-product-owner-triangle-of-tension-wants-needs-feasibility/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 13 Aug 2026 15:55:39 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[feature1]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[product owner]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8830</guid>

					<description><![CDATA[How do you manage the inevitable tension between what stakeholders want, what is needed, and what’s feasible? As Product Managers or Product Owners, we constantly navigate this &#8216;Triangle of Tension,&#8217; balancing human dynamics with practical constraints. The Triangle of Tension isn’t a problem to solve, it’s a dynamic to embrace. Success lies in navigating it with clarity, boldness, and empathy. As more organizations adopt Agile product practices, expectation management becomes increasingly critical. Misalignment between stakeholders and Scrum teams can stall progress and erode trust. This talk offers practical advice for transforming that tension into a force for collaboration and delivery, equipping Product Owners or Product Managers to approach these challenges with confidence. Drawing on 15 years of experience, including a recent case study with a charity client, the presenter shares her mistakes, lessons learned and actionable strategies for managing expectations, fostering trust, and aligning your Agile teams for success. Video producer: https://www.agileonthebeach.co.uk/]]></description>
		
		
		
			</item>
		<item>
		<title>The 3 S of User Stories: Simple; Single; Specific</title>
		<link>https://www.scrumexpert.com/videos/the-3-s-of-user-stories-simple-single-specific/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 30 Jul 2026 15:36:37 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8822</guid>

					<description><![CDATA[User stories are the cornerstone of Agile requirements. Scrum teams use them to plan and deliver solutions that meet their users’ needs. Beyond just solution requirements, user stories focus on value delivery from the perspective of the user, describing the capabilities needed, as well as the benefits they would provide. However, user stories can be tricky to write by Agile teams in a way that they are understood by our stakeholders and the delivery team. We may believe that everyone knows what is expected to be delivered, but then find we are wrong. All too often, stories are not delivered because they are misunderstood, too big, not scoped correctly, or missing detail. This session will explore how to write effective user stories using the three “S” of User Stories : Simple; Single; Specific. These three simple guidelines can help us to assess our user stories to ensure they are sized appropriately and well understood, enabling continuous value delivery by the Scrum team. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Refactoring Legacy Applications the Right Way</title>
		<link>https://www.scrumexpert.com/videos/refactoring-legacy-applications-the-right-way/</link>
					<comments>https://www.scrumexpert.com/videos/refactoring-legacy-applications-the-right-way/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 13 Jul 2026 23:27:42 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8810</guid>

					<description><![CDATA[If you have worked in a legacy codebase or &#8216;big ball of mud&#8217;, you know that it can make development unnecessarily slow, frustrating and costly. The solution, many developers would say, is to just rewrite the whole thing. But good luck getting every stakeholder to agree to such a costly and risky refactoring process. This presentation takes a look at the different ways you can clean up your codebase, while minimizing risk and costs. It discusses some of the different legacy codebase refactoring strategies like the &#8216;Strangler Fig Pattern&#8217; and the presenter gives you a few tips and best-practices on how you can avoid the same mistakes in the future. Video producer: https://oredev.org/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/refactoring-legacy-applications-the-right-way/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Prioritize What Truly Matters in Backlog to Focus on Results</title>
		<link>https://www.scrumexpert.com/videos/prioritize-what-truly-matters-in-backlog-to-focus-on-results/</link>
					<comments>https://www.scrumexpert.com/videos/prioritize-what-truly-matters-in-backlog-to-focus-on-results/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 24 Jun 2026 14:19:12 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[product backlog]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8787</guid>

					<description><![CDATA[This presentation explains how an organization moved from 17 component backlogs to one shared, results-focused product backlog—and what that changed for delivery speed and alignment. The presenters explain how “autonomous” component teams optimized for local work, not customer value, creating high WIP, heavy dependencies, and long lead times. By restructuring into cross-functional feature teams, running one shared cadence, and prioritizing work for the whole product, they dramatically improved flow. The talk also covers their next step: shifting from output (features) to outcomes (user behavior change) using continuous discovery. The key outcomes from the changes in product backlog prioritization approach were: Time-to-market reduced from ~7 months to ~40 days Up to 80% shorter delivery time (≈5× faster) Same people—better structure, clearer priorities Video producer: https://less.works/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/prioritize-what-truly-matters-in-backlog-to-focus-on-results/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Architecture and Agile: the Meeting of the Undead</title>
		<link>https://www.scrumexpert.com/videos/architecture-and-agile-the-meeting-of-the-undead/</link>
					<comments>https://www.scrumexpert.com/videos/architecture-and-agile-the-meeting-of-the-undead/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 09 Jun 2026 19:09:39 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[software architecture]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8765</guid>

					<description><![CDATA[Twenty years ago, Architecture was murdered in its sleep by Agile, as part of the assassination plot against the arch-enemy Waterfall. Fast-forward to today, and Agile isn&#8217;t looking too healthy either: reduced to hollow-eyed cargo culting and pointless rituals, wading through the debris of methodology pop culture, or bloated to a monstrous parody of itself in order to scale. But death aside, they are both still among us, and moaning for brains. Why? One reason might be that the problems that Architecture and Agile set out to fix have not been solved. Or they need continuous solving, and in the absence of new life to tackle them, we animate our dead. What are these problems, and how do we see them today? Have we learned anything from the death of these two grand attempts at fixing software development, and their refusal to lie down even in the face of death? Is there still something that can be found in the black hearts of the undead that can be of use in addressing the problems we face? Should Agile and Architecture be revived or put out of their misery for good? Will we be able to? What new kind of life do these two half-lives point towards? What acts of bravery will be required of us going forward with Agile Architecture? Video producer: https://ndcoslo.com/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/architecture-and-agile-the-meeting-of-the-undead/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Agile in Security and Security in Agile</title>
		<link>https://www.scrumexpert.com/videos/agile-in-security-and-security-in-agile/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 21 May 2026 16:01:16 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[security Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8746</guid>

					<description><![CDATA[This presentation explores how Agile and security works together in an Agile banking environment. Is security conflicting with Agile methodologies? Scrum or Kanban, which one is better with Agile and fast and secure delivery? The following topics are discussed in this presentation: Looking for ways to improve our delivery securely. Is security a bottleneck? Let&#8217;s integrate security in our CI/CD pipelines. Don&#8217;t forget about security open source project: OWASP is playing an important role in today security world. We want to deliver software faster and more secure. Video producer: https://www.devoxx.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Learn the Culture First, Before Going Agile!</title>
		<link>https://www.scrumexpert.com/videos/learn-the-culture-first-before-going-agile/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 06 May 2026 17:18:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8733</guid>

					<description><![CDATA[Agile is everywhere. Everybody is talking about it. Everybody wants to start the Agile journey with the various Agile frameworks like Scrum. And then, many hit the ceiling and give up the Agile journey altogether. This interactive session shares the story of how an organization started with understanding its culture first and then brought agility that sustained. At the end of the video, you will: * learn where to start when bringing agility into the organization. * become aware of why it is important to have a systemic view when bringing agility into the organization. * get introduced to a model to identify your current and desired organizational culture. Video producer: https://agileswarming.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Scaling Agility in Customer Experience at Ford Motor Company</title>
		<link>https://www.scrumexpert.com/videos/scaling-agility-in-customer-experience-at-ford-motor-company/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 05 Mar 2026 17:29:55 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[scaling Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8609</guid>

					<description><![CDATA[Benjamin Igna worked with Ford Motor Company and lead the transformation within the launch of the new Ford Explorer (EV). In this presentation, he shares his learnings and approaches during the change towards agility of the CX organization across 5 different Markets and cultures affecting multiple hundred people in sales and marketing. Here are some of his thoughts about agility: &#8220;With the hidden story of agility in mind, the advancement of various approaches, examples of the successful application of agile techniques and my personal experience, I would like to leave you with three final thoughts: The essence of agility stems from the discovery phase of a product and not its delivery. This understanding underlines the need to carefully analyse the context in which a team operates and to select and adapt the appropriate framework accordingly. The uniqueness of each project, due to specific technological challenges and industry-specific requirements, makes it almost impossible to provide an all-encompassing solution with a single framework. Kelly Johnson could never have developed an mRNA vaccine in a smelly tent. And certainly with SAFe 6.0, the development of the P80 shooting star would have taken longer than 143 days. Agile methods provide a valuable framework, but their true strength lies in their flexibility and adaptability to the situation at hand. Teams should not blindly rely on the guidelines of a framework, but use its principles as a guide to find their own way. Technology is developing rapidly and industries are facing constantly changing challenges. What was <a class="mh-excerpt-more" href="https://www.scrumexpert.com/videos/scaling-agility-in-customer-experience-at-ford-motor-company/" title="Scaling Agility in Customer Experience at Ford Motor Company">[...]</a>]]></description>
		
		
		
			</item>
	</channel>
</rss>
