<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><!-- generator="wordpress/2.3.3" --><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Product Management Insights</title>
	<link>http://www.accompa.com/product-management-blog</link>
	<description>A blog: Practical insights into technology &amp; software Product Management, with special focus on building more successful products by managing requirements in a better way.</description>
	<pubDate>Thu, 15 Oct 2009 12:01:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/PracticalProductManagement" type="application/rss+xml" /><feedburner:emailServiceId>PracticalProductManagement</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Personas are Great - For Wasting Time!</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/AmmwM_jAgbg/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/10/15/personas-are-great-for-wasting-time/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 11:53:43 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<category><![CDATA[Requirements Management Basics]]></category>

		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/10/15/personas-are-great-for-wasting-time/</guid>
		<description>I’ve been meaning to write this post for a while. Recently, I saw a couple of blog posts on this topic (here and here) from bloggers I respect a lot. This spurred me to finally get around to writing this post.
This post is about using “personas” as a part of software requirements process. It’s not [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/AmmwM_jAgbg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/10/15/personas-are-great-for-wasting-time/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/10/15/personas-are-great-for-wasting-time/</feedburner:origLink></item>
		<item>
		<title>Use Case Template - Example (Requirements Management Basics)</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/ketijNE6oZk/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/10/08/use-case-template-example-requirements-management-basics/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 23:26:09 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Requirements Management Basics]]></category>

		<category><![CDATA[Use Cases]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/10/08/use-case-template-example-requirements-management-basics/</guid>
		<description>In a recent post, I provided a definition of use case as well as an example.
The example I provided uses a very simple format. In most real-world projects, teams find it helpful to use a more fully-dressed format.
  
In this post, I share a template of a fully-dressed format, as well as an example [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/ketijNE6oZk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/10/08/use-case-template-example-requirements-management-basics/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/10/08/use-case-template-example-requirements-management-basics/</feedburner:origLink></item>
		<item>
		<title>Death of Product Management at SaaS Companies…</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/pFXN9v-JqDA/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/23/death-of-product-management-at-saas-companies/#comments</comments>
		<pubDate>Thu, 24 Sep 2009 05:06:48 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[General]]></category>

		<category><![CDATA[Product Management]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/23/death-of-product-management-at-saas-companies/</guid>
		<description>Last night I got an email from a company with the subject &amp;#8220;Saas and the death of software product management&amp;#8220;.
And&amp;#8230; with the subtitle of &amp;#8220;Or, While You Weren&amp;#8217;t Looking, Your Product Manager&amp;#8217;s Job Became a Zombie&amp;#8221;.
The email said the following:
The growth of the SaaS business model spells the end of product management as it&amp;#8217;s been [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/pFXN9v-JqDA" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/23/death-of-product-management-at-saas-companies/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/23/death-of-product-management-at-saas-companies/</feedburner:origLink></item>
		<item>
		<title>Use Cases - Top-10 Reasons for Using Them to Document Your Requirements</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/Sw36i9dDn5o/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/22/use-cases-top-10-reasons-for-using-them-to-document-your-requirements/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 21:52:21 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Requirements Management Basics]]></category>

		<category><![CDATA[Use Cases]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/22/use-cases-top-10-reasons-for-using-them-to-document-your-requirements/</guid>
		<description>In my previous post, I provided a definition of Use Case along with an example. I also took a strong stance against considering UML diagrams as use cases.
Matt Klein made a good observation on Twitter today on how use cases are often not used well when documenting requirements:
Use Cases are important and very often not [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/Sw36i9dDn5o" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/22/use-cases-top-10-reasons-for-using-them-to-document-your-requirements/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/22/use-cases-top-10-reasons-for-using-them-to-document-your-requirements/</feedburner:origLink></item>
		<item>
		<title>Use Cases - Definition (Requirements Management Basics)</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/YjHrMJdFqrg/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/19/use-cases-definition-requirements-management-basics/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 04:48:57 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Requirements Management Basics]]></category>

		<category><![CDATA[Use Cases]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/19/use-cases-definition-requirements-management-basics/</guid>
		<description>A question that frequently comes up in my conversations nowadays is:
What exactly is a Use Case?
Let me try and explain it in this short blog post.
Similar Posts:

Use Case Template - Example (Requirements Management Basics) (1 comments)
Use Cases - Top-10 Reasons for Using Them to Document Your Requirements (5 comments)
Personas are Great - For Wasting Time! [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/YjHrMJdFqrg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/19/use-cases-definition-requirements-management-basics/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/19/use-cases-definition-requirements-management-basics/</feedburner:origLink></item>
		<item>
		<title>Why I Switched From Tweetdeck to Seesmic - And the Lessons for Product Managers</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/mgkiiy_jsqY/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/15/why-i-switched-from-tweetdeck-to-seesmic-and-the-lessons-for-product-managers/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 05:54:27 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/15/why-i-switched-from-tweetdeck-to-seesmic-and-the-lessons-for-product-managers/</guid>
		<description>An hour ago, I did something without much conscious thought at all. I uninstalled the Twitter client I used to like (Tweetdeck), and installed a new one (Seesmic). And there I went, merrily tweeting.
Then, I caught myself and started thinking why I did that. The more I thought, the more I realized that there are [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/mgkiiy_jsqY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/15/why-i-switched-from-tweetdeck-to-seesmic-and-the-lessons-for-product-managers/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/15/why-i-switched-from-tweetdeck-to-seesmic-and-the-lessons-for-product-managers/</feedburner:origLink></item>
		<item>
		<title>Product Management - SaaS vs Traditional Software</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/uVyHU-w9Q4Y/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/09/product-management-saas-vs-traditional-software/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 17:18:21 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/09/product-management-saas-vs-traditional-software/</guid>
		<description>Mark Kromer at TechProdo blog recently wrote a nice blog post titled SaaS Product Management: Is there a difference?
In his post Mark poses the interesting question (applicable to a lot of product managers):
I was wondering what differences I would find in my role as a product manager if the products that I was managing moved [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/uVyHU-w9Q4Y" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/09/product-management-saas-vs-traditional-software/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/09/product-management-saas-vs-traditional-software/</feedburner:origLink></item>
		<item>
		<title>Product Management Blogs - Top-10</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/_hBKa2hbsUU/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/09/01/product-management-blogs-top-10/#comments</comments>
		<pubDate>Wed, 02 Sep 2009 05:55:26 +0000</pubDate>
		<dc:creator>accompa</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/09/01/product-management-blogs-top-10/</guid>
		<description>Here&amp;#8217;s our definitive list of the top-10 blogs on Product Management. We&amp;#8217;ve found that all of these blogs consistently produce posts that are useful to product management professionals.
P.S. In case you&amp;#8217;re wondering, we arrived at this list using a proprietary, patent-pending, 100% scientific formula. Hence it is infallible and is THE definitive list. Okay?  [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/_hBKa2hbsUU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/09/01/product-management-blogs-top-10/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/09/01/product-management-blogs-top-10/</feedburner:origLink></item>
		<item>
		<title>Product Management vs. Product Marketing - 2 Departments or 1?</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/RB6SuQKoxxQ/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/08/25/product-management-vs-product-marketing-2-departments-or-1/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 17:59:09 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<category><![CDATA[Product Marketing]]></category>

		<category><![CDATA[product management vs product marketing]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/08/25/product-management-vs-product-marketing-2-departments-or-1/</guid>
		<description>Today, at the vast majority of software companies that have 500 or more employees, there are two separate but closely related departments: &amp;#8220;Product Management&amp;#8221; and &amp;#8220;Product Marketing&amp;#8220;.
I believe this is a fundamentally flawed setup for today&amp;#8217;s fast-changing markets - a setup that leads to confusion over roles, lack of ownership, unnecessary politics &amp;#38; poor morale [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/RB6SuQKoxxQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/08/25/product-management-vs-product-marketing-2-departments-or-1/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/08/25/product-management-vs-product-marketing-2-departments-or-1/</feedburner:origLink></item>
		<item>
		<title>User-Friendly Error Messages - A Good Example</title>
		<link>http://feedproxy.google.com/~r/PracticalProductManagement/~3/cWmbJNEBlfY/</link>
		<comments>http://www.accompa.com/product-management-blog/2009/08/21/user-friendly-error-messages-a-good-example/#comments</comments>
		<pubDate>Fri, 21 Aug 2009 20:22:13 +0000</pubDate>
		<dc:creator>Michael Shrivathsan</dc:creator>
		
		<category><![CDATA[Product Management]]></category>

		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.accompa.com/product-management-blog/2009/08/21/user-friendly-error-messages-a-good-example/</guid>
		<description>One of my pet peeves with most software is the cryptic, unfriendly error messages thrown up by so many of them.
At Accompa, we try to make error messages in our own software as friendly and useful as possible. I think we still have a long way to go, but we work hard at it.
I just [...]&lt;img src="http://feeds.feedburner.com/~r/PracticalProductManagement/~4/cWmbJNEBlfY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.accompa.com/product-management-blog/2009/08/21/user-friendly-error-messages-a-good-example/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.accompa.com/product-management-blog/2009/08/21/user-friendly-error-messages-a-good-example/</feedburner:origLink></item>
	</channel>
</rss>
