Beatriz Silva De Santana
Manoel Mendonca
ABSTRACT
[Context] Interpersonal relationships are as important as processes and technology mastery in software engineering. These relationships can impact the quality of the software product and the software teams’ quality of life. Understanding how and which aspects impact interpersonal relationships is essential for a psychologically safe environment. However, little is known about which aspects may affect the maintenance of a psychologically safe environment within the software engineering context. [Aims] This study aims to investigate interpersonal conflict scenarios and their potential indicators of psychological insecurity from the perspective of software practitioners. [Method] This article identified and qualitatively analyzed discussions related to psychological safety on Stack Exchange, an important question-and-answer site used by software professionals in their daily activities. [Results] We identified 11 scenarios concentrated on four types of interpersonal relationships: with the client, with team members, with leadership, and with other departments. In addition, we investigated whether there were previous attempts to resolve conflicts. Lastly, we found seven potential indicators of psychological insecurity in the conflicts exposed. [Conclusion] We organized the set of scenarios and their potential indicators of psychological insecurity in a Sankey diagram. It can support researchers and practitioners in understanding how to define a healthier and more productive environment for software projects.
- Faheem Ahmed, Luiz Fernando Capretz, Salah Bouktif, and Piers Campbell. 2013. Soft Skills and Software Development: A Reflection from the Software Industry. Journal of Information Processing and Management (IJIPM) 4, 3 (2013), 171.Google Scholar
Cross Ref
- Faheem Ahmed, Luiz Fernando Capretz, and Piers Campbell. 2012. Evaluating the demand for soft skills in software development. It Professional 14, 1 (2012), 44–49.Google ScholarDigital Library
- Mohammad R Basirati, Marko Otasevic, Koushyar Rajavi, Markus Böhm, and Helmut Krcmar. 2020. Understanding the relationship of conflict and success in software development projects. Information and Software Technology 126 (2020), 106331.Google ScholarCross Ref
- Luiz Fernando Capretz. 2014. Bringing the human factor to software engineering. IEEE software 31, 2 (2014), 104–104.Google Scholar
- Mikkel Agerlin Christensen and Paolo Tell. 2022. Building a Toolbox for Working with Psychological Safety in Agile Software Teams. In Agile Processes in Software Engineering and Extreme Programming: 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13–17, 2022, Proceedings. Springer, 82–98.Google ScholarCross Ref
- John W Creswell and J David Creswell. 2017. Research design: Qualitative, quantitative, and mixed methods approaches. Sage publications.Google Scholar
- R. S. Dubey, V. Tewari, and B. Pandiya. 2017. A soft approach towards gaining employability in IT professionals. In 2017 IEEE International Conference on Industrial Engineering and Engineering Management (IEEM). 299–303. https://doi.org/10.1109/IEEM.2017.8289900Google ScholarCross Ref
- Charles Duhigg. 2016. What Google learned from its quest to build the perfect team. The New York Times Magazine 26, 2016 (2016), 2016.Google Scholar
- Amy Edmondson. 1999. Psychological safety and learning behavior in work teams. Administrative science quarterly 44, 2 (1999), 350–383.Google Scholar
- Amy C Edmondson. 2002. Managing the risk of learning: Psychological safety in work teams. Wiley Online Library. 255–275 pages.Google Scholar
- Amy C Edmondson. 2018. The fearless organization: Creating psychological safety in the workplace for learning, innovation, and growth. John Wiley & Sons.Google Scholar
- Amy C Edmondson and Zhike Lei. 2014. Psychological safety: The history, renaissance, and future of an interpersonal construct. Annu. Rev. Organ. Psychol. Organ. Behav. 1, 1 (2014), 23–43.Google ScholarCross Ref
- Rafael Elizalde and Sussy Bayona. 2018. Interpersonal relationships, leadership and other soft skills in software development projects: a systematic review. Trends and Advances in Information Systems and Technologies: Volume 2 6 (2018), 3–15.Google ScholarCross Ref
- Sávio Freire, Felipe Gomes, Larissa Barbosa, Thiago Souto Mendes, Galdir Reges, Rita SP Maciel, Manoel Mendonça, and Rodrigo Spínola. 2023. Requirements Engineering Issues Experienced by Software Practitioners: A Study on Stack Exchange. In Requirements Engineering: Foundation for Software Quality: 29th International Working Conference, REFSQ 2023, Barcelona, Spain, April 17–20, 2023, Proceedings. Springer, 3–20.Google ScholarDigital Library
- Felipe Gomes, Eder Pereira dos Santos, Sávio Freire, Manoel Mendonça, Thiago Souto Mendes, and Rodrigo Spínola. 2022. Investigating the point of view of project management practitioners on technical debt: a preliminary study on stack exchange. In Proceedings of the International Conference on Technical Debt. 31–40.Google ScholarDigital Library
- Mark A Griffin and Matteo Curcuruto. 2016. Safety climate in organizations. Annual review of organizational psychology and organizational behavior 3 (2016), 191–212.Google Scholar
- Phil Hennel and Christoph Rosenkranz. 2021. Investigating the “Socio” in Socio-technical development: The case for psychological safety in agile information systems development. Project Management Journal 52, 1 (2021), 11–30.Google ScholarCross Ref
- Dron Khanna and Xiaofeng Wang. 2022. Are Your Online Agile Retrospectives Psychologically Safe? the Usage of Online Tools. In Agile Processes in Software Engineering and Extreme Programming: 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13–17, 2022, Proceedings. Springer, 35–51.Google ScholarCross Ref
- Klaus Krippendorff. 1980. Content Analysis: An Introduction to its Methodology. Beverly Hills, CA: Sage.Google Scholar
- Per Lenberg and Robert Feldt. 2018. Psychological safety and norm clarity in software engineering teams. In Proceedings of the 11th international workshop on cooperative and human aspects of software engineering. 79–86.Google ScholarDigital Library
- Julie Yu-Chih Liu, Hun-Gee Chen, Charlie C Chen, and Tsong Shin Sheu. 2011. Relationships among interpersonal conflict, requirements uncertainty, and software project performance. International Journal of Project Management 29, 5 (2011), 547–556.Google ScholarCross Ref
- Richard C Lupton and Julian M Allwood. 2017. Hybrid Sankey diagrams: Visual analysis of multidimensional data for understanding resource use. Resources, Conservation and Recycling 124 (2017), 141–151.Google ScholarCross Ref
- Gerardo Matturro, Florencia Raschetti, and Carina Fontán. 2019. A Systematic Mapping Study on Soft Skills in Software Engineering.J. Univers. Comput. Sci. 25, 1 (2019), 16–41.Google Scholar
- Frances J Milliken, Elizabeth W Morrison, and Patricia F Hewlin. 2003. An exploratory study of employee silence: Issues that employees don’t communicate upward and why. Journal of management studies 40, 6 (2003), 1453–1476.Google ScholarCross Ref
- Alexander Newman, Ross Donohue, and Nathan Eva. 2017. Psychological safety: A systematic review of the literature. Human resource management review 27, 3 (2017), 521–535.Google Scholar
- Róisín O’donovan and Eilish Mcauliffe. 2020. A systematic review of factors that enable psychological safety in healthcare teams. International journal for quality in health care 32, 4 (2020), 240–250.Google ScholarCross Ref
- Róisín O’Donovan, Desirée Van Dun, and Eilish McAuliffe. 2020. Measuring psychological safety in healthcare teams: developing an observational measure to complement survey methods. BMC medical research methodology 20 (2020), 1–17.Google Scholar
- Daryl Posnett, Eric Warburg, Premkumar Devanbu, and Vladimir Filkov. 2012. Mining stack exchange: Expertise is evident from initial contributions. In 2012 International Conference on Social Informatics. IEEE, 199–204.Google ScholarDigital Library
- Umar Safdar, Yuosre F Badir, and Bilal Afsar. 2017. Who can I ask? How psychological safety affects knowledge sourcing among new product development team members. The Journal of High Technology Management Research 28, 1 (2017), 79–92.Google ScholarCross Ref
- Eder Pereira Santos, Felipe Gomes, Sávio Freire, Manoel Mendonça, Thiago Souto Mendes, and Rodrigo Spínola. 2022. Technical Debt on Agile Projects: Managers’ point of view at Stack Exchange. In Proceedings of the XXI Brazilian Symposium on Software Quality. 1–9.Google ScholarDigital Library
- Edgar H Schein 1992. How can organizations learn faster?: the problem of entering the Green Room. MIT Sloan Management Review 34, 2 (1992), 85.Google Scholar
- Subhasree Sengupta and Caroline Haythornthwaite. 2020. Learning with comments: An analysis of comments and community on Stack Overflow. In 53rd Annual Hawaii International Conference on System Sciences, HICSS 2020. IEEE Computer Society, 2898–2907.Google ScholarCross Ref
- Amjed Tahir, Jens Dietrich, Steve Counsell, Sherlock Licorish, and Aiko Yamashita. 2020. A large scale study on how developers discuss code smells and anti-pattern in stack exchange sites. Information and Software Technology 125 (2020), 106333.Google ScholarCross Ref
- Robert Philip Weber. 1990. Basic content analysis. Vol. 49. Sage.Google Scholar
Index Terms
- Exploring Psychological Safety in Software Engineering: Insights from Stack Exchange
Recommendations
A Survey of Software Engineering Practice: Tools, Methods, and Results
The results of a survey of software development practice are reported and analyzed. The problems encountered in various phases of the software life cycle are measured and correlated with characteristics of the responding installations. The use and ...
Software engineering research versus software development
Engineering research differs greatly, both in its aims and in its methods, from traditional "scientific" research. While Sciences deal with the study of existing objects and phenomena, be it physically, metaphysically or conceptually, Engineering is ...
Antecedents of psychological safety in agile software development teams
Abstract Context:Psychological safety continues to inspire researchers’ curiosity in various fields of study. It has been shown to enhance teams’ performance, efficiency, and learning, among other corollaries. Researchers are ...
Highlights- Researchers explore psychological safety impacts, expanding current knowledge.
- ...
Comments