commercial successful software products that address a specific scientific domain usually started out as an exploratory prototype written by group of subject matter experts with strong scientific background who have acquired the programming skills, transforming their theoretical formulas into working code. research and planning typically do not marry well. particularly, the traditional waterfall approach with its strong focus on a predefined requirements scope, design and implementation phase, does not appeal to research staff who find it difficult to predict what they are going to build. this research showed that the lean asdm approach seems to be a better fit for research developers working on scientific software solutions for it embraces change. it was obvious that the iterative and incremental lifecycle approach that agile supports, proved to be much better tailored to the research way of development in that it allowed for timely changing direction if an idea does not yield the expected result or users provide different requirements. the same benefits applied when using research stories which are often difficult to manage.