<?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>prioritization | Project Management for Software Development</title>
	<atom:link href="https://www.projectmanagementplanet.com/tag/prioritization/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.projectmanagementplanet.com</link>
	<description>Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban</description>
	<lastBuildDate>Mon, 24 Oct 2022 15:37:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Four Project Feature Prioritization Systems in Four Minutes</title>
		<link>https://www.projectmanagementplanet.com/four-project-feature-prioritization-systems-in-four-minutes/</link>
		
		<dc:creator><![CDATA[Project Management Planet]]></dc:creator>
		<pubDate>Mon, 24 Oct 2022 15:33:44 +0000</pubDate>
				<category><![CDATA[Videos]]></category>
		<category><![CDATA[prioritization]]></category>
		<guid isPermaLink="false">https://www.projectmanagementplanet.com/?p=2562</guid>

					<description><![CDATA[<p>Small software development projects are easy to manage. GitHub issues or Basecamp todos are more than enough to keep things going. Adding a feature or refactoring a small software development project is also easy, because there aren’t too many moving parts to consider. Large and especially long-living software development projects&#46;&#46;&#46;</p>
The post <a href="https://www.projectmanagementplanet.com/four-project-feature-prioritization-systems-in-four-minutes/">Four Project Feature Prioritization Systems in Four Minutes</a> first appeared on <a href="https://www.projectmanagementplanet.com">Project Management for Software Development</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Who Should I Listen To? Prioritizing Organizational Stakeholders</title>
		<link>https://www.projectmanagementplanet.com/who-should-i-listen-to-prioritizing-organizational-stakeholders/</link>
					<comments>https://www.projectmanagementplanet.com/who-should-i-listen-to-prioritizing-organizational-stakeholders/#comments</comments>
		
		<dc:creator><![CDATA[Project Management Planet]]></dc:creator>
		<pubDate>Mon, 30 Oct 2017 08:58:28 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[prioritization]]></category>
		<category><![CDATA[stakeholders]]></category>
		<guid isPermaLink="false">http://www.projectmanagementplanet.com/?p=1292</guid>

					<description><![CDATA[<p>Stakeholders are individuals or organizations who stand to gain or lose from the success or failure of a software development project. This article focuses is on the prioritization of stakeholders within the organization to create the good requirements for a successful project. It presents a process for dealing with internal&#46;&#46;&#46;</p>
The post <a href="https://www.projectmanagementplanet.com/who-should-i-listen-to-prioritizing-organizational-stakeholders/">Who Should I Listen To? Prioritizing Organizational Stakeholders</a> first appeared on <a href="https://www.projectmanagementplanet.com">Project Management for Software Development</a>.]]></description>
		
					<wfw:commentRss>https://www.projectmanagementplanet.com/who-should-i-listen-to-prioritizing-organizational-stakeholders/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
