<?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>Polarion Software Weblog &#187; Managers Corner</title>
	<atom:link href="http://blog.polarion.com/archives/category/managers-corner/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.polarion.com</link>
	<description>Tomorrow&#039;s ALM Platform Today</description>
	<lastBuildDate>Tue, 20 Jul 2010 10:29:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Management wants &#8220;ROI&#8221; numbers. Now what?</title>
		<link>http://blog.polarion.com/archives/863#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/863#comments</comments>
		<pubDate>Thu, 08 Jul 2010 10:33:16 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[investment]]></category>
		<category><![CDATA[Polarion ALM]]></category>
		<category><![CDATA[Polarion Requirements]]></category>
		<category><![CDATA[ROI]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=863</guid>
		<description><![CDATA[By Robert Neher You&#8217;ve done your homework and you know you&#8217;ve come across a great solution (namely Polarion ALM or Polarion Requirements!) that would be a major benefit to your organization. But management wants you to show them the &#8220;Return on Investment&#8221; (&#8220;ROI&#8221; in execu-speak). What? You manage development projects, you&#8217;re not a number juggler. [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/863/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Requirements Your Way (Part 5 of 5)</title>
		<link>http://blog.polarion.com/archives/516#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/516#comments</comments>
		<pubDate>Tue, 17 Nov 2009 09:37:46 +0000</pubDate>
		<dc:creator>Stefano Rizzo</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Tips, Tricks, How-To]]></category>
		<category><![CDATA[Polarion Requirements]]></category>
		<category><![CDATA[requirements management]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=516</guid>
		<description><![CDATA[In this last post of the series, I will give you an overview of some basic concepts that are part of our own Requirements Management process at Polarion Software. This is not a process, it is just a bunch of hints that should help those people and companies who have no process in place. Try [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/516/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Requirements your way (Part 4)</title>
		<link>http://blog.polarion.com/archives/500#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/500#comments</comments>
		<pubDate>Mon, 02 Nov 2009 11:41:05 +0000</pubDate>
		<dc:creator>Stefano Rizzo</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Polarion Requirements]]></category>
		<category><![CDATA[requirements management]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=500</guid>
		<description><![CDATA[While Agile methods are becoming more and more popular in Software Development shops, Requirements Management is a formal discipline widely adopted and adapted in System Engineering and in general inside those companies that have to comply with strict regulations and norms. The Formal Requirements Process The formal requirements process evolved first in industries such as [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/500/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Requirements your way (Part 3)</title>
		<link>http://blog.polarion.com/archives/479#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/479#comments</comments>
		<pubDate>Thu, 15 Oct 2009 13:57:03 +0000</pubDate>
		<dc:creator>Stefano Rizzo</dc:creator>
				<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Tips, Tricks, How-To]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[Polarion Requirements]]></category>
		<category><![CDATA[requirements management]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[XP]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=479</guid>
		<description><![CDATA[Several customers and friends reported to me that they would like to embrace Agile methodologies for their development team. Most of them are, however, concerned about how to Manage Requirements with such an approach. In this post I&#8217;m going to provide a few hints that could be beneficial to parallel Agile methods with some light-weight [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/479/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Requirements your way (Part 2)</title>
		<link>http://blog.polarion.com/archives/460#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/460#comments</comments>
		<pubDate>Tue, 29 Sep 2009 07:50:59 +0000</pubDate>
		<dc:creator>Stefano Rizzo</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Tips, Tricks, How-To]]></category>
		<category><![CDATA[manual process]]></category>
		<category><![CDATA[Polarion Requirements]]></category>
		<category><![CDATA[requirements management]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=460</guid>
		<description><![CDATA[In the previous post we defined the requirements lifecycle and we outlined its formats and capture methods. Let’s now take a look at a few of the ways organizations approach requirements management today. Depending on an organization’s needs, the requirements management process can range from the most simple and rudimentary, to extremely formalized. We’ll also [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/460/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Requirements your way (Part 1)</title>
		<link>http://blog.polarion.com/archives/425#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/425#comments</comments>
		<pubDate>Tue, 15 Sep 2009 10:03:28 +0000</pubDate>
		<dc:creator>Stefano Rizzo</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Tips, Tricks, How-To]]></category>
		<category><![CDATA[Polarion Requirements 2.0]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[requirements management]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=425</guid>
		<description><![CDATA[Intro In this Blog series I will try to reveal new ways to improve your requirements process – regardless of your starting point or requirements process. In this post I will define the requirements process and outline the various capture methods available today. In future posts we’ll look at the pros and cons of various [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/425/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Polarion goes Scrum (part 6)</title>
		<link>http://blog.polarion.com/archives/381#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/381#comments</comments>
		<pubDate>Mon, 24 Aug 2009 14:18:15 +0000</pubDate>
		<dc:creator>Nick Entin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[ALM]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[Polarion ALM]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[sprint]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=381</guid>
		<description><![CDATA[by Nick Entin Sprint Development During a sprint, the development team continuously integrates all changes, and updated versions of the product are installed on the internal servers daily to prove stability and allow earlier testing of new functionality by other people (testers, doc writers, etc.) The Polarion development process stipulates the following: An integration build [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/381/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Little-known Polarion Fact</title>
		<link>http://blog.polarion.com/archives/345#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/345#comments</comments>
		<pubDate>Mon, 17 Aug 2009 08:23:05 +0000</pubDate>
		<dc:creator>Michael Carey</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[CMMI]]></category>
		<category><![CDATA[Polarion ALM]]></category>
		<category><![CDATA[Polarion Requirements 2.0]]></category>
		<category><![CDATA[Polarion Software]]></category>
		<category><![CDATA[Polarion Track & Wiki]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=345</guid>
		<description><![CDATA[by Michael Carey Many people reading this post will have seen this image before: The Polarion Software logo, right? But do you know what it represents and why? Here&#8217;s a hint: You guessed it: Polarion&#8217;s logo represents the Aurora Borealis, commonly known as the northern lights. Not to disparage our friends &#8220;down under&#8221; who have [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/345/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Polarion goes Scrum (Part 5)</title>
		<link>http://blog.polarion.com/archives/307#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/307#comments</comments>
		<pubDate>Thu, 16 Jul 2009 11:07:02 +0000</pubDate>
		<dc:creator>Nick Entin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[iteration]]></category>
		<category><![CDATA[Polarion ALM]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=307</guid>
		<description><![CDATA[Sprint Meetings Meetings are possibly the most important assets of Scrum. As described in previous chapters, Scrum allows us to identify problems and help find ways resolve them. Meetings are the essential part when team commits to Product Owner on the amount of work (features) they will address over the sprint, they discuss the progress [...]]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/307/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Polarion goes Scrum (Part 4)</title>
		<link>http://blog.polarion.com/archives/239#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://blog.polarion.com/archives/239#comments</comments>
		<pubDate>Wed, 24 Jun 2009 07:32:10 +0000</pubDate>
		<dc:creator>Nick Entin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[Managers Corner]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[Polarion ALM]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://blog.polarion.com/?p=239</guid>
		<description><![CDATA[Polarion R&#038;D VP Nick Entin talks about backlogs as used in Polarion's Scrum process]]></description>
		<wfw:commentRss>http://blog.polarion.com/archives/239/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
