Happy New Year!

fireworksThe SCALARE consortium wishes everybody a Happy and Healthy 2015. The project has been running now for approximately one year, and we’ve been working hard to better understand that software scaling phenomenon. In a few weeks, the project will have its first review, conducted by ITEA experts.

 

SCALARE will run till December 2016, and all project partners are looking forward to working on this exciting project! As the project progresses, we will upload the various deliverables, papers and reports on this website. Stay Tuned!

Scaling the process: Time-Based Releases

relengsiSCALARE partner Lero/University of Limerick and Dr Martin Michlmayr from HP have had a paper accepted in the Special Issue on Release Engineering, which will appear in IEEE Software magazine, which is targeted at software professionals. This special issue will be published in May/April 2015.

 

Release engineering is an important aspect in the software development life cycle, for several reasons. One of them is that companies who integrate open source software components into their products must synchronize their release cycle with the open source community release cycle. This paper presents work led by Dr Martin Michlmayr, who used to be project leader of the Debian Linux distribution and provides an argument for why open source projects should adopt time-based releases (rather than feature-based releases). The paper also provides a number of guidelines that indicate how they might do this.

SCALARE Features on LUCAS DAGEN

Reports of unusable IT systems are commonplace, and the latest of a long line is the police service’s new PUST system. Hundreds of millions of kronor are spent developing systems that eventually are canceled due to occupational safety and health issues. Why is it so hard to commission and develop these systems? Are there any good examples of ones that do what they set out to? Are the public procurement regulations to blame, is the technology inadequate, or do the users simply not know what they want?

 

This year’s LUCAS Day will focus on software procurement, taking an open-minded approach to discussions about potential causes and solutions to the issue. Perhaps we can even identify possible new areas of research on the topic. As is customary, we will also present current research and results from the software research projects at LTH.

 

Dr. Ulf Asklund discusses the SCALARE project in the video below (in Swedish).

 

A Case Study of Software Crowdsourcing

crowdpaperSCALARE partner Lero/University of Limerick has conducted a case study on software crowdsourcing. The case study was published in the proceedings of the International Conference on Software Engineering (ICSE) which was held in Hyderabad, India in June 2014. The abstract of the paper follows below, and the paper can be found here.

 

Abstract. Crowdsourcing is an emerging and promising approach which involves delegating a variety of tasks to an unknown workforce— the crowd. Crowdsourcing has been applied quite successfully in various contexts from basic tasks on Amazon Mechanical Turk to solving complex industry problems, e.g. InnoCentive. Companies are increasingly using crowdsourcing to accomplish specific soft- ware development tasks. However, very little research exists on this specific topic. This paper presents an in-depth industry case study of crowdsourcing software development at a multinational corporation. Our case study highlights a number of challenges that arise when crowdsourcing software development. For example, the crowdsourcing development process is essentially a waterfall model and this must eventually be integrated with the agile approach used by the company. Crowdsourcing works better for specific software development tasks that are less complex and stand-alone without interdependencies. The development cost was much greater than originally expected, overhead in terms of company effort to prepare specifications and answer crowdsourcing community queries was much greater, and the time-scale to complete contests, review submissions and resolve quality issues was significant. Finally, quality issues were pushed later in the lifecycle given the lengthy process necessary to identify and resolve quality issues. Given the emphasis in software engineering on identifying bugs as early as possible, this is quite problematic.

Inner Source Project Management

sp-changing-worldA new book has been launched with the title “Software Project Management in a Changing World“. The book is edited by Prof. Günther Ruhe and Prof. Claes Wohlin, and contains 18 chapters on contemporary and emerging software project management approaches. Among the contributors to the book are Dr. Sarah Beecham, Prof. Barry Boehm, Dr. Torgeir Dingsoyr, Prof. Mark Harman, Prof. Martin Shepperd, and Prof. Ioannis Stamelos. Prof. Martin Höst from the SCALARE Project also has co-authored a chapter with Dr. Klaas-Jan Stol and Alma Orucevic-Alagic on Inner Source Project Management.

Inner Source Tutorial: How to Adopt Open Source Development Practices inside Your Company?

ieeesw front croppedInner Source refers to the adoption of open source development practices within the confines of an organization. Inner Source offers numerous benefits, such as increased software reuse, increased transparency and personnel mobility. Inner Source is attracting a lot of interest from industry, including SCALARE partners such as Sony Mobile.

We’ve recently written a tutorial-style article that provides some insights into the adoption of Inner Source. The article has been accepted for publication in IEEE Software magazine, and is expected to be published in Spring 2015. However, the article is already available for download here.