Integrating Approaches in Software Development: A Case Analysis in a Small Software Company Mary Sánchez-Gordón 1[0000-0002-5102-1122] , Ricardo Colomo-Palacios 1[0000-0002-1555-9726] , Alex Sánchez 2 and Sandra Sanchez-Gordon 3 1 Østfold University College, Halden, Norway {mary.sanchez-gordon,ricardo.colomo-palacios}@hiof.no 2 LogicStudio Panamá, Panamá alex.sanchez@logicstudio.net 2 Escuela Politécnica Nacional Quito, Ecuador sandra.sanchez@epn.edu.ec Abstract. There are a myriad of software development methods, methodolo- gies, frameworks, techniques and practices in both traditional and agile soft- ware development. Seeking synergy between these approaches has become necessary for the evolution of a software development process. Software com- panies deal with that challenge by combining well-structured comprehensive methods and flexible agile practices. In fact, some studies have revealed that mixed approaches in software industry are not uncommon. This paper analyzes a case study of the evolution of a software development process in a small company, which is based on Design Thinking, PMBOK and SCRUM. Results show the natural evolution of the software process over 15 years and lessons learned from a pragmatic process selection. The evolution in the company de- pends on its adaptability which captures the capacity of the company to learn, combine experience and knowledge, and adjust its software process to a chang- ing context. Despite the results are promising further studies should be done. Keywords: Agile Software Development, Case Study, Lessons Learned. 1 Introduction Software practitioners, especially in small companies because of their nature [1], face a major challenge in shaping the many available methods, methodologies, frame- works and techniques [2, 3]. Even in the software process improvement field, there is a lot of diversity [1]. In fact, there is no silver-bullet or one-size-fits-all solution to all software development settings [3, 4]. Although, the literature has reported Waterfall as one of the most popular traditional (non-agile) approaches [4, 5], there are a large number of them, e.g. prototyping, spiral model and unified process. Additionally, Scrum is a well-known and popular agile approach [4, 5] but there are also a large number of them, e.g. Scrum, eXtreme Programming, Feature Driven Development and Crystal. Each approach, whether traditional or agile, is characterized by an indi- vidual specific structure that reflects the particular point of view and experiences of