Abstract
Risk—the possibility of resulting in an unsatisfactory outcome—is an important driving force for a software development project to progress. Although techniques like identifying a project’s top-10 risk items are taught commonly in software engineering courses, little work has been carried out to examine how students working in agile teams perceive and mitigate the risks over multiple software development cycles. In this chapter, we summarize our recent work where we discovered the collaborative nature of students’ risk management strategies. Furthermore, we show that students also followed lean practices by wasting little effort on non-actionable risks. Linking collaboration and waste-elimination provided additional insights into teaching a wider range of lean principles in agile settings, e.g., students should deliver as fast as possible the non-collaborative risk mitigations but should decide as late as possible when facing interdependent mitigations.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
Agresti, A. (2007). An introduction to categorical data analysis. Wiley.
Anslow, C., & Maurer, F. (2015). An experience report at teaching a group based agile software development project course. In Proceedings of the ACM Technical Symposium on Computer Science Education, Kansas City, MO, USA (pp. 500–505).
Baeza-Yates, R., & Ribeiro-Neto, B. (1999). Modern information retrieval. Addison-Wesley.
Beck, K., et al. (2001). Manifesto for agile software development. Agile Alliance. Retrieved from http://agilemanifesto.org/.
Bhowmik, T., Niu, N., Wang, W., Cheng, J.-R. C., Li, L., & Cao, X. (2016). Optimal group size for software change tasks: A social information foraging perspective. IEEE Transactions on Cybernetics, 46(8), 1784–1795.
Boehm, B. (1986). A spiral model of software development and enhancement. ACM SIGSOFT Software Engineering Notes, 11(4), 14–24.
Boehm, B. (1991). Software risk management: Principles and practices. IEEE Software, 8(1), 32–41.
Boehm, B. (2007). Top 10 software-intensive system risk items. In Presentation at USC Annual Research Review.
Cantrell, G., Dampier, D., Dandass, Y., Niu, N., & Bogen, C. (2012). Research toward a partially-automated, and crime specific digital triage process model. Computer and Information Science, 5(2), 29–38.
Carr, M. J., Konda, S. L., Monarch, I., Ulrich, F. C., & Walker, C. F. (1993). Taxonomy-based risk identification. Technical Report, CMU/SEI-93-TR-6.
Cohn, M. (2013). A framework for evaluating agile risk management. Retrieved from https://tcagley.wordpress.com/2013/10/01/a-framework-for-evaluating-agile-risk-management-daily-process-thoughts/.
Collofello, J. S., & Pinkerton, A. K. (1997). Integrating risk management into an undergraduate software engineering course. In Proceedings of the 27th Annual Conference on Frontiers in Education, Pittsburgh, PA, USA (pp. 856–860).
Devedzic, V., & Milenkovic, S. (2011). Teaching agile software development: A case study. IEEE Transactions on Education, 54(2), 273–278.
Emiliani, M. L. (2004). Improving business school courses by applying lean principles and practices. Quality Assurance in Education, 12(4), 175–187.
Gabrilovich, M., & Markovitch, S. (2007). Computing semantic relatedness using Wikipedia-based explicit semantic analysis. In Proceedings of the International Joint Conference on Artificial Intelligence, Hyderabad, India (pp. 1606–1611).
Gosall, N. K., & Gosall, G. S. (2015). The doctor’s guide to critical appraisal. Chestire: Knutsford.
Hanna, J. (2007). Bringing ‘lean’ principles to service industries. Harvard Business School Working Paper, No. 08-001.
Holweg, M. (2007). The genealogy of lean production. Journal of Operations Management, 25(2), 420–437.
Hoodat, H., & Rashidi, H. (2009). Classification and analysis of risks in software engineering. International Journal of Computer, Electrical, Automation, Control and Information Engineering, 3(8), 2044–2050.
ISO. (2018). ISO (International Organization for Standardization) 31000—Risk management. Retrieved from https://www.iso.org/iso-31000-risk-management.html.
Kamble, S., **, X., Niu, N., & Simon, M. (2017). A novel coupling pattern in computational science and engineering software. In Proceedings of the International Workshop on Software Engineering for Science, Buenos Aires, Argentina (pp. 9–12).
Ker, J. I., Wang, Y., Hajli, M. N., Song, J., & Ker, C. W. (2014). Deploying lean in healthcare: Evaluating information technology effectiveness in US hospital pharmacies. International Journal of Information Management, 34(4), 556–560.
Koolmanojwong, S., & Boehm, B. (2013). A look at software engineering risks in a team project course. In Proceedings of the International Conference on Software Engineering Education and Training, San Francisco, CA, USA (pp. 21–30).
Mahmoud, A., Niu, N., & Xu, S. (2012). A semantic relatedness approach for traceability link recovery. In Proceedings of the International Conference on Program Comprehension, Passau, Germany (pp. 183–192).
Mahmoud, A., & Niu, N. (2015). One the role of semantics in automated requirements tracing. Requirements Engineering, 20(3), 281–300.
Niu, N., Bhowmik, T., Liu, H., & Niu, Z. (2014a). Traceability-enabled refactoring for managing just-in-time requirements. In Proceedings of the International Requirements Engineering Conference, Karlskrona, Sweden (pp. 133–142).
Niu, N., Brinkkemper, S., Franch, X., Partanen, J., & Savolainen, S. (2018). Requirements engineering and continuous deployment. IEEE Software, 35(2), 86–90.
Niu, N., & Easterbrook, S. (2007). Analysis of early aspects in requirements goal models: A concept-driven approach. Transactions on Aspect-Oriented Software Development, III, 40–72.
Niu, N., Savolainen, J., Niu, Z., **, M., & Cheng, J.-R. C. (2014b). A systems approach to product requirements reuse. IEEE Systems Journal, 8(3), 826–827.
Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit. Addison-Wesley.
Radnor, Z., Walley, P., Stephens, A., & Bucci, G. (2006). Evaluation of the lean approach to business management and its use in the public section. Scottish Executive Social Research.
Reifer, D. (2002). Ten deadly risks in internet and intranet software development. IEEE Software, 6(2), 12–14.
Rico, D. F., & Sayani, H. H. (2009). Use of agile methods in software engineering education. In Proceedings of the Agile Conference, Chicago, IL, USA (pp. 174–179).
Ropponen, J., & Lyytinen, K. (2000). Components of software development risks: How to address them? A project manager survey. IEEE Transactions on Software Engineering, 26(2), 98–112.
Schmidt, C., Dart, P., Johnston, L., Sterling, L., & Thorne, P. (1999). Disincentives for communicating risk: A risk paradox. Information and Software Technology, 41(7), 403–411.
Schroeder, A., Klarl, A., Mayer, P., & Kroiss, C. (2012). Teaching agile software development through lab courses. In Proceedings of the IEEE Global Engineering Education Conference, Marrakech, Morocco (pp. 1–10).
Sharpe, D. (2015). Your chi-square test is statistically significant: Now what? Practical Assessment, Research & Evaluation, 20(8), 1–10.
Strube, M., & Ponzetto, S. (2006). Wikirelate! Computing semantic relatedness using Wikipedia. In Proceedings of the National Conference on Artificial Intelligence, Boston, MA, USA (pp. 1419–1424).
Thota, C., Niu, N., Wang, W., & Purdy, C. C. (2017). Students’ perceptions of software risks. In Proceedings of the ASEE Annual Conference, Columbus, OH, USA, Article No. 18053.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2019 Springer Nature Singapore Pte Ltd.
About this chapter
Cite this chapter
Wang, W., Thota, C., **, X., Niu, N., Purdy, C.C. (2019). Lean Learning of Risks in Students’ Agile Teams. In: Parsons, D., MacCallum, K. (eds) Agile and Lean Concepts for Teaching and Learning. Springer, Singapore. https://doi.org/10.1007/978-981-13-2751-3_13
Download citation
DOI: https://doi.org/10.1007/978-981-13-2751-3_13
Published:
Publisher Name: Springer, Singapore
Print ISBN: 978-981-13-2750-6
Online ISBN: 978-981-13-2751-3
eBook Packages: EducationEducation (R0)