Steffen Küpper
ABSTRACT
Hybrid approaches for software and system development have become reality. Recent research shows the use of hybrid development approaches mainly grounded in experience and driven by pragmatism. At the same time, a vast number of success factors is known that influences process development and process use alike. However, even though industrial practice shows a need for hybrid development approaches and knowledge regarding the success factors is in place, a systematic approach to develop, deploy and tailor hybrid development approaches is missing. This paper reports on ongoing research that aims at developing a method to support the evidence-driven construction of hybrid development approaches. We provide an overview of the required method components and outline how hybrid development approaches can be deployed at the organizational level and tailored at the project level. We further give an overview of ongoing and completed studies supporting the method's construction and evaluation.
- B. Boehm and R. Turner. 2003. Using Risk to Balance Agile and Plan-Driven Methods. IEEE Computer 36, 6 (2003), 57--66. Google Scholar
Digital Library
- B. Boehm and R. Turner. 2005. Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software 22, 5 (2005), 30--39. Google ScholarDigital Library
- P. Clarke and R.V. O'Connor. 2012. The situational factors that affect the software development process: Towards a comprehensive reference framework,. Journal of Information Software and Technology 54 (2012), 433--447. Google ScholarDigital Library
- P. Clarke, R. V. O'Connor, B. Leavy, and M. Yilmaz. 2015. Exploring the Relationship between Software Process Adaptive Capability and Organisational Performance. IEEE Transactions on Software Engineering 41, 12 (Dec 2015), 1169--1183.Google ScholarCross Ref
- M. Cusumano, A. MacCormack, C. F. Kemerer, and W. Crandall. 2003. Software Development Worldwide: The State of the Practice. 20, 6 (2003), 28--34. Google ScholarDigital Library
- P. Diebold and T. Zehler. 2016. The Right Degree of Agility in Rich Processes. In Managing Software Process Evolution. Springer International Publishing, Chapter 2, 15--37.Google Scholar
- T. Dingsøyr, S. Nerur, V. Balijepally, and N. B. Moe. 2012. A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software 85, 6 (2012), 1213--1221. Google ScholarDigital Library
- B. Henderson-Sellers, J. Ralyte, and P. J. Agerfalk. 2014. Situational Method Engineering. Springer. Google ScholarDigital Library
- S. Jeners, P. Clarke, R. V. O'Connor, L. Buglione, and M. Lepmets. 2013. Harmonizing Software Development Processes with Software Development Settings - A Systematic Approach. In Systems, Software and Services Process Improvement, F. McCaffery, R V. O'Connor, and R. Messnarz (Eds.). Springer Berlin Heidelberg, Berlin, Heidelberg, 167--178.Google Scholar
- C. Jones. 2003. Variations in Software Development Practices. IEEE Software 20, 6 (2003), 22--27. Google ScholarDigital Library
- J. Klünder, P. Hohl, M. Fazal-Baqaie, S. Krusche, S. Küpper, O. Linssen, and C. R. Prause. 2017. HELENA Study: Reasons for Combining Agile and Traditional Software Development Approaches in and German Companies. In Proceedings of the 18th International Conference on Product-Focused Software Process Improvement. 428--434.Google Scholar
- M. Kuhrmann. 2015. Crafting a Software Process Improvement Approach - A Retrospectice Systematization. Journal of Software: Evolution and Process 27, 2 (2015), 114--145. Google ScholarDigital Library
- M. Kuhrmann and S. Beecham. 2014. Artifact-Based Software Process Improvement and Management: A Method Proposal. In Proceedings of the 2014 International Conference on Software and System Process. 119--123. Google ScholarDigital Library
- M. Kuhrmann, P. Diebold, and J. Münch. 2016. Software Process Improvement: A systematic mapping study on the state of the art. Peer J Computer Science 2, 1 (2016), 1--38.Google Scholar
- M. Kuhrmann, P. Diebold, J. Münch, P. Tell, V. Garousi, M. Felderer, K. Trektere, F. McCaffery, and O. Linssen. 2017. Hybrid Software and System Development in Practice: Waterfall, Scrum, and Beyond. In Proceedings of the 2017 International Conference on Software and System Process. 30--39. Google ScholarDigital Library
- M. Kuhrmann, P. Diebold, J. Münch, P. Tell, K. Trektere, F. McCaffrey, G. Vahid, M. Felderer, O. Linssen, E. Hanser, and C. Prause. 2018. Hybrid Software Development Approaches in Practice: A European Perspective. In IEEE Software, Vol. PP. IEEE.Google Scholar
- S. Küpper, M. Kuhrmann, M. Wiatrok, U. Andelfinger, and A. Rausch. 2017. Is There a Blueprint for Building an Agile Culture?. In Projektmanagement und Vorgehensmodelle 2017. Bonn, 111--127.Google Scholar
- B. Murphy, C. Bird, T. Zimmermann, L. Williams, N. Nagappan, and A. Begel. 2013. Have Agile Techniques been the Silver Bullet for Software Development at Microsoft. In 2013 ACM/ IEEE International Symposium on Empirical Software Engineering and Measurement.Google Scholar
- P. O'Leary and I. Richardson. 2012. Process reference model construction: implementing an evolutionary multi-method research approach. IET Software 6, 5 (2012), 423--430.Google ScholarCross Ref
- E. Papatheocharous and A. S. Andreou. 2014. Empirical evidence and state of practice of software agile teams. Journal of Software: Evolution and Process 26, 9 (2014), 855--866. Google ScholarDigital Library
- A. Raninen, J. J. Ahonen, H.-M. Sihvonen, P. Savolainen, and S. Beecham. 2012. LAPPI: A light-weight technique to practical process modeling and improvement target identification. Journal of Software: Evolution and Process 25, 9 (2012), 915--933.Google ScholarCross Ref
- G. Theocharis, M. Kuhrmann, J. Münch, and P. Diebold. 2016. Is Water-Scrum-Fall Reality? On the Use and of Agile and Traditional Development Practices. In Proceedings of the 16th International Conference on Product-Focused Software Process Improvement. 149--166. Google ScholarDigital Library
- L. R. Vijayasarathy and C. W. Butler. 2016. Choice of Software Development Methodologies: Do Organizational, Project, and Team Characteristics Matter? IEEE Software 33, 5 (2016), 86--94.Google ScholarDigital Library
- D. West. 2011. Water-Scrum-Fall Is The Reality Of Agile For Most Organizations Today. Technical Report. Forrester.Google Scholar
Index Terms
- Towards the systematic development of hybrid software development processes
Recommendations
Towards Improving the Organization of Hybrid Development Approaches
ICSSP '20: Proceedings of the International Conference on Software and System ProcessesAgile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with ...
How are Hybrid Development Approaches Organized?: A Systematic Literature Review
ICSSP '20: Proceedings of the International Conference on Software and System ProcessesAgile software development methods promise shorter time-to-market and higher product quality, but lack the ability of long-term planning or coping with large projects. However, software companies often also want the ability of long-term planning, ...
Expert Survey on Current Trends in Agile, Disciplined and Hybrid Practices for Software Development
AbstractEvery software development company makes software development based on a specific approach. There are a number of approaches to software development, both disciplined and agile. Each approach includes a set of different activities. Sometimes, the ...
Comments