Eirini Kalliamvakou

Eirini Kalliamvakou

Auto-generated profile, based on publicly available information

Eirini Kalliamvakou

Computer Science, University of Victoria, Victoria, British Columbia Canada V8W 2Y2

Research Focus & Metrics

Academic Career Length

12Years (2015-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
5 September 2015 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
EKEirini Kalliamvakou
Eirini Kalliamvakou
GGGeorgios Gousios
Georgios Gousios
KBKelly Blincoe
Kelly Blincoe
LSLeif Singer
Leif Singer
DGDaniel M. German
Daniel M. German
DDDaniela Damian
Daniela Damian

28 August 2020 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
MSMargaret-Anne Storey
Margaret-Anne Storey
NENeil A. Ernst
Neil A. Ernst
CWCourtney Williams
Courtney Williams
EKEirini Kalliamvakou
Eirini Kalliamvakou

27 September 2019 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
MSMargaret-Anne Storey
Margaret-Anne Storey
TZThomas Zimmermann
Thomas Zimmermann
CBChristian Bird
Christian Bird
JCJacek Czerwonka
Jacek Czerwonka
BMBrendan Murphy
Brendan Murphy
EKEirini Kalliamvakou
Eirini Kalliamvakou
Developer satisfaction and work productivity are important considerations for software companies. Enhanced developer satisfaction may improve the attraction, retention and health of employees, while higher productivity should reduce costs and increase customer satis- faction through faster software improvements. Many researchers and companies assume that perceived productivity and job satisfaction are related and may be used as proxies for one another, but these claims are a current topic of debate. There are also many social and technical factors that may impact satisfaction and productivity, but which factors have the most impact is not clear, especially for specific development contexts. Through our research, we developed a theory articulating a bi-directional relationship between software developer job satisfaction and perceived productivity, and identified what additional social and technical factors, challenges and work context variables influence this relationship. The constructs and relationships in our theory were derived in part from related literature in software engineering and knowledge work, and we validated and extended these concepts through a rigorously designed survey instrument. We instantiate our theory with a large software company, which suggests a number of propositions about the relative impact of various factors and challenges on developer satisfaction and perceived productivity. Our survey instrument and analysis approach can be applied to other development settings, while our findings lead to concrete recommendations for practitioners and researchers.

2 November 2017 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
EKEirini Kalliamvakou
Eirini Kalliamvakou
CBChristian Bird
Christian Bird
TZThomas Zimmermann
Thomas Zimmermann
ABAndrew Begel
Andrew Begel
RDRobert DeLine
Robert DeLine
DGDaniel M. German
Daniel M. German
Having great managers is as critical to success as having a good team or organization. In general, a great manager is seen as fuelling the team they manage, enabling it to use its full potential. Though software engineering research studies factors that may affect the performance and productivity of software engineers and teams (like tools and skill), it has overlooked the software engineering manager. The software industry's growth and change in the last decades is creating a need for a domain-specific view of management. On the one hand, experts are questioning how the abundant work in management applies to software engineering. On the other hand, practitioners are looking to researchers for evidence-based guidance on how to manage software teams. We conducted a mixed methods empirical study of software engineering management at Microsoft to investigate what manager attributes developers and engineering managers perceive important and why. We present a conceptual framework of manager attributes, and find that technical skills are not the sign of greatness for an engineering manager. Through statistical analysis we identify how engineers and managers relate in their views, and how software engineering differs from other knowledge work groups in its perceptions about what makes great managers. We present strategies for putting the attributes to use, discuss implications for research and practice, and offer avenues for further work.

26 August 2019 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
PKPavneet Singh Kochhar
Pavneet Singh Kochhar
EKEirini Kalliamvakou
Eirini Kalliamvakou
NNNachiappan Nagappan
Nachiappan Nagappan
TZThomas Zimmermann
Thomas Zimmermann
CBChristian Bird
Christian Bird
Open source software systems have gained a lot of attention in the past few years. With the emergence of open source platforms like GitHub, developers can contribute, store, and manage their projects with ease. Large organizations like Microsoft, Google, and Facebook are open sourcing their in-house technologies in an effort to more broadly involve the community in the development of software systems. Although closed source and open source systems have been studied extensively, there has been little research on the transition from closed source to open source systems. Through the study we report in this paper we aim to: a) provide guidance and insight for other teams planning to open source their projects and b) to help them avoid pitfalls during the transition process. We studied six Microsoft systems, which were recently open-sourced i.e., CoreFX, CoreCLR, Roslyn, Entity Framework, MVC, and Orleans. This paper presents the transition from the viewpoints of both Microsoft and the open source community based on interviews with eleven Microsoft developer, five Microsoft senior managers involved in the decision to open source, and eleven open-source developers. From Microsoft's perspective we discuss the reasons for the transition, experiences of developers involved, and the transition's outcomes and challenges. Our results show that building a vibrant community, prompt answers, developing an open source culture, security regulations and business opportunities are the factors which persuade companies to open source their products. We also discuss the transition outcomes on processes such as code reviews, version control systems, continuous integration as well as developers' perception of these changes. From the open source community's perspective, we illustrate the response to the open-sourcing initiative through contributions and interactions with the internal developers and provide guidelines for other projects planning to go open source.

22 August 2026 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
RCRudrajit Choudhuri
Rudrajit Choudhuri
BTBianca Trinkenreich
Bianca Trinkenreich
RPRahul Pandita
Rahul Pandita
EKEirini Kalliamvakou
Eirini Kalliamvakou
ISIgor Steinmacher
Igor Steinmacher
ASAnita Sarma
Anita Sarma
Generative AI (genAI) tools promise productivity gains, yet developers still struggle to determine when to trust and effectively integrate these tools into their everyday work. Moreover, genAI can be exclusionary, failing to adequately support developers across individual differences. One such difference is cognitive style , which can shape how developers engage with genAI (e.g., risk-averse developers may gate outputs behind tests, whereas risk-tolerant ones may prototype directly and address issues post hoc). When tools fail to accommodate these differences, they can create additional usability barriers. Thus, to design tools that developers intend to use, we must understand which factors shape developers’ trust in and adoption of genAI at work . We developed a theoretical model of developers’ trust and adoption of genAI using a large-scale survey ( N = 238) conducted at GitHub and Microsoft. Using Partial Least Squares Structural Equation Modeling (PLS-SEM), we found aspects related to genAI’s system and output quality (e.g., presentation, safety/security, and performance), functional value (e.g., educational and practical benefits), and goal maintenance (ability to sustain alignment with task goals) to be significantly associated with trust. Trust, alongside developers’ cognitive styles (i.e., risk tolerance, technophilic motivations, and computer self-efficacy), was in turn significantly associated with adoption intentions, which ultimately were associated with reported usage. An Importance-Performance Matrix Analysis (IPMA) identified high-importance factors for which existing genAI tools provided insufficient support, highlighting actionable targets for design improvements. We bolstered these findings through a qualitative analysis of developers’ reported challenges and risks of genAI use, uncovering why these gaps persisted in development contexts. Our study offers practical guidance for designing genAI tools that support trustworthy and inclusive developer–AI interactions.