<?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: Specialists bring special problems</title>
	<atom:link href="http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Sat, 11 Feb 2012 15:16:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arie Kahn</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-11</link>
		<dc:creator>Arie Kahn</dc:creator>
		<pubDate>Wed, 31 Dec 2003 02:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-11</guid>
		<description>Regards large projects and a generalist as a head, your
explanation is basically not opposites mine. What I mean,
is that a project manager must be technically or potentially
capable to understand or work in all areas of project.

It just will take too much time, or it will take additional time
to achieve the same level of proficiency, as of each specialist.
So, this project manager feel competent and independent.
So, now, he/she can hire others to do the parts.

Such project manager can save a situation, when somebody
quits in the middle of development. He/she can&#039;t be fooled
by a specialist, who say that it does not possible.

Any other way to manage leads to &quot;administrative&quot; kind
of management. There is no one in the team, who
really knows how this damn thing works, and no one
who takes responsibility on the whole. I see such
model every day.
</description>
		<content:encoded><![CDATA[<p>Regards large projects and a generalist as a head, your<br />
explanation is basically not opposites mine. What I mean,<br />
is that a project manager must be technically or potentially<br />
capable to understand or work in all areas of project.</p>
<p>It just will take too much time, or it will take additional time<br />
to achieve the same level of proficiency, as of each specialist.<br />
So, this project manager feel competent and independent.<br />
So, now, he/she can hire others to do the parts.</p>
<p>Such project manager can save a situation, when somebody<br />
quits in the middle of development. He/she can&#8217;t be fooled<br />
by a specialist, who say that it does not possible.</p>
<p>Any other way to manage leads to &#8220;administrative&#8221; kind<br />
of management. There is no one in the team, who<br />
really knows how this damn thing works, and no one<br />
who takes responsibility on the whole. I see such<br />
model every day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udi Dahan - The Software Simplist</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-10</link>
		<dc:creator>Udi Dahan - The Software Simplist</dc:creator>
		<pubDate>Wed, 31 Dec 2003 02:30:34 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-10</guid>
		<description>Arie: in my post I refer to the problems that can occur in large projects when many specialists are involved, nay, run the project. My thesis is that you must have a generalist at the head of the project. This generalist doesn&#039;t have to have the same level of knowledge and skills as each specialist in their field, but must understand the importance of those skills to the specific parts of the project where they will be needed.</description>
		<content:encoded><![CDATA[<p>Arie: in my post I refer to the problems that can occur in large projects when many specialists are involved, nay, run the project. My thesis is that you must have a generalist at the head of the project. This generalist doesn&#8217;t have to have the same level of knowledge and skills as each specialist in their field, but must understand the importance of those skills to the specific parts of the project where they will be needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arie Kahn</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-9</link>
		<dc:creator>Arie Kahn</dc:creator>
		<pubDate>Wed, 31 Dec 2003 02:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-9</guid>
		<description>I understand what are talking about and this is
a really interesting question.

I think, my big principle here is as follows:

I can be a project manager, if and only if I potentially
can do ALL THE WORK MYSELF. In other words, I
have a full picture of the project and of every small part.
Now, for the sake of efficiency and cost effectiveness,
I can afford myself to buy a services of specialists.

I prefer one man studio and simpler project, than
5 people team and a complex project.

If not one man studio, then maximum 2. Both are
generalists.

Another strategy is to make things simple and modular,
to be ready for changes in the project. Just from the
start I think of how I will introduce dramatic changes
later, so on the code level, HTML for example, I make
everything as CMS approach, headers, footers, insertions.
I can rebuild and recompile, and change structure and
navigation of 50 pages website in less than 1 day.</description>
		<content:encoded><![CDATA[<p>I understand what are talking about and this is<br />
a really interesting question.</p>
<p>I think, my big principle here is as follows:</p>
<p>I can be a project manager, if and only if I potentially<br />
can do ALL THE WORK MYSELF. In other words, I<br />
have a full picture of the project and of every small part.<br />
Now, for the sake of efficiency and cost effectiveness,<br />
I can afford myself to buy a services of specialists.</p>
<p>I prefer one man studio and simpler project, than<br />
5 people team and a complex project.</p>
<p>If not one man studio, then maximum 2. Both are<br />
generalists.</p>
<p>Another strategy is to make things simple and modular,<br />
to be ready for changes in the project. Just from the<br />
start I think of how I will introduce dramatic changes<br />
later, so on the code level, HTML for example, I make<br />
everything as CMS approach, headers, footers, insertions.<br />
I can rebuild and recompile, and change structure and<br />
navigation of 50 pages website in less than 1 day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Udi Dahan</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-8</link>
		<dc:creator>Udi Dahan</dc:creator>
		<pubDate>Tue, 11 Nov 2003 02:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-8</guid>
		<description>I am proposing one expert generalist at a minimum per project.

On the issue of process, my problem is when the decision making process degrades into a multi-dimensional tug-of-war by parties that don&#039;t have enough information to make any decision, let alone the &quot;right&quot; one. ( sometimes there is only the not-so-bad decision out of many bad ones )

I am interested in changing the landscape so that the problem disappears - evaporating cloud anyone ? ( TOC )

I am exactly talking about the hiring, training, and retaining &quot;processes&quot; in a company. These are the processes that need to be changed, or evolved as I like to call it. Evolution implies gradual change which leads to overall improvement.

Process is not about distrust. Even though many managers put processes in place because they don&#039;t trust their teams. There is a reason why they don&#039;t trust their teams. They hire crappy teams. Of course, when building a team one should not hire 2 strongly willed people of opposing personalities, and place them in positions where they will vye for political advancement. Of course, it is never the manager&#039;s fault when this happens, even if he/she personally were involved in the hiring process.</description>
		<content:encoded><![CDATA[<p>I am proposing one expert generalist at a minimum per project.</p>
<p>On the issue of process, my problem is when the decision making process degrades into a multi-dimensional tug-of-war by parties that don&#8217;t have enough information to make any decision, let alone the &#8220;right&#8221; one. ( sometimes there is only the not-so-bad decision out of many bad ones )</p>
<p>I am interested in changing the landscape so that the problem disappears &#8211; evaporating cloud anyone ? ( TOC )</p>
<p>I am exactly talking about the hiring, training, and retaining &#8220;processes&#8221; in a company. These are the processes that need to be changed, or evolved as I like to call it. Evolution implies gradual change which leads to overall improvement.</p>
<p>Process is not about distrust. Even though many managers put processes in place because they don&#8217;t trust their teams. There is a reason why they don&#8217;t trust their teams. They hire crappy teams. Of course, when building a team one should not hire 2 strongly willed people of opposing personalities, and place them in positions where they will vye for political advancement. Of course, it is never the manager&#8217;s fault when this happens, even if he/she personally were involved in the hiring process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McCallister</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-7</link>
		<dc:creator>Brian McCallister</dc:creator>
		<pubDate>Mon, 10 Nov 2003 20:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-7</guid>
		<description>btw - thank you for starting to blog. Sadly, I do not remember where I found the link to your blog, but I would like to thank that gent as well. 

What you are saying rings very true and you have a knack for putting things clearly, it seems!</description>
		<content:encoded><![CDATA[<p>btw &#8211; thank you for starting to blog. Sadly, I do not remember where I found the link to your blog, but I would like to thank that gent as well. </p>
<p>What you are saying rings very true and you have a knack for putting things clearly, it seems!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McCallister</title>
		<link>http://www.udidahan.com/2003/11/09/specialists-bring-special-problems/comment-page-1/#comment-6</link>
		<dc:creator>Brian McCallister</dc:creator>
		<pubDate>Mon, 10 Nov 2003 20:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/7#comment-6</guid>
		<description>Specialists are cheaper than generalists. This is very important to keep in mind. A team of primarily generalists is a great thing, but finding expert generalists is very difficult, and getting them to work for you more so. Most generalists start out as specialists and then keep learning more until they realize the the same problems, and solutions, keep recurring in each domain. Then they start to see themselves as generalists and realize they can charge a lot more for their time.

Secondly, as you bring up process. Process is one of those nasty many-headed beasties. In general if you are dicussing process as it applies to yourself things are fine and healthy. When you start talking process as it applies to somebody else it typically means that you do not trust that somebody else to do his or her job correctly. This changes when not trusting people to do their jobs is an institutional virtue (CMM 5 type orgs). When a typical organization and team has management talking &quot;process&quot; though it usually means that management has no faith in that team. The long term solution is then to rethink how hiring, training, and retaining is done.</description>
		<content:encoded><![CDATA[<p>Specialists are cheaper than generalists. This is very important to keep in mind. A team of primarily generalists is a great thing, but finding expert generalists is very difficult, and getting them to work for you more so. Most generalists start out as specialists and then keep learning more until they realize the the same problems, and solutions, keep recurring in each domain. Then they start to see themselves as generalists and realize they can charge a lot more for their time.</p>
<p>Secondly, as you bring up process. Process is one of those nasty many-headed beasties. In general if you are dicussing process as it applies to yourself things are fine and healthy. When you start talking process as it applies to somebody else it typically means that you do not trust that somebody else to do his or her job correctly. This changes when not trusting people to do their jobs is an institutional virtue (CMM 5 type orgs). When a typical organization and team has management talking &#8220;process&#8221; though it usually means that management has no faith in that team. The long term solution is then to rethink how hiring, training, and retaining is done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

