Most of the software developers have never seen successful software projects

Image credits : freom fotolia

May be you are doing it wrong again and again because most of the software developers have never seen successful software projects, as per the statement of Dave Farley, a delivery evangelist. The more he added that may be they have built their careers on doing the wrong things.

Dave Farley, at Mannheim, while kicking off the CLC (Continuous Lifecycle Conference) stated that research after research had shown that even small software development projects can get big success. In one of the study, which was done by McKinsey and Oxford University on more than 5,400 software projects, showed that more than 17 per cent software projects were so catastrophically bad and they have threatened the existence of the company. With these kinds of statics, Dave Farley argued that individuals can easily spend their whole career in software development industry without even encountering an unequivocally successful software development projects. The more he added that according to me, “The maximum software developers have spent the maximum percentage of their careers not even knowing that what they are doing, what will be end project and how a successful software project looks like”.

Dave Farley traced a sorry state in software development projects and its practices which is based on the misreading fundamental of the 1970s Winston Royce paper as it considered the waterfall projects with an aims to shaped the traditional software development practices. This paper is description of what to do or not to do while working on software projects. But Dave Farley’s papers had gone into argument for feedback and testing and do the best possible job twice if possible. Royce was arguing in 1970s iterative development and Farley stated that we have a situation in present time where we prefer to take entirely ad hoc approach for software development which can leads towards the successful outcomes in comparison of previous traditional waterfall approaches. With an aim to improve the chances of producing a successful outcome, Farley advised that his audience should automate different stages of software projects such as; software testing, configuration management, pilot testing and slash cycle times.