<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Specializing Generalists and the Politics of Agile</title>
	<atom:link href="http://tynerblain.com/blog/2008/02/14/specializing-generalists/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2008/02/14/specializing-generalists/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/02/14/specializing-generalists/comment-page-1/#comment-307637</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sun, 17 Feb 2008 04:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2008/02/14/specializing-generalists/#comment-307637</guid>
		<description>Hey guys, thanks for commenting, and for being active participants here for so long!  Personally, it makes the place feel like home, for lack of a better description.

I hope I didn&#039;t dilute the message, Barb - I agree with you that the bigger problem is in companies forcing product managers to stretch too thin.  I think I am vamping on one of the coloring arguments that keeps these issue from being black and white.  Chalk it up to me trying to be &quot;nuanced.&quot;

And Roger - you&#039;re spot on in your article.  As part of a teams trying to drive home the value of user experience &lt;i&gt;expertise&lt;/i&gt;, I&#039;ve seen the angst that the truly gifted designers feel when people assume that the job can be done without the skills.  It&#039;s a lot like writing - everyone can write, but not everyone can be an author.

Thanks again!
Scott</description>
		<content:encoded><![CDATA[<p>Hey guys, thanks for commenting, and for being active participants here for so long!  Personally, it makes the place feel like home, for lack of a better description.</p>
<p>I hope I didn&#8217;t dilute the message, Barb &#8211; I agree with you that the bigger problem is in companies forcing product managers to stretch too thin.  I think I am vamping on one of the coloring arguments that keeps these issue from being black and white.  Chalk it up to me trying to be &#8220;nuanced.&#8221;</p>
<p>And Roger &#8211; you&#8217;re spot on in your article.  As part of a teams trying to drive home the value of user experience <i>expertise</i>, I&#8217;ve seen the angst that the truly gifted designers feel when people assume that the job can be done without the skills.  It&#8217;s a lot like writing &#8211; everyone can write, but not everyone can be an author.</p>
<p>Thanks again!<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barbara Nelson</title>
		<link>http://tynerblain.com/blog/2008/02/14/specializing-generalists/comment-page-1/#comment-305043</link>
		<dc:creator>Barbara Nelson</dc:creator>
		<pubDate>Fri, 15 Feb 2008 16:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2008/02/14/specializing-generalists/#comment-305043</guid>
		<description>Scott,
As usual, great post. 

I &quot;almost agree&quot; with you, too. In a world where you have superheroes, they can do anything. In my 20+ years of experience in the technology arena, I have seen great teams build great stuff, regardless of methodology, regardless of roles being clearly defined. Waterfall, agile, whatever. Great teams have a special chemistry. Superheroes just get stuff done. Brilliantly. And when they solve problems people actually want to pay someone to solve, there is no stopping them. With or without formal product management. (Did I say that?)

The &quot;specializing generalist&quot; concept has merit, particularly for the developers. But in the role of product management where there are a whole bunch of other things to be done that are beyond the development process, it isn&#039;t practical. If the team is 2 guys in a garage, that&#039;s a different story. Or a 20-person start-up. With superheroes on the team.

But those teams and those people aren&#039;t the ones we&#039;re talking about. Superheroes don&#039;t need special methodologies. Being pragmatic, we are looking for repeatable. We are looking for ways to help regular people. We are looking for ways to grow our businesses. My gut tells me that only 5% fit the archetypes you describe. They are born that way. The other 95% might not be brilliant, but they can be successful with focus. Someone on the team keeping the vision of what needs to be built, for whom, where we can all make money. (In a start-up, this is usually a founder, not the product manager.)

I frequently see product managers filling some of the other development roles. BUT, if they are deep into the development process of designing, testing, developing rather than in the market gaining the deep understanding of the market, they will fall back on opinions rather than facts to make decisions. I&#039;m OK with that as long as SOMEONE&#039;s job is market expert. Market expertise does not come from sitting in development.

Happy Friday!</description>
		<content:encoded><![CDATA[<p>Scott,<br />
As usual, great post. </p>
<p>I &#8220;almost agree&#8221; with you, too. In a world where you have superheroes, they can do anything. In my 20+ years of experience in the technology arena, I have seen great teams build great stuff, regardless of methodology, regardless of roles being clearly defined. Waterfall, agile, whatever. Great teams have a special chemistry. Superheroes just get stuff done. Brilliantly. And when they solve problems people actually want to pay someone to solve, there is no stopping them. With or without formal product management. (Did I say that?)</p>
<p>The &#8220;specializing generalist&#8221; concept has merit, particularly for the developers. But in the role of product management where there are a whole bunch of other things to be done that are beyond the development process, it isn&#8217;t practical. If the team is 2 guys in a garage, that&#8217;s a different story. Or a 20-person start-up. With superheroes on the team.</p>
<p>But those teams and those people aren&#8217;t the ones we&#8217;re talking about. Superheroes don&#8217;t need special methodologies. Being pragmatic, we are looking for repeatable. We are looking for ways to help regular people. We are looking for ways to grow our businesses. My gut tells me that only 5% fit the archetypes you describe. They are born that way. The other 95% might not be brilliant, but they can be successful with focus. Someone on the team keeping the vision of what needs to be built, for whom, where we can all make money. (In a start-up, this is usually a founder, not the product manager.)</p>
<p>I frequently see product managers filling some of the other development roles. BUT, if they are deep into the development process of designing, testing, developing rather than in the market gaining the deep understanding of the market, they will fall back on opinions rather than facts to make decisions. I&#8217;m OK with that as long as SOMEONE&#8217;s job is market expert. Market expertise does not come from sitting in development.</p>
<p>Happy Friday!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://tynerblain.com/blog/2008/02/14/specializing-generalists/comment-page-1/#comment-304732</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Fri, 15 Feb 2008 12:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2008/02/14/specializing-generalists/#comment-304732</guid>
		<description>The way &lt;a href=&quot;http://cauvin.blogspot.com/2008/02/interaction-design-neglected-skill.html&quot; rel=&quot;nofollow&quot;&gt;I put it in my most recent blog entry&lt;/a&gt; is:

&quot;And in a healthy, productive organization, some people are flexible and play multiple roles.&quot;

Nonetheless, the problem in most organizations is that there is little awareness of the skills necessary to play some of the roles.  For example:

&quot;Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don&#039;t even realize how unqualified they are.&quot;</description>
		<content:encoded><![CDATA[<p>The way <a href="http://cauvin.blogspot.com/2008/02/interaction-design-neglected-skill.html" rel="nofollow">I put it in my most recent blog entry</a> is:</p>
<p>&#8220;And in a healthy, productive organization, some people are flexible and play multiple roles.&#8221;</p>
<p>Nonetheless, the problem in most organizations is that there is little awareness of the skills necessary to play some of the roles.  For example:</p>
<p>&#8220;Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don&#8217;t even realize how unqualified they are.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Politics &#187; Specializing Generalists and the Politics of Agile</title>
		<link>http://tynerblain.com/blog/2008/02/14/specializing-generalists/comment-page-1/#comment-304089</link>
		<dc:creator>Politics &#187; Specializing Generalists and the Politics of Agile</dc:creator>
		<pubDate>Fri, 15 Feb 2008 02:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2008/02/14/specializing-generalists/#comment-304089</guid>
		<description>[...] Glen oglaza wrote an interesting post today onHere&#8217;s a quick excerpt [...]</description>
		<content:encoded><![CDATA[<p>[...] Glen oglaza wrote an interesting post today onHere&#8217;s a quick excerpt [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

