Issue No.04 - July-Aug. (2012 vol.29)
Chris Morris , Science and Technology Facilities Council, UK
Judith Segal , Open University, UK
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2012.93
In the mid-90s, I was working for a company transitioning to agile software development. We hadn't considered that our biggest problem in this change was that developers would be talking directly to customers. After some small disasters, we realized that somehow we needed to transfer the expertise and experience of our business and marketing teams to developers. When I first read the current Insights article, I immediately recognized many patterns in the list of lessons learned and that what these authors have to say is much broader than “scientific” software—it's about any kind of software, actually, any kind of development effort.
scientific databases, software development, requirements, lessons learned
Chris Morris, Judith Segal, "Lessons Learned from a Scientific Software Development Project", IEEE Software, vol.29, no. 4, pp. 9-12, July-Aug. 2012, doi:10.1109/MS.2012.93