Comments on: Lean Software Development http://missioncontrol.itteco.org/2009/12/20/lean-software-development/ Project Tales & Lesson Learned by Itteco Scrum Masters Sun, 25 Apr 2010 13:05:19 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Pavel Kartautsau http://missioncontrol.itteco.org/2009/12/20/lean-software-development/comment-page-1/#comment-5 Pavel Kartautsau Tue, 22 Dec 2009 07:22:08 +0000 http://missioncontrol.itteco.org/?p=41#comment-5 Sorry for confusing - I didn't mention anywhere 80/20 rule. 80 and 20 where just the examples... I should have given an example with 90 and 10 or 95 and 5: "In general you are satisfied if the feature is released with 90% of the functions, and the other 10% are not working - it is ok for you, they will be fixed soon". Sorry for confusing – I didn’t mention anywhere 80/20 rule. 80 and 20 where just the examples…

I should have given an example with 90 and 10 or 95 and 5: “In general you are satisfied if the feature is released with 90% of the functions, and the other 10% are not working – it is ok for you, they will be fixed soon”.

]]> By: Ivan Paramonau http://missioncontrol.itteco.org/2009/12/20/lean-software-development/comment-page-1/#comment-4 Ivan Paramonau Tue, 22 Dec 2009 00:44:45 +0000 http://missioncontrol.itteco.org/?p=41#comment-4 Funny coincidence. I bumped into exact same words at <a href="http://onstartups.com/tabid/3339/bid/11416/Releasing-Early-Is-Not-Always-Good-Heresy.aspx" rel="nofollow">OnStartups</a>: <strong>You're misinterpreting the 80/20 rule</strong> The typical 80/20 rule is: 80% of your customers use just 20% of your features. The "release early" folks take this to mean: Just implement 20% of the features you think you need, because if that's good enough to get 80% of your sales, this is a much simpler, efficient, and therefore profitable way to operate a software company. But this interpretation is wrong! To spell out the 80/20 rule more accurately: 80% of your customers use just 20% of your features, but each customer uses a different 20%. That implies you need more features, not fewer, otherwise there won't be enough for the various use-cases for your software. Funny coincidence. I bumped into exact same words at OnStartups:

You’re misinterpreting the 80/20 rule

The typical 80/20 rule is: 80% of your customers use just 20% of your features.

The “release early” folks take this to mean: Just implement 20% of the features you think you need, because if that’s good enough to get 80% of your sales, this is a much simpler, efficient, and therefore profitable way to operate a software company.

But this interpretation is wrong! To spell out the 80/20 rule more accurately: 80% of your customers use just 20% of your features, but each customer uses a different 20%. That implies you need more features, not fewer, otherwise there won’t be enough for the various use-cases for your software.

]]> By: Pavel Kartautsau http://missioncontrol.itteco.org/2009/12/20/lean-software-development/comment-page-1/#comment-3 Pavel Kartautsau Mon, 21 Dec 2009 13:17:21 +0000 http://missioncontrol.itteco.org/?p=41#comment-3 I agree with you. One of the ideas of the post was to give the examples of the projects where 'done' means at least 80%. (delivered means 100%). I'm not the fan of the "'done' means at least 80%", but in a real life such projects could take place. I agree with you.
One of the ideas of the post was to give the examples of the projects where ‘done’ means at least 80%. (delivered means 100%).
I’m not the fan of the “‘done’ means at least 80%”, but in a real life such projects could take place.

]]> By: Ivan Paramonau http://missioncontrol.itteco.org/2009/12/20/lean-software-development/comment-page-1/#comment-2 Ivan Paramonau Mon, 21 Dec 2009 05:13:33 +0000 http://missioncontrol.itteco.org/?p=41#comment-2 I think 80/20 principle is a bit misinterpreted. It suggests that 80% of features take 20% of development time. It does not say that you may deploy when 80% of feature works :) Lean, just like any other agile methodology, starts with the definition of 'Done'. It is usually an equivalent of 'Shippable', which suggests 'Bug-free'. It is very essential, as all agile processes are based on assumption that dev team does not come back to re-fix features. It is true for Scrum, and it is true for Lean too. I think 80/20 principle is a bit misinterpreted. It suggests that 80% of features take 20% of development time. It does not say that you may deploy when 80% of feature works :)

Lean, just like any other agile methodology, starts with the definition of ‘Done’. It is usually an equivalent of ‘Shippable’, which suggests ‘Bug-free’. It is very essential, as all agile processes are based on assumption that dev team does not come back to re-fix features. It is true for Scrum, and it is true for Lean too.

]]>