Skip to Main Content
This paper reports an experience of a solo programmer who added a new feature into an open source program called muCommander. The process is observed on two granularities: Granularity of software change (SC) and granularity of Solo Iterative Process (SIP). The experience confirms that both SC and SIP process models can be successfully enacted, are able to implement the described feature, and produced a high quality code in reasonable time. The lessons learned, particularly the exit criteria for SC phases, are discussed in more detail in the paper and may be applicable to team iterative processes, including agile processes.