Agile Principle 8: Enough Is Enough!

This content is syndicated from by Kelly Waters. To view the original post in full, click here.

Pareto's law is more commonly known as the 80/20 rule. The theory is about the law of distribution and how many things have a similar distribution curve. This means that *typically* 80% of your results may actually come from only 20% of your efforts!

Pareto's law can be seen in many situations - not literally 80/20 but certainly the principle that the majority of your results will often come from the minority of your efforts.

So the really smart people are the people who can see (up-front without the benefit of hind-sight) *which* 20% to focus on.  In agile development, we should try to apply the 80/20 rule, seeking to focus on the important 20% of effort that gets the majority of the results.

If the quality of your application isn't life-threatening, if you have control over the scope, and if speed-to-market is of primary importance, why not seek to deliver the important 80% of your product in just 20% of the time? In fact, in that particular scenario, you could ask why you would ever bother doing the last 20%?

Now that doesn't mean your product should be fundamentally flawed, a bad user experience, or full of faults. It just means that developing some features, or the richness of some features, is going the extra mile and has a diminishing return that may not be worthwhile.

So does that statement conflict with my other recent post: "done means DONE!"? Not really. Because within each Sprint or iteration, what you *do* choose to develop *does* need to be 100% complete within the iteration.

As a slight aside, I was at Microsoft last week for an executive briefing on all their latest products. Sharepoint 2007 looks great by the way; a real leap from the earlier versions which were not really up to scratch. Vista, for those that haven't tried it, looked rather slow even on a laptop with 4GB RAM! And apart from being slightly prettier didn't really seem to offer much. Windows Workflow Services and .Net v3 looked pretty cool, if you can afford to develop in Microsoft tools ;-)

Anyway, back to my point about the 80/20 rule, Microsoft's own research found that the average user of Word uses only *8%* of the functionality. That's 8%! And I wouldn't mind betting at least 80% of us use the same 8% too! [assertion]. If Microsoft had developed only the important 8% of Word, maybe they could still have captured the same market share? Maybe, maybe not; sadly we will never know.

It's also worth considering the impact on user experience. Google has shown us that users often prefer apps that do just what you want. That's *just* what you want. And no more. The rest is arguably clutter and actually interferes with the user experience for only a limited benefit to a limited set of users.

So in an agile development world, when you're developing a brand new product, think very hard about what your app is *really* all about. Could you take it to market with all the important features, or with features that are less functionally rich, in a fraction of the time?

Apart from reduced cost, reduced risk and higher benefits by being quicker to market, you also get to build on the first release of the product based on real customer feedback.

So all of this is really common sense I suppose. But it's amazing how often development teams, with all the right intentions, over-engineer their solution. Either technically, or functionally, or both.

The really tough question, however, is can you see up-front *which* 20% is the important 20%? - the 20% that will deliver 80% of the results. In very many cases, the answer sadly is no.


Leave a Reply

Your email address will not be published. Required fields are marked *

three + sixteen =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”



To explore how we can help you, please get in touch