<?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"
	>
<channel>
	<title>Comments on: Key Distinction: Practice vs. Project Leadership</title>
	<atom:link href="http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Fri, 21 Nov 2008 13:55:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: rolywalter</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5662</link>
		<dc:creator>rolywalter</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5662</guid>
		<description>&lt;p&gt;Thanks for another great article. I've always had a niggling desire to keep myself (as a person) &#038; my name as part of my business brand, since I know that the trust I have earnt is almost entirely due to people trusting me as a human, rather than my (rather awkward) sales pitch or my product set etc. Even thought I may change the name of my business, this 'practice' model will help me keep the personal, professional touch, rather than just being one of the consultants at x with skillset y.  The only problem is, this seems to go against the idea of working 'on' your business rather than 'for' it, which means you couldn't look to sell it easily in the future. Michael Gerber may not approve of this one!&lt;/p&gt;

&lt;p&gt;Anyone else have any thoughts?&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Thanks for another great article. I&#8217;ve always had a niggling desire to keep myself (as a person) &#038; my name as part of my business brand, since I know that the trust I have earnt is almost entirely due to people trusting me as a human, rather than my (rather awkward) sales pitch or my product set etc. Even thought I may change the name of my business, this &#8216;practice&#8217; model will help me keep the personal, professional touch, rather than just being one of the consultants at x with skillset y.  The only problem is, this seems to go against the idea of working &#8216;on&#8217; your business rather than &#8216;for&#8217; it, which means you couldn&#8217;t look to sell it easily in the future. Michael Gerber may not approve of this one!</p>
<p>Anyone else have any thoughts?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: RockyShark</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5663</link>
		<dc:creator>RockyShark</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5663</guid>
		<description>&lt;p&gt;Andrew says: "...they tend to rely on strict clinical protocols and guidelines"&lt;/p&gt;

&lt;p&gt;I think that's an important statement when you talk about working on your business rather than in it. If you have good procedures and processes, you can replicate that, get staff to do it, and concentrate on growing your business.&lt;/p&gt;

&lt;p&gt;That's my theory, anyway. Still trying to put it into practise!!!&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Andrew says: &#8220;&#8230;they tend to rely on strict clinical protocols and guidelines&#8221;</p>
<p>I think that&#8217;s an important statement when you talk about working on your business rather than in it. If you have good procedures and processes, you can replicate that, get staff to do it, and concentrate on growing your business.</p>
<p>That&#8217;s my theory, anyway. Still trying to put it into practise!!!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: aneitlich</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5664</link>
		<dc:creator>aneitlich</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5664</guid>
		<description>&lt;p&gt;To Roly's comment:&lt;/p&gt;

&lt;p&gt;IBM, Accenture, Deloitte, McKinsey, CapGemini and many other firms have become huge, and all have the "practice" model. So having a professional practice and working on instead of in your business go together fine.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>To Roly&#8217;s comment:</p>
<p>IBM, Accenture, Deloitte, McKinsey, CapGemini and many other firms have become huge, and all have the &#8220;practice&#8221; model. So having a professional practice and working on instead of in your business go together fine.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dimensionmedia</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5665</link>
		<dc:creator>dimensionmedia</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5665</guid>
		<description>&lt;p&gt;Putting your name to a business can backfire on you - even if you truly are honest and hardworking. You could rightly refuse to do something for a client (such as doing ALOT of work that your contract didn't cover) and the client can talk bad behind your back. If your name = company name, this could screw you even more. At least with a corporate name (like mine, Dimension Media) you can give the illusion that if people overhear anything and about you, you can allude that problem people at your company are let go (it's not always right to talk bad about the ex-client that is badmouthing you, for several reasons.) With a corporate name, you can give the illusion that your company is bigger than you - which is important to some clients. That's my $0.02 anyway. :-)&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Putting your name to a business can backfire on you - even if you truly are honest and hardworking. You could rightly refuse to do something for a client (such as doing ALOT of work that your contract didn&#8217;t cover) and the client can talk bad behind your back. If your name = company name, this could screw you even more. At least with a corporate name (like mine, Dimension Media) you can give the illusion that if people overhear anything and about you, you can allude that problem people at your company are let go (it&#8217;s not always right to talk bad about the ex-client that is badmouthing you, for several reasons.) With a corporate name, you can give the illusion that your company is bigger than you - which is important to some clients. That&#8217;s my $0.02 anyway. :-)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lastcraft</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5666</link>
		<dc:creator>lastcraft</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5666</guid>
		<description>&lt;p&gt;Hi.&lt;/p&gt;

&lt;p&gt;It was kind of implied in your article that there were four factors to balance: scope, quality, time, resources. In practice I find that although time is uually given as an absolute by a client, it is often the one that turns out most flexible. When they say they want X in three weeks it usually means that they want one feature of X in particular. By prioritising your work queue you can more favourably balance scope with time (although you should leave high risk unknown portions until last). The Scrum methodology is built around this.&lt;/p&gt;

&lt;p&gt;yours, Marcus&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>It was kind of implied in your article that there were four factors to balance: scope, quality, time, resources. In practice I find that although time is uually given as an absolute by a client, it is often the one that turns out most flexible. When they say they want X in three weeks it usually means that they want one feature of X in particular. By prioritising your work queue you can more favourably balance scope with time (although you should leave high risk unknown portions until last). The Scrum methodology is built around this.</p>
<p>yours, Marcus</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lastcraft</title>
		<link>http://www.sitepoint.com/blogs/2004/05/25/key-distinction-practice-vs-project-leadership/#comment-5667</link>
		<dc:creator>lastcraft</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">1159959437#comment-5667</guid>
		<description>&lt;p&gt;Correction! That should have been...&lt;/p&gt;

&lt;p&gt;(although you should NOT leave high risk unknown portions until last)&lt;/p&gt;

&lt;p&gt;yours, Marcus&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Correction! That should have been&#8230;</p>
<p>(although you should NOT leave high risk unknown portions until last)</p>
<p>yours, Marcus</p>]]></content:encoded>
	</item>
</channel>
</rss>
