ABSTRACT
Earlier empirical studies have demonstrated the interest that agile methods have generated in the software industry. Currently, lean approaches are increasingly adopted for complementing agile methods in software processes. With the goal of providing up-to-day results that can be used by organizations implementing or planning to implement agile and/or lean methods, we have conducted a study on the current stage of agile and lean adoption and usage in the software industry. For this purpose, we conducted an extensive survey among Finnish software practitioners in 2011, using the membership registry of The Finnish Information Processing Association (FIPA) as a sampling frame. 408 responses were collected from 200 software intensive organizations in the study. The survey included questions for identifying the rate of agile and lean usage in software organizations as well as the implementation of specific methods and practices, goals in adopting agile and lean, reasons for not applying these methods and effects of the agile and lean usage. The results of the survey reveal that a majority of respondents' organizational units are using agile and/or lean methods (58%). Furthermore, lean appears as a new player, being used by 24% of respondents, mainly in combination with agile (21%). The reasons and benefits for using agile and lean methods appeared to correspond in most parts to the findings of the earlier research. Generally, the experiences of using agile and lean methods seem to be rather positive, although challenges, such as obtaining management support and limitations for scaling agile in distributed settings, were also identified.
- Dybå, T. and Dingsøyr, T. 2008. Empirical studies of agile software development: A systematic review. Inf. Softw. Technol. 50, 9--10 (August 2008), 833--859. DOI=http://dx.doi.org/10.1016/j.infsof.2008.01.006 Google ScholarDigital Library
- Layman, L., Williams, L. and Cunningham, L. 2004. Exploring Extreme Programming in Context: An Industrial Case Study. In Proceedings of the Agile Development Conference (ADC '04). IEEE Computer Society, Washington, DC, USA, 32--41. Google ScholarDigital Library
- Melnik, G. and Maurer, F.2006. Comparative analysis of job satisfaction in agile and non-agile software development teams, Inc. Extreme Programming and Agile Processes in Software Engineering (XP 2006), LNCS 4004, pp. 32--42. Google ScholarDigital Library
- Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P. and Still, J. 2008. The impact of agile practices on communication in software development, Empir Software Eng (2008) 13:303--337, DOI=http://dx.doi.org/10.1007/s10664-008-9065-9. Google ScholarDigital Library
- Rico, D.F. 2008. Effects of Agile Methods on Website Quality for Electronic Commerce. In Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS '08). IEEE Computer Society, Washington, DC, USA, 463-. DOI=http://dx.doi.org/10.1109/HICSS.2008.137. Google ScholarDigital Library
- McHugh, O., Conboy, K. and Lang, M. 2011. The impact of agile practices on trust in software project teams, IEEE Software, 25 Aug. 2011. IEEE computer Society Digital Library. IEEE Computer Society, DOI= http://doi.ieeecomputersociety.org/10.1109/MS.2011.118. Google ScholarDigital Library
- Begel, A. and Nagappan, N. 2007. Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study. In Proceedings of the First International Symposium on Empirical Software Engineering and Measurement (ESEM '07). IEEE Computer Society, Washington, DC, USA, 255--264. DOI=http://dx.doi.org/10.1109/ESEM.2007.85. Google ScholarDigital Library
- Vijayasarathy, L. and Turk, D. 2008. Agile software development: A survey of early adopters, Journal of Information Tech. Management, vol. 19, no. 2Google Scholar
- Hanssen, G. K., Smite, D. and Brede Moe, N. 2011. Signs of agile trends in global software engineering research: A tertiary study. In Proceedings of the Sixth IEEE International Conference on Global Software Engineering Workshops, DOI 10.1109/ICGSE-W.2011.12. Google ScholarDigital Library
- Womack J.P., Jones D.T., Roos D. 1990. The Machine that Changed the World: The Story of Lean Production. New York: HarperPerennial.Google Scholar
- Poppendieck, M., Poppendieck, T.2007. Implementing lean software development: From concept to cash. Upper Saddle River, NJ: Addison-Wesley. Google ScholarDigital Library
- Freeman, P. 1992. Lean concepts in software engineering, IPSS-Europe International Conference on Lean Software Development, Stuttgart, Germany, pp. 1--8.Google Scholar
- Middleton, P., Flaxel, A. and Cookson, A. 2005. Lean software management case study: Timberline. Inc. Extreme Programming and Agile Processes in Software Engineering, (XP 2005) Springer-Verlag Berlin Heidelberg, pp.1--9. Google ScholarDigital Library
- Mehta, M., Anderson, D. and Raffo, D. 2008. Providing value to customers in software development through lean principles, Software Process Improvement and Practice, 13(1), January, 2008, pp.101--109. Google ScholarDigital Library
- Staats, B., Brunner, D. and Upton, D. 2011. Lean principles, learning, and knowledge work: Evidence from a software services provider, Journal of Operations Management, 29(5), July 2011, pp.376--390.Google ScholarCross Ref
- Mandic, V., Oivo, M., Rodriguez, P., Kuvaja, P., Kaikkonen H. and Turhan B. 2010 What is flowing in lean software development?, in Proceedings of the 1st International Conference on Lean Enterprise Software and Systems (LESS 2010), pp.72--84.Google ScholarCross Ref
- Petersen, K. and Wohlin, C. 2011. Measuring the flow in lean software development, Software: Practice and Experience, 41(9), August 2011, pp.975--996. Google ScholarDigital Library
- Wang, X. and Conboy, K. 2011. Comparing apples with oranges? Perspectives of a lean online community on the differences between agile and lean. Thirty Second International Conference on Information Systems (ICIS 2011). Shanghai.Google Scholar
- Chow, T. and Cao, D. B. 2008. A survey study of critical success factors in agile software projects, J. Syst. Softw., vol. 81, no. 6, pp. 961--971. DOI=http://dx.doi.org/10.1016/j.jss.2007.08.020. Google ScholarDigital Library
- Livermore, J. A. 2008. Factors that significantly impact the implementation of an agile software development methodology. Journal of Software, Vol. 3, No. 4, April (2008)Google ScholarCross Ref
- Misra, S. C., Kumar, V. and Kumar, U. 2009. Identifying some important success factors in adopting agile software development practices. J. Syst. Softw. 82, 11, 1869--1890. DOI=http://dx.doi.org/10.1016/j.jss.2009.05.052. Google ScholarDigital Library
- Dingsøyr, T., Dybå, T. and Abrahamsson, P. 2008. A preliminary roadmap for empirical research on agile software development. In Proceedings of the Agile 2008 (AGILE '08). IEEE Computer Society, Washington, DC, USA, 83--94. DOI=http://dx.doi.org/10.1109/Agile.2008.50. Google ScholarDigital Library
- Business Software Alliance. 2011. Investment for the Future Benchmarking IT Industry Competitiveness Report.Google Scholar
- Version One. 2011. The sixth annual "State of Agile Development" survey (available: http://www.versionone.com/pdf/2011_State_of_Agile_Development_Survey_Results.pdf)Google Scholar
- Ambler, S. 2008. Results from Scott Ambler's February 2008 Agile Adoption Survey (available: http://www.ambysoft.com/surveys/ )Google Scholar
- West, D. and Grant, T. 2010. Agile development: mainstream adoption has changed agility. Forrester Research.Google Scholar
- Salo, O. and Abrahamsson, P. 2008. Agile methods in European embedded software development organizations: a survey on the actual use and usefulness of extreme programming and scrum, Software, IET, vol. 2, no. 1, pp. 58--64.Google ScholarCross Ref
- Asnawi, A. L., Gravell, A. M. and Wills, B. 2011. Empirical investigation on agile methods usage: issues identified from early adopters in Malaysia. Inc. Extreme Programming and Agile Processes in Software Engineering (XP 2011), LNCS LNBIP 77, pp. 192--207Google Scholar
- Conboy K. 2009. Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development. Information Systems Research, 20(3), September 2009, pp.329--354. Google ScholarDigital Library
- Highsmith, J. 2002, Agile software development ecosystems, Addison-Wesley, Boston. Google ScholarDigital Library
- Poppendieck, M. 2002. Principles of lean thinking, http://www.leanessays.com/2002/11/principles-of-lean-thinking.html (last accessed March, 11, 2012)Google Scholar
- Coplien J. and Bjornwig G. 2010. Lean architecture for agile software development. West Sussex, UK, John Wiley & Sons Ltd. Google ScholarDigital Library
- Rodríguez, P., Markkula, J., Oivo, M., and Garbajosa, J. 2012. Analyzing the Drivers of the Combination of Lean and Agile in Software Development Companies, in Proceedings of the 13th International Conference on Product Focused Software Development and Process Improvement (PROFES 2012), pp. 145--159. Google ScholarDigital Library
Index Terms
- Survey on agile and lean usage in finnish software industry
Recommendations
Empirical Study of Agile Software Development Methodologies: A Comparative Analysis
In today's software industry, technological prowess and ever-evolving customer requirements have led to more complex software demands. Agile based software development is increasingly being adopted by the software practitioners as it assures early ...
Facilitating Agile Software Development with Lean Architecture in the DCI Paradigm
ITNG '12: Proceedings of the 2012 Ninth International Conference on Information Technology - New GenerationsBoth agile software development and lean architecture have been studied in the software engineering field. Combining these two approaches has also been investigated. However, the existing research and practices only present the principles but fail to ...
Lean Software Development: A Tutorial
“Lean Software Development” has become a popular term over the last few years. This tutorial describes where it comes from, what it means, how it relates to well-known agile development practices, and how it will evolve in the future.
Comments