I know there is probably an actual definition of the 80/20 rule somewhere, but here's my interpretation, which I think gels with the article. 80% of the work is done quickly , which is the absolute core stuff, with 0 polish and full of edge-case data and interface bugs. Then the last 20% of the work takes roughly equal to the first 80%. The percentages have nothing to do with actual work completed or time spent, rather how complete it looks to the client/your boss/someone with no details of the technical implementation.
And that's only to get to 1.0. Some of these features would be unnecessary for launch but should be added post-launch, e.g., the editor imo.
EDIT: Looking it up there is an 80-20 rule that I think is in a similar vein but if applied properly to this situation would say that 80% of the work exists in 20% of the features.
And that's only to get to 1.0. Some of these features would be unnecessary for launch but should be added post-launch, e.g., the editor imo.
EDIT: Looking it up there is an 80-20 rule that I think is in a similar vein but if applied properly to this situation would say that 80% of the work exists in 20% of the features.
Which may even be true sometimes.