<?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>change | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/change/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>change | 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>Be Strongly Agile: Show Your Weaknesses</title>
		<link>https://www.scrumexpert.com/knowledge/be-strongly-agile-show-your-weaknesses/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 15 Sep 2026 15:31:28 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8842</guid>

					<description><![CDATA[I am frequently amused when the same people who believe that it is not possible to get the requirements for a product correct up front, and therefore want to use Scrum for development, will in the next breath explain how they aren’t quite ready to start using Scrum because they haven’t worked out all of the details of their Scrum approach! This type of thinking is poorly aligned with fundamental Scrum principles. When employing Scrum, you shouldn’t worry about getting things perfect up front. You can’t! And trying to be perfect up front will force you to guess at the expense of important learning that you will get only by applying Scrum and seeing what happens. In my experience, most teams’ first couple of sprints aren’t all that pretty. That’s OK. My only expectation of any Scrum team is that it be better in the next sprint than it was in the previous sprint. So, don’t delay getting started. Whatever you think you know now about your use of Scrum, imagine how much more you will really know after you start and finish the next sprint! Also, don’t expect your Scrum adoption to be problem free. I can guarantee that at some point your organization will encounter impediments that make performing Scrum difficult. Scrum makes visible the dysfunctions and waste that prevent organizations from reaching their true potential. What it does not do is tell organizations how to solve those issues. That hard work is up to the people in <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/be-strongly-agile-show-your-weaknesses/" title="Be Strongly Agile: Show Your Weaknesses">[...]</a>]]></description>
		
		
		
			</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>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>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>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>
		<item>
		<title>Managed Evolutionary Change in Agile</title>
		<link>https://www.scrumexpert.com/videos/managed-evolutionary-change-in-agile/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 19 Sep 2025 11:31:32 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8440</guid>

					<description><![CDATA[This presentation explores managed evolutionary change by designing experiments to solve some of the problems that your Agile organizations or Scrum teams have. Using managed evolutionary change can help navigate the complexities of change and ensure long-term success in today&#8217;s dynamic business environment. In today&#8217;s dynamic business landscape, organizations face the constant need to adapt to change and evolve to stay ahead. Traditional change management approaches often fall short in addressing the complexities and uncertainties associated with continuous improvement. Evolutionary change is a powerful management approach that embraces small incremental changes starting with what you do now. In order to have effective evolutionary change, it is critical to emphasize the importance of continuous feedback loops, empowering teams to learn from their experiences and adapt accordingly. Scrum tells team members to “inspect and adapt,” but what does that mean? Through regular reflection and data-driven analytics, organizations can foster a culture of continuous improvement, where evolutionary change becomes the norm rather than a disruptive event. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Eight Steps For Implementing Successful Change in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/eight-steps-for-implementing-successful-change-in-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 03 Mar 2025 16:02:37 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8256</guid>

					<description><![CDATA[Implementing Agile and Scrum in software development organization means a big change. In her book &#8220;The Great ScrumMaster&#8220;, the Agile coach Zuzana Šochová recommends an eight steps journey for a successful transformation to the Scrum approach. The second important concept about change management describes a process for implementing successful change in eight steps. It addresses those change phases. First, you set the stage. Next, you decide what to do and make it happen. And finally, you make it stick. Create a Sense of Urgency The very first step before you implement any change is to create a sense of urgency. Make the change necessary, because until you feel pain in your current processes, there is no need for improvement. And it doesn’t matter if the desired change is huge, like an Agile transformation, or small, like using Git instead of CVS. Without good motivation and a good reason there will be no change. Be honest and transparent in presenting both the opportunities and the threats; otherwise you might lose the trust of others. Guiding Team As one individual, it’s hard to change anyone. You should focus on early adopters and encourage them to become part of your team. You need people who are passionate, good communicators, and leaders. Make the group diverse. It shouldn’t follow any organizational structures if it is to access a broader audience. In general, if there are three of you, you already have the ability to create a snowball effect by attracting others. Creating a change <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/eight-steps-for-implementing-successful-change-in-scrum/" title="Eight Steps For Implementing Successful Change in Scrum">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Surviving in a Rapidly Changing Post-Agile World</title>
		<link>https://www.scrumexpert.com/videos/surviving-in-a-rapidly-changing-post-agile-world/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 10 Jan 2025 16:18:33 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[change]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8189</guid>

					<description><![CDATA[This presentation empowers you to evolve from conventional Agile and cultivate a culture of continuous growth. Of course, it offers a treasure trove of real-life stories from the trenches, providing an authentic glimpse into Agile but redefined for the modern era. This talk will help your Agile organization to get unstuck. This is the era of rapid and increasing change, adapting rapidly or perishing. Many organizations, big and small, struggle to survive. Their products and software have aged and become hard to maintain until they reach Technical Death, where all available effort goes into mere survival. At the same time, in our global economy, competition comes from anywhere, with better products built at lower costs. Organizations must jump the Innovators’ Dilemma and reinvent themselves to stay ahead of the competition. Speed, agility, and adaptability are more crucial than ever for Scrum teams. However, agile frameworks became both a solution and a source of uncertainty and rigidity. Organizations seek fresh perspectives and adaptable strategies and techniques. They are stuck. This video presents a battle-tested repertoire of practical strategies and techniques that serve as a compass for comprehending and continuously navigating between maintenance, renovation, and innovation, maintaining a solid focus on customer-centricity, reaching your dot on the horizon while instilling transparency, autonomy, and collaboration. These strategies involve leveraging proposed tools such as idea funnels, tech boards, collectives and microteams. Video producer: https://voxxeddays.com/]]></description>
		
		
		
			</item>
	</channel>
</rss>
