Software process fusion by combining pair and solo programming

The role of pair programming in software development is controversial. This is due partly to the relatively unclear benefit of pair programming over solo programming. There have been arguments either way and there have been studies to show that one is more cost-effective than the others. Rather than investigating into pair vs. solo programming here, we present a new process model combining both together. This paper argues and shows, with two case studies, that the fusing of pair and solo programming processes may actually be better than adopting either alone. In the proposed model called software process fusion (SPF), a donor and a recipient process can be defined and if some transfer conditions are met, one process can be converted into another to achieve tasks with minimal costs. The transfer conditions we define is related to a software fusion ratio (SFR). SFR can be used to evaluate the effectiveness of an SPF model. In our case studies, we observed that, with SPF, programmers would design solution patterns of their own in pairs and then use these patterns to build sub-modules in solos. We conclude that SPF can be a more effective approach to increase productivity of less experienced programmers.