<?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>scrum team | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/team/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Mon, 15 Jun 2026 20:51:08 +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>scrum team | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Nine Questions for a Good Scrum Team Structure</title>
		<link>https://www.scrumexpert.com/knowledge/nine-questions-for-a-good-scrum-team-structure/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 14 Apr 2026 14:07:40 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Quotes]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8723</guid>

					<description><![CDATA[In his book “Succeeding with Agile”, Mike Cohn present nine questions that you should ask for a current or proposed team. Questions should be asked iteratively&#8230; until you answer “yes” to each. Here are the questions: * Does the structure accentuate the strengths, shore up the weaknesses, and support the motivations of the team members? * Does the structure minimize the number of people required to be on two teams (and avoid having anyone on three)? * Does the structure maximize the amount of time that teams will remain together? * Are component teams used only in limited and easily justifiable cases? * Will you be able to feed most teams with two pizzas? * Does the structure minimize the number of communication paths between teams? * Does the structure encourage teams to communicate who wouldn’t otherwise do so? * Does the design support a clear understanding of accountability? * Did team members have input into the design of the team? Reference: “Succeeding with Agile”, Mike Cohn, Addison-Wesley, 463 pages, IBSN 978-0-321-57936-2 Besides the cultural bias (in Italy, one pizza will usually feed one person, but it might be different in the USA&#8230;), you could use these questions for every Agile project that you are currently running or plan to run to check the quality of your Scrum team.]]></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>Free Retrospective Tools for Distributed Scrum Teams</title>
		<link>https://www.scrumexpert.com/tools/free-retrospective-tools-for-distributed-scrum-teams/</link>
					<comments>https://www.scrumexpert.com/tools/free-retrospective-tools-for-distributed-scrum-teams/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 23 Mar 2026 08:00:50 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Tools]]></category>
		<category><![CDATA[distributed teams]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2950</guid>

					<description><![CDATA[Even if Agile approaches favor collocated teams, distributed Scrum teams with remote work are more common that what you might think. Many Agile software development teams are based on a virtual organization. This article presents some free online retrospective tools that can be used to facilitate retrospectives for distributed and remote Scrum teams. You will find in this article only online Scrum retrospective tools that are supposed to be used for free in the long term. We do not list tools that offer only a free trial based on duration or the number of retrospectives. We will also only mention the tools that have features specifically dedicated to Agile and Scrum retrospectives. There are many other tools that Scrum teams might use, from video conferencing platforms to online whiteboard software. Mentioning all these tools will result more in a book than an article. If you want to add a tool that fits these requirements to this article, just let us now using the contact form. Free retrospective tools for distributed scrum teams listed in this article are EasyRetro, Retro Cadence, RetroTeam, Reetro, IdeaBoardz, Metro Retro, Pointing Poker, Retro Cadence, Retrospected / Retro-Board, Retrospect.team, Scrumlr, Sprint Boards, Stormboard, Swift Board. Updates March 23 2026: added Mural, RetroTime, RetroTool.io, removed GoRetro (no more free plan), Metro Retro (renamed as Ludi, no more free plan), Retro Cadence (domain expired), May 7 2024: added Kollabe, Return removed postfacto (open source tool archived) December 5 2022: added EasyRetro, Miro, RetroTeam, Swift Board January 17 2022: <a class="mh-excerpt-more" href="https://www.scrumexpert.com/tools/free-retrospective-tools-for-distributed-scrum-teams/" title="Free Retrospective Tools for Distributed Scrum Teams">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/tools/free-retrospective-tools-for-distributed-scrum-teams/feed/</wfw:commentRss>
			<slash:comments>29</slash:comments>
		
		
			</item>
		<item>
		<title>AI Assistance for Software Teams: an Overview</title>
		<link>https://www.scrumexpert.com/videos/ai-assistance-for-software-teams-an-overview/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 12 Jan 2026 21:03:51 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8547</guid>

					<description><![CDATA[After almost two years of high attention on coding assistants, many software engineering managers are disappointed by the measurable results. Software developers are suffering from hype fatigue, even the ones who have learned to love their new AI teammate. Meanwhile, the pace of change in the AI tooling space is still quite high, which contributes further to the hype fatigue. This presentation gives an overview of the tooling and features available today, what works and what doesn&#8217;t, and what might work with more technical advances. It will mostly focus on AI assistance for tasks that involve writing, reading and changing code, but also touch on software delivery tasks that don&#8217;t touch code directly, like requirements analysis. This whirlwind tour of the AI tooling landscape is based on the presenter&#8217;s experience as Thoughtworks&#8217; global SME for AI-assisted software delivery. Video producer: https://gotocph.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Agile Teams: Building a Collaborative Scrum Team</title>
		<link>https://www.scrumexpert.com/knowledge/agile-teams-building-a-collaborative-scrum-team/</link>
					<comments>https://www.scrumexpert.com/knowledge/agile-teams-building-a-collaborative-scrum-team/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 05 Jan 2026 18:20:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8532</guid>

					<description><![CDATA[How do you get people to work effectively as a team? Instead of reorganizing every two weeks, maybe we should focus on what makes teaming work. Books and blogs focus on psychological safety, communications, trust, personal growth, and a shared purpose. These are good things to be sure, but how do you get there? I&#8217;ve experienced dysfunctional teams and apathetic ones more often than not; once burned, trust is not something easily given. How do you fix a broken heart and build a team? I think collaboration is your best approach, and should be encouraged whenever possible. Author: Mark Haynes, https://www.linkedin.com/in/donald-mark-haynes-csm-745a609/ Scrum is an ideal framework for a collaborative approach. The Daily Scrum, also known as the Daily Stand-up, is a team support mechanism. The focus is on team goals, not on status reporting. The Retrospective encourages an open, honest assessment of what worked and what didn&#8217;t. It encourages self-empowered teams. A small team size reduces the likelihood of communication problems. Agile embraces the Servant Leadership principles. Still, Scrum teams have been known to fracture and break into isolated, antagonistic cliques. Scrum is the start, but we need more than good intentions. We need to create a culture of agility and collaboration. Consider using collaborative approaches to increase your team&#8217;s effectiveness. Engage your team using collaborative techniques, such as workshops and Whiteboarding sessions. There isn&#8217;t a magic formula, but there are a few pathways you should consider. Encouraging teamwork and collaboration Why do Scrum teams fail? Are you implementing Agile <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/agile-teams-building-a-collaborative-scrum-team/" title="Agile Teams: Building a Collaborative Scrum Team">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/agile-teams-building-a-collaborative-scrum-team/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Team Size &#8211; Why Less Is More</title>
		<link>https://www.scrumexpert.com/knowledge/team-size-why-less-is-more/</link>
					<comments>https://www.scrumexpert.com/knowledge/team-size-why-less-is-more/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 28 Oct 2025 22:00:35 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[people]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8471</guid>

					<description><![CDATA[Sizing an Agile team is not an easy task. In this article, Mark Haynes discusses some of the factors (control, the nature of the work, optimal communications) that will influence the decision for the size of a Scrum team. Author: Mark Haynes, https://www.linkedin.com/in/donald-mark-haynes-csm-745a609/ We live in a world of knowledge workers, so why do we persist in building organizational pyramids? We know that development team members aren&#8217;t a fungible resource, yet we persist in traditional organizational structures. Are you motivated towards larger teams, due to one of these axioms: Many hands make light work, or More people provide more diversified skills, or More eyes create a better solution. The Many Hands Fallacy The Pareto Principle states that 80% of the output is produced by 20% of the workers. Why would adding additional people significantly increase the output? Those two or three people who do most of the productive work are now carrying a much larger load. Ask yourself, have additional people proportionally increased productivity, or has it increased frustration and staff turnover? All The Necessary Skills Fallacy Agile prioritizes flexibility over economies of scale. One constant in a continually changing technical environment is that our work is unpredictable. So, how can you predict the required future skill sets? Trying to staff all possible contingencies will quickly create large, unmanageable teams. What do you do if a skill set becomes unnecessary? Do you eliminate that person or hang on to them just in case? Maybe they will grow into their job, <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/team-size-why-less-is-more/" title="Team Size &#8211; Why Less Is More">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/team-size-why-less-is-more/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Free Online Scrum Tools</title>
		<link>https://www.scrumexpert.com/tools/free-online-scrum-tools/</link>
					<comments>https://www.scrumexpert.com/tools/free-online-scrum-tools/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 21 Aug 2025 14:00:13 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Tools]]></category>
		<category><![CDATA[distributed teams]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2310</guid>

					<description><![CDATA[Agile approaches like Scrum recommend a &#8220;just enough&#8221; attitude in software development and this is also the case when you discuss tools. Ideally, you would work with a small team that is collocated, but this is not always possible and you might be running your project virtually with a distributed Scrum team scattered around the world. If you don&#8217;t want to start using a sophisticated tool to manage your efforts, you might be interested in adopting some web tools that will fit your particular need to share some project information or status among all the team members. This article presents some online tools that are based on Scrum and Agile approaches, that implement specific Agile practices (backlog management, burndown chart) and that are freely available (no commercial/paid version!) on the web for distributed Scrum teams. Retrospective tools are not mentioned in this article, as we wrote a specific article about free retrospective tools for distributed scrum teams. The open source Scrum planning poker tools have been listed in a separate article like Open Source Planning Poker Tools. We will not present in this page the free option offered by commercial Scrum tools vendors, neither some free offer from tools that are still in their beta stage. You will find only Agile tools with no commercial option that are completely free (and supposed to stay so forever). If you want to add a free online Scrum tool to this page, just let us know using the comment form or the contact <a class="mh-excerpt-more" href="https://www.scrumexpert.com/tools/free-online-scrum-tools/" title="Free Online Scrum Tools">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/tools/free-online-scrum-tools/feed/</wfw:commentRss>
			<slash:comments>12</slash:comments>
		
		
			</item>
		<item>
		<title>Navigating the Rocky Path to Successful Feature Teams</title>
		<link>https://www.scrumexpert.com/videos/navigating-the-rocky-path-to-successful-feature-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 28 Jul 2025 16:29:39 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8410</guid>

					<description><![CDATA[This presentation explores the challenges and opportunities of transitioning from Component Teams to cross-functional Feature Teams, examining the dynamics of unchanged individual functional roles and considering both short and long-term development strategies. Video producer: https://less.works/]]></description>
		
		
		
			</item>
		<item>
		<title>Introduction to the Agile Retrospective: The Why, The What, and The How</title>
		<link>https://www.scrumexpert.com/knowledge/introduction-to-the-agile-retrospective-the-why-the-what-and-the-how/</link>
					<comments>https://www.scrumexpert.com/knowledge/introduction-to-the-agile-retrospective-the-why-the-what-and-the-how/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 16 Apr 2025 08:35:47 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8296</guid>

					<description><![CDATA[Agile retrospectives are a cornerstone of continuous improvement, enabling teams to reflect, adapt, and enhance their processes. Whether you call it a Sprint Retrospective, Iteration Retrospective, or Team Retrospective, the goal remains the same-identify what&#8217;s working, what&#8217;s not, and how to improve. Author: Edo Williams, RetroTeam AI In this article, we explore the origins, benefits, and best practices of retrospectives and provide actionable insights on how to implement them effectively. The Origins and Evolution of Agile Retrospectives Agile retrospectives have been around since the early days of Agile. Their foundation can be traced back to 1997, when Alistair Cockburn described reflection workshops in his book Surviving Object-Oriented Projects. By 2001, the concept gained traction with the Agile Manifesto, which emphasized: &#8220;At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.&#8221; Norman L. Kerth further popularized retrospectives in his book Project Retrospectives: A Handbook for Team Reviews. Later, Esther Derby and Diana Larsen reinforced their importance in Agile Retrospectives: Making Good Teams Great. Today, retrospectives are a vital practice in Agile methodologies like Scrum, SAFe, and Kanban. What is an Agile Retrospective? An Agile retrospective is a structured meeting where a team reflects on their last sprint or iteration. The purpose is to inspect past work, adapt strategies, and drive continuous improvement. During a retrospective, teams typically answer three key questions: What went well? What didn&#8217;t go well? How can we improve? However, retrospectives go beyond simple reflections. Different formats and facilitation <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/introduction-to-the-agile-retrospective-the-why-the-what-and-the-how/" title="Introduction to the Agile Retrospective: The Why, The What, and The How">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/introduction-to-the-agile-retrospective-the-why-the-what-and-the-how/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Team Transformation Canvas: Team Building Starts With You</title>
		<link>https://www.scrumexpert.com/videos/team-transformation-canvas-team-building-starts-with-you/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 19 Mar 2025 18:27:37 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[scrum team]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8273</guid>

					<description><![CDATA[If you want an easy tool to help you start building the best Scrum team, then you should explore the Team Transformation Canvas. It is a practical worksheet to help you and your Agile teammates discover the best in each other and put it into action. The Team Transformation Canvas facilitates individual self-awareness of their current emotional state and their desired personal outcomes. They develop a deepened understanding of what drives their behaviors and actions. By identifying and owning these intrinsic motivations, participants align their future actions with their most inherent needs—creating their own unique pathway to professional and personal self-actualization. Finally, the canvas facilitates deep emotional and supportive connections with each other—the building blocks of a high-performance Scrum team. The canvas can be used as a solitary contemplative exercise for self-improvement, or as a tool for bootstrapping a Scrum team toward intentional greatness. This video provides actionable next steps to improve you and your Agile teams. You will know how to use the canvas with your own teams, to help other individuals and teams gain deeper insight into themselves, so they can pursue their greatness. For those familiar with the Core Protocols, the canvas facilitates a superfast individual and team boot-up. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
	</channel>
</rss>
