Altova Mailing List Archives


Re: [xml-dev] The myth of 80/20

From: Robert Koberg <rob@------.--->
To: Eric van der Vlist <vdv@--------.--->
Date: 3/4/2004 4:46:00 PM
Eric van der Vlist wrote:

> On Thu, 2004-03-04 at 17:23, Bullard, Claude L (Len) wrote:
> 
>>It's easy to conceive of why 80/20 dominates given 
>>incomplete or ambiguous requirements and such.  Just 
>>remember that the alternative is to do all the work 
>>under one root, and in our world, that means a framework 
>>capable of subsuming all of the objects needed to 
>>paint that screen and keep updating it from data stores.
> 
> 
> That's not really what I meant. 
> 
> 80/20 is fine except that we usually have no measurement to evaluate on
> which side of the 80/20 frontier a feature is 


sure we do. it is called money

-Francisco D'Anconia

:)

and 80/20 becomes just an
> easy way to reject features we don't like.
> 
> Digression: for programmers an alternative to 80/20 is XP (extreme
> programming). Unfortunately that doesn't seem easy to adapt for
> specification authors.
> 
> Eric

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.