<?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: Following the Pareto principle (aka the 80/20 rule)</title>
	<atom:link href="http://www.jasonplant.co.uk/2009/08/following-the-pareto-principle-aka-the-8020-rule/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jasonplant.co.uk/2009/08/following-the-pareto-principle-aka-the-8020-rule/</link>
	<description>A law blog written by someone from IT or an IT blog written by someone who works for a law firm</description>
	<lastBuildDate>Wed, 18 Jan 2012 13:34:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Jason</title>
		<link>http://www.jasonplant.co.uk/2009/08/following-the-pareto-principle-aka-the-8020-rule/comment-page-1/#comment-2395</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 19 Aug 2009 16:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasonplant.co.uk/?p=330#comment-2395</guid>
		<description>Now I&#039;m not sure if your first sentence is in jest? There certainly are software companies that release clearly before they&#039;ve finished any testing! It&#039;s one thing releasing once your key requirements are done, but never release something that clearly doesn&#039;t fulfil any.

The overall driver though should be get a working version with the key requirements in front of the people who will use it as soon as possible. That way you can get feedback quickly and review the requirements, focussing on the important and discarding the unimportant.</description>
		<content:encoded><![CDATA[<p>Now I&#8217;m not sure if your first sentence is in jest? There certainly are software companies that release clearly before they&#8217;ve finished any testing! It&#8217;s one thing releasing once your key requirements are done, but never release something that clearly doesn&#8217;t fulfil any.</p>
<p>The overall driver though should be get a working version with the key requirements in front of the people who will use it as soon as possible. That way you can get feedback quickly and review the requirements, focussing on the important and discarding the unimportant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peninsulawyer</title>
		<link>http://www.jasonplant.co.uk/2009/08/following-the-pareto-principle-aka-the-8020-rule/comment-page-1/#comment-2387</link>
		<dc:creator>Peninsulawyer</dc:creator>
		<pubDate>Wed, 19 Aug 2009 10:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasonplant.co.uk/?p=330#comment-2387</guid>
		<description>I&#039;m sure I have come across software where they have been following this the other way around (i.e. wait until it is 20% right and then launch!)

I have seen this principle quoted the other way around in relation to clients of professional services businesses as well - that it is likely that 20% of your clients generate 80% of your profit. This doesn&#039;t work for all businesses (not even all law firms), but if it does apply it can be useful to bear in mind when decided where to focus your time and resources.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure I have come across software where they have been following this the other way around (i.e. wait until it is 20% right and then launch!)</p>
<p>I have seen this principle quoted the other way around in relation to clients of professional services businesses as well &#8211; that it is likely that 20% of your clients generate 80% of your profit. This doesn&#8217;t work for all businesses (not even all law firms), but if it does apply it can be useful to bear in mind when decided where to focus your time and resources.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

