<?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>Headline | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/category/headline/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Thu, 01 Oct 2026 12:39:28 +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>Headline | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Jira Retrospectives Plugins</title>
		<link>https://www.scrumexpert.com/tools/jira-retrospectives-plugins/</link>
					<comments>https://www.scrumexpert.com/tools/jira-retrospectives-plugins/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Thu, 01 Oct 2026 12:38:43 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Tools]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[distributed teams]]></category>
		<category><![CDATA[retrospective]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8854</guid>

					<description><![CDATA[A retrospectives plugin for Jira will add to Jira the Scrum retrospectives features that the Jira does not provide natively. This is especially important for distributed Agile teams. Even if it is used by many Agile teams, Jira has no retrospectives features. Jira is primarily built for issue tracking, task management and workflow automation. Its core functionality revolves around managing work items (e.g., bugs, user stories, tasks) rather than facilitating team processes like retrospectives. While Jira supports Scrum and Kanban, it doesn&#8217;t enforce or include Agile ceremonies like retrospectives. The Atlassian plugin ecosystem allows plugins to enhance the core Jira features. You can find plugins that specifically support Scrum retrospectives. Retrospective plugins for Jira are designed to help Agile teams run structured, engaging, and actionable sprint retrospectives without leaving the Jira environment. The most effective ones combine real-time collaboration, psychological safety features for discussion and voting and tight integration with Jira issue-tracking capabilities. The most important features that you should look for in Jira retrospectives plugins are: Predefined and custom retro templates: plugins should offer popular retrospective formats out of the box. Examples of these formats are Mad/Sad/Glad, Start/Stop/Continue, 4 L’s (Liked, Learned, Lacked, Longed for), and Speedboat. The Agile team should also be able to create fully custom boards. This flexibility ensures the retro format matches the team culture and goals. Anonymous and simultaneous participation: to encourage honest feedback and reduce groupthink. Plugins support anonymous submission and simultaneous (or asynchronous) input, so team members can add ideas independently before <a class="mh-excerpt-more" href="https://www.scrumexpert.com/tools/jira-retrospectives-plugins/" title="Jira Retrospectives Plugins">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/tools/jira-retrospectives-plugins/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Agile Job Seeker</title>
		<link>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/</link>
					<comments>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/#respond</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 21 Sep 2026 15:14:04 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[feature2]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8845</guid>

					<description><![CDATA[How do you approach a job search with an Agile mind? In this article Mark Haynes discusses how to plan your quest for a new job using the Scrum framework and concepts like sprints or user stories.. Author: Mark Haynes, https://www.linkedin.com/in/donald-mark-haynes-csm-745a609/ Think small and incrementally. Keep the big picture in mind, but focus on tasks you can accomplish in a few hours a day. Concentrate on one doable task at a time. Give yourself small assignments, then work them to completion, and move on to the next. Don’t obsess over things that will take months, or anything you have already accomplished. If you need to revisit it, then do that as a separate task. The job search, skill assessment, and skill development are all interrelated. Don’t get trapped rationalizing that you need more experience before you apply. Ask: How do I get experience? This is an excellent time to conduct a skills assessment and create a career development plan. Create a list of targeted skills. Think tools, techniques, and experience. Look for opportunities to pursue them. Constantly changing goals will lead to a spiral of self-doubt and indecision as you hit roadblocks. Pick a path. If you choose multiple paths, then work on them separately. Where do you start? It doesn’t matter. What matters is that you start now. There are jobs available, even in a bad economy. When is it a good time to look for a job? Always. You need market data. It gives a perspective on what <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/the-agile-job-seeker/" title="The Agile Job Seeker">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/the-agile-job-seeker/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>1</slash:comments>
		
		
			</item>
		<item>
		<title>Tips on How to Find a Good Agile Coach</title>
		<link>https://www.scrumexpert.com/resources/tips-on-how-to-find-a-good-agile-coach/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 03 Jul 2026 16:19:40 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Resources]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[coaching Agile]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8794</guid>

					<description><![CDATA[The notion of coaching is specific to Agile approaches in the software development world. There has always been consultants, but they were seen as a different role. Here are some resources about Agile coaching, starting with some quotes from the Agile Coaching book written by Rachel Davies and Liz Sedley. &#8220;Agile is all about teams working together to produce great software. As an Agile coach, you can help your team go from first steps to running with Agile to unleashing their full Agile potential.&#8221; &#8220;The art of Agile coaching is understanding the situation, the values underlying Agile software development, and how the two can combine. As an Agile coach, you don’t need to have all the answers; it takes time and a few experiments to hit on the right approach. We’ve worked with teams who’ve come up with great solutions, and we learn from every team we work with.&#8221; &#8220;Don’t expect to get recognition for your work as an Agile coach. It’s a supporting role rather than one that delivers direct benefits. A good coach gives credit to the team. When you work on an idea with Frank, it’s Frank’s idea if it succeeds, and if it doesn’t, then commiserate together.&#8221; Source: “Agile Coaching”, Rachel Davies and Liz Sedley, Pragmatic Bookshelf, 250 pages Some good points to keep in mind the next time you will be looking for some coaching help to transition to Agile. Resources about Agile Coaching Agile Coaching Tips When you are engaged as an agile coach, <a class="mh-excerpt-more" href="https://www.scrumexpert.com/resources/tips-on-how-to-find-a-good-agile-coach/" title="Tips on How to Find a Good Agile Coach">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Open Source Planning Poker Tools</title>
		<link>https://www.scrumexpert.com/tools/open-source-planning-poker-tools/</link>
					<comments>https://www.scrumexpert.com/tools/open-source-planning-poker-tools/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 27 May 2026 10:00:29 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Tools]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[planning poker]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6030</guid>

					<description><![CDATA[The first thing to say is that the term “Planning Poker®” is a registered trademark of Mountain Goat Software, the Mike Cohn company. This is why this agile planning practice could be sometimes names differently: scrum poker, agile poker, etc. This article presents a list of free and open source planning poker tools and plugins that are also directly available as online tools. Planning poker is originally a card game used by Scrum teams to estimate effort or relative size of user stories or features when during sprint planning. Team members estimates by playing numbered cards face-down to the table. Then the cards are revealed and the estimates are discussed. Discussion is the main interest of playing planning poker, because some developers will share why they vote differently from the consensus. This can be done with paper cards if the team is collocated, but in the case of a distributed Scrum team, you need to use a software to do it. Using a tool also makes it easier to record and remind previous planning estimations. There are many open source implementations of the Agile planning poker practice. I have decided to present only those who have also an online website or that are built as a plugin for another application like Slack, Jira, Trello, Discord or the Azure Boards. If a good tool is missing from this list, do not hesitate to contact us, and we will add it in a future update. Updates May 27 2026 Added: Card Estimator <a class="mh-excerpt-more" href="https://www.scrumexpert.com/tools/open-source-planning-poker-tools/" title="Open Source Planning Poker Tools">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/tools/open-source-planning-poker-tools/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
