<?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>self organized team | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/self-organization/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Fri, 09 Oct 2026 15:07:29 +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>self organized team | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<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>Overcome Self-Organization Blocks</title>
		<link>https://www.scrumexpert.com/videos/overcome-self-organization-blocks/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 17 Sep 2015 14:19:28 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2773</guid>

					<description><![CDATA[We know that self-organization is a critical aspect of every successful Agile project and we know that it takes trust, respect, openness and responsibility. So why many teams have a hard time to achieve it? Self-organization changes the leader/team dynamics and the teammate/teammate ones. Resistance may arise and the source is frequently rooted in mental habits, such as a latent blaming culture, confusing guidance and command, fear of taking responsibility or losing status, unconscious personal agendas. Attend this session to learn how to deal with organizational issues such as: * Creating team’s cohesion; counteracting division * Positioning yourself at your proper guidance level * Identifying a latent blaming culture and mitigate its consequences * Understanding the manager’s and team’s roadblocks to self-organization * Making your team collaborate more smoothly Video producer: http://leanagile.scot/]]></description>
		
		
		
			</item>
		<item>
		<title>Scrum Teams: Courage, Openness, Pigs and Chickens</title>
		<link>https://www.scrumexpert.com/videos/scrum-teams-courage-openness-pigs-and-chickens/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 19 Dec 2013 19:58:27 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1741</guid>

					<description><![CDATA[The board game Othello has the slogan: &#8220;A minute to learn, a lifetime to master.&#8221; This applies really well to a team that’s learning Scrum. The basic practices and mechanics of Scrum are straightforward, and not difficult to adopt. The basic pattern for a Scrum project is simple, which makes it very attractive for teams who want to go agile. And if that were all it took to adopt Scum effectively, we’d all be running great agile teams! But many teams find that they run into trouble with their Scrum adoption, and usually end up with what feels like an “empty” implementation. We explore the reasons behind this in our new talk, Scrum and Self-Organizing Teams: Openness, Courage, Pigs, and Chickens. [youtube GCH04X426Ps] Video producer: NY SPIN &#8211; New York Software &#38; Systems Process Improvement Network Slide from the presentation: http://www.stellman-greene.com/blog/wp-content/uploads/2012/06/Scrum-and-Self-Organizing-Teams.pdf]]></description>
		
		
		
			</item>
		<item>
		<title>Self-Organization of Scrum Adoption</title>
		<link>https://www.scrumexpert.com/knowledge/self-organization-of-scrum-adoption/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 27 Nov 2013 18:05:36 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1716</guid>

					<description><![CDATA[How will an organization that is already truly self-organized before Agile changes its process to adopt a framework like Scum? In this blog post, the Lomio team, a worker-owned cooperative company with no bosses, discusses how they embrace Scrum. They start by writing that adopting Scrum is painful. The exact quote is &#8220;Because we’re stubborn, we had to learn the hard way, by making mistakes. More than a few times, just as we thought something we were building was nearing completion we’d realize it was not quite right (or even very wrong). Or things would take way longer than we thought. Or people would get frustrated at the way the team was working.&#8221; This is a real life account of the issues linked with total self-organization. In this specific case, an Agile coach might have helped the team progress faster. The Lomio realized that to get the full benefits of Scrum, you must adopt it completely and follow it to the rule. Retrospectives were an important tool for the Scrum adoption process. The post presents some of the facilitation techniques that have worked for the team. It also discusses an example of how their processes improved with formal retrospectives. Then it discusses how they manage the new Scrum roles in their team. Finally, this long post ends with a &#8220;lesson learned&#8221; section. Read the complete blog post on http://blog.loomio.org/2013/11/20/occupy-scrum/]]></description>
		
		
		
			</item>
		<item>
		<title>Self-Designing Scrum Teams</title>
		<link>https://www.scrumexpert.com/knowledge/self-designing-scrum-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 08 Oct 2013 21:14:11 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1658</guid>

					<description><![CDATA[In this article, Craig Larman and Ahmad Fahmy discuss how long does it take an organization to reorganize in order to adopt Scrum. This article is based on the transition done at Bank of America&#8217;s Merrill Lynch Global Securities Operations Technology where the software development teams went from a traditional activity based organisation (business analysts, developers, &#8230;) to Scrum. There were two constraints on design of the teams: * Teams needed to be co-located. * Teams needed to be cross-functional and cross-component; they should be able to (or be able to learn to) deliver any item from the product backlog. The self-designing session was divided in four cycles of 25 minutes, with a five-minute review at the end of each, plus some breaks. Initially, teams tended to be formed on former working habits of working together. During the review, each team&#8217;s composition was assessed and gradually the situation changed to teams having a more balanced skills composition. In a final step, each team selected its ScrumMaster. The conclusion of the article is that &#8220;it&#8217;s worth noting how much can be quickly changed when the organizational will and appropriate hands-on worker and leadership support is in place. And it&#8217;s worth noting that, with some facilitation, people are quite capable of deciding among themselves how to organize into teams, without command-and-control management.&#8221; Read the complete article on http://www.scrumalliance.org/community/articles/2013/2013-april/how-to-form-teams-in-large-scale-scrum-a-story-of]]></description>
		
		
		
			</item>
		<item>
		<title>Self-Organization and Estimation in Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/self-organization-and-estimation-in-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 06 Feb 2013 13:44:24 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[estimating]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1387</guid>

					<description><![CDATA[In Scrum the estimation effort and accuracy depend on the team. In this article, Jingjie Wang discusses the situation where the Scrum team tends to underestimate its capacity to deliver so to be sure that the product owner and the scrummaster are always happy at the end of each sprint because everything promised is deliver. But in Scrum the productivity is as important as the production of the team and this is an issue that must be addressed. Jingjie Wang proposes two tools that can help to monitor the productivity of the team: * Using story points rather than hours or days to estimate * Recording and reviewing the velocity of each sprint Jingjie Wang explains that improvement should not only come from monitoring productivity, but that it is also the job of the ScrumMaster to keep the team inspired and more aggressive on its commitment. In his case, he experiment by reducing the span of a Sprint from 15 days into 8 days, without decreasing the scope. All committed tasks were finished without any compromise in quality.]]></description>
		
		
		
			</item>
		<item>
		<title>Using Lean to Create Context for Self Organization</title>
		<link>https://www.scrumexpert.com/videos/using-lean-to-create-context-for-self-organization/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 29 Aug 2012 16:32:54 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[lean]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[self organized team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1197</guid>

					<description><![CDATA[Learn how to achieve multiple team collaboration in large scale software development projects. Self-organization is a key concept for all Lean-Agile methods. However, as projects expand across the enterprise and, more specifically, cut across multiple teams, teams clearly can’t just organize in any way they want to. A blend of top-down direction with bottom-up self organization is needed. Lean provides the insights necessary for teams to self-organize within the context of the value stream within which the teams work. A top-down perspective, created by driving from business value, can provide insights on how teams must organize and work together. This talk presents some case studies where the principles of Lean-Flow provide the guidance for multiple teams to self-organize as a bigger team. This guidance includes how providing work to the teams can effectively lower the coordination necessary. This determination of work to be done typically must be decided not by the teams themselves but by proxies for the business stakeholders. Essentially, quick delivery at scale often requires decisions about what the teams are to work on before the work hits the teams themselves. These decisions provide the context within which the teams then self-organize to implement the value to be delivered. Watch this video on Vimeo]]></description>
		
		
		
			</item>
	</channel>
</rss>
