addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartrashtriangle-downtriangle-uptwitteruseryahoo

Re: Re: Re: [ljc] "I've never been a true believer in the Agile method"

From: Anatoli Davidson C.
Sent on: Wednesday, June 19, 2013 11:39 AM

Thanks for your reply, lots of useful info there! See my reply to Abraham re: the 80% stat. It's an approximation for the sake of discussion.

Luck has nothing (or very little) to do with success in the software projects, especially in the complex ones. You just don't happen to stumble by luck on the Linux kernel code :) In my personal humble experience I probably had to write (and subsequently delete) more than 100 lines of code before I arrived at the final 10 lines which I was happy to commit to the repo. See, again the "90% of everything is crap" rule is at work here :) It's inevitable.

Bad luck can be a factor in the failure of software projects, of course. There are a myriad of ways to fail in a software project and of them is pure misfortune, but there are very few ways to succeed and none of them is luck.

So, people deliver software projects not because they are lucky, but because they know what they are doing. The ones that get promoted and get to teach others are not necessarily the clever 20%. Plus the 80% of those "others" are the less clever bunch so they will inevitably misapply the methods preached by the gurus.

I agree that just having the right people is not enough. However it's 80% of success (please don't ask me from where did I get the 80% figure :)), because the right people will come up with the right methods (Gawande is a perfect example of the right type of person -- he saw a problem and he found a solution for it). They won't call it Agile or anything else with a capital first letter, they might just call it a checklist, and they will know not only what to put on that list, but also how to get it done.


Our Sponsors

  • Our Blog

    Read the latest news from the LJC

  • RecWorks Ltd

    Fixing Tech Recruitment using the Power of Community

  • jClarity

    Java/JVM Performance Analysis Tools & mentoring for Java related matters

  • LJC Aggrity

    Our LJC Aggrity site contains blog posts from our members

  • LJC Book Club

    Our Book club with book reviews from our members

  • Devoxx UK

    Java Community Conference in collaboration with the LJC, 8-10th June 16

  • SkillsMatter

    "Host, help organise, promote, film many of our meetings."

  • IBM

    Build Enterprise-grade apps at start-up speed.

  • New Relic

    New Relic makes sense of billions of metrics a day in real time.

  • Hazelcast

    Hazelcast is the leader in operating in-memory computing.

  • Java.Net

    We are an official Java User Group recognised by Oracle's JUG program

  • JRebel

    Free 3 month J-Rebel license.

  • O'Reilly

    40% discount on printed books and 50% on e-books.

  • Craft Rebellion

    Your choice of fresh craft beer, delivered. For 10% off use ‘LJC'

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy