Performance Alignment Work: How software developers experience the continuous adaptation of team performance in Lean and Agile environments

ContextCompanies increasingly strive to adapt to market and ecosystem changes in real time. Gauging and understanding team performance in such changing environments present a major challenge. ObjectiveThis paper aims to understand how software developers experience the continuous adaptation of performance in a modern, highly volatile environment using Lean and Agile software development methodology. This understanding can be used as a basis for guiding formation and maintenance of high-performing teams, to inform performance improvement initiatives, and to improve working conditions for software developers. MethodA qualitative multiple-case study using thematic interviews was conducted with 16 experienced practitioners in five organisations. ResultsWe generated a grounded theory, Performance Alignment Work, showing how software developers experience performance. We found 33 major categories of performance factors and relationships between the factors. A cross-case comparison revealed similarities and differences between different kinds and different sizes of organisations. ConclusionsBased on our study, software teams are engaged in a constant cycle of interpreting their own performance and negotiating its alignment with other stakeholders. While differences across organisational sizes exist, a common set of performance experiences is present despite differences in context variables. Enhancing performance experiences requires integration of soft factors, such as communication, team spirit, team identity, and values, into the overall development process. Our findings suggest a view of software development and software team performance that centres around behavioural and social sciences.

[1]  Robert Biddle,et al.  The Social Nature of Agile Teams , 2007, Agile 2007 (AGILE 2007).

[2]  Goparaju Purna Sudhakar,et al.  Soft factors affecting the performance of software development teams , 2011 .

[3]  Abigail Marks,et al.  Debugging the system: the impact of dispersion on the identity of software team members , 2005 .

[4]  Pekka Abrahamsson,et al.  Operationalizing the Concept of Success in Software Engineering Projects , 2011, Int. J. Innov. Digit. Econ..

[5]  S. Schneider National vs. corporate culture: Implications for human resource management , 1988 .

[6]  T. Cassidy Culture's consequences (abridged edn)—International differences in work-related values: G. Hofstede: Sage, London (1984). £11.95 , 1985 .

[7]  Tore Dybå,et al.  Team effectiveness in software development: Human and cooperative aspects in team effectiveness models and priorities for future studies , 2012, 2012 5th International Workshop on Co-operative and Human Aspects of Software Engineering (CHASE).

[8]  Kathleen M. Eisenhardt,et al.  Theory Building From Cases: Opportunities And Challenges , 2007 .

[9]  Fabian Fagerholm,et al.  Developer experience: Concept and definition , 2012, 2012 International Conference on Software and System Process (ICSSP).

[10]  Michael Eichberg,et al.  A Handbook of Software and Systems Engineering , 2009 .

[11]  Michael R. Harwell,et al.  Research design: Qualitative, quantitative, and mixed methods: Pursuing ideas as the keystone of exemplary inquir , 2011 .

[12]  Peter Cuyvers,et al.  Social perspectives: emote control , 1999, INTR.

[13]  Binshan Lin,et al.  Effect of team diversity on software project performance , 2007, Ind. Manag. Data Syst..

[14]  Dana E. Sims,et al.  Is there a “Big Five” in Teamwork? , 2005 .

[15]  Dragan Bjelica,et al.  Measuring Project Success in Project-Oriented , 2013 .

[16]  Petri Kettunen,et al.  Bringing Total Quality in to Software Teams: A Frame for Higher Performance , 2013, LESS.

[17]  Pekka Abrahamsson,et al.  Are Happy Developers more Productive? The Correlation of Affective States of Software Developers and their self-assessed Productivity , 2013, PROFES.

[18]  R. Yin Case Study Research: Design and Methods , 1984 .

[19]  Stig Larsson,et al.  Evaluating performance in the development of software-intensive products , 2014, Inf. Softw. Technol..

[20]  Sarma R. Nidumolu A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software Development Projects , 1996, J. Manag. Inf. Syst..

[21]  Thomas Shaw,et al.  The emotions of systems developers: an empirical study of affective events theory , 2004, SIGMIS CPR '04.

[22]  Paul Ralph,et al.  Report on the first SEMAT workshop on general theory of software engineering (GTSE 2012) , 2013, SOEN.

[23]  M. Hoegl,et al.  Teamwork Quality and the Success of Innovative Projects , 2001 .

[24]  Daniela Cruzes,et al.  Analyzing the Impact of Beliefs in Software Project Practices , 2011, 2011 International Symposium on Empirical Software Engineering and Measurement.

[25]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[26]  Jan Bosch,et al.  Climbing the "Stairway to Heaven" -- A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software , 2012, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.

[27]  G. Hofstede,et al.  Culture′s Consequences: International Differences in Work-Related Values , 1980 .

[28]  J. Hackman Why Teams Don’t Work , 1998 .

[29]  James Noble,et al.  Understanding Lack of Trust in Distributed Agile Teams: A grounded theory study , 2012, EASE.

[30]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[31]  G. Graen,et al.  Relationship-based approach to leadership: Development of leader-member exchange (LMX) theory of leadership over 25 years: Applying a multi-level multi-domain perspective , 1995 .

[32]  Kurt R. Linberg Software developer perceptions about software project failure: a case study , 1999, J. Syst. Softw..

[34]  A. Twycross Research design: qualitative, quantitative and mixed methods approaches Research design: qualitative, quantitative and mixed methods approaches Creswell John W Sage 320 £29 0761924426 0761924426 [Formula: see text]. , 2004, Nurse researcher.

[35]  Natalia Juristo Juzgado,et al.  Towards understanding the relationship between team climate and software quality—a quasi-experimental study , 2008, Empirical Software Engineering.

[36]  Albert Endres,et al.  A handbook of software and systems engineering - empirical observations, laws and theories , 2003, The Fraunhofer IESE series on software engineering.

[37]  I. Nonaka,et al.  A firm as a knowledge-creating entity: a new perspective on the theory of the firm , 2000 .

[38]  D. L. Gladstein Groups in context: A model of task group effectiveness. , 1984 .

[39]  Jürgen Münch,et al.  How do software developers experience team performance in lean and agile environments? , 2014, EASE '14.

[40]  Risa B. Hyman Creative chaos in high-performance teams: an experience report , 1993, CACM.

[41]  Jon R. Katzenbach,et al.  The Wisdom of Teams: Creating the High-Performance Organization , 1992 .

[42]  Heng-Li Yang,et al.  Team structure and team performance in IS development: a social network perspective , 2004, Inf. Manag..

[43]  Hee-Dong Yang,et al.  An exploratory study on meta skills in software development teams: antecedent cooperation skills and personality for shared mental models , 2008, Eur. J. Inf. Syst..

[44]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[45]  Ayse Basar Bener,et al.  Empirical analyses of the factors affecting confirmation bias and the effects of confirmation bias on software developer/tester performance , 2010, PROMISE '10.

[46]  Tore Dybå,et al.  Inferring Skill from Tests of Programming Performance: Combining Time and Quality , 2011, 2011 International Symposium on Empirical Software Engineering and Measurement.

[47]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[48]  Johnny Saldaña,et al.  The Coding Manual for Qualitative Researchers , 2009 .

[49]  Paul Ralph,et al.  The dimensions of software engineering success , 2014, ICSE.

[50]  R. Mcintyre,et al.  A Conceptual Framework for Teamwork Measurement , 1997 .

[51]  R. Yin,et al.  Case Study Research: Design and Methods (4th ed. , 2009 .

[52]  Torgeir Dingsøyr,et al.  Team Performance in Agile Development Teams: Findings from 18 Focus Groups , 2013, XP.

[53]  Fabio Q. B. da Silva,et al.  Motivation in software engineering: A systematic review update , 2011, EASE.

[54]  David L. Altheide,et al.  Criteria for assessing interpretive validity in qualitative research. , 1994 .

[55]  Ronald H. Rasch,et al.  Factors Affecting Software Developers' Performance: An Integrated Approach , 1992, MIS Q..

[56]  Gunnar R. Bergersen,et al.  Programming Skill, Knowledge, and Working Memory Among Professional Software Developers from an Investment Theory Perspective , 2011 .

[57]  Neil Douglas,et al.  From Belief to Knowledge: Achieving and Sustaining an Adaptive Culture in Organizations , 2010 .

[58]  Deborah G. Ancona,et al.  The Comparative Advantage of X-Teams , 2002 .

[59]  Andrew P. Martin,et al.  A multiple comparative study of test-with development product changes and their effects on team speed and product quality , 2011, Empirical Software Engineering.

[60]  P. Åstedt‐Kurki,et al.  Two approaches to the study of experiences of health and old age: the thematic interview and the narrative method. , 1994, Journal of advanced nursing.

[61]  K. Eisenhardt Building theories from case study research , 1989, STUDI ORGANIZZATIVI.

[62]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[63]  Juliet M. Corbin,et al.  Basics of Qualitative Research (3rd ed.): Techniques and Procedures for Developing Grounded Theory , 2008 .

[64]  J. Hackman,et al.  The design of work teams , 1987 .

[65]  Devendra Potnis,et al.  Culture's consequences: Economic barriers to owning mobile phones experienced by women in India , 2016, Telematics Informatics.

[66]  Helen Sharp,et al.  Motivation in Software Engineering: A systematic literature review , 2008, Inf. Softw. Technol..

[67]  Michal R. Wróbel,et al.  Emotions in the software development process , 2013, 2013 6th International Conference on Human System Interactions (HSI).

[68]  Philippe Kruchten,et al.  Reconciling perspectives: A grounded theory of how people manage the process of software development , 2012, J. Syst. Softw..

[69]  Tracy Hall,et al.  Motivating developer performance to improve project outcomes in a high maturity organization , 2007, Software Quality Journal.

[70]  Tracy Hall,et al.  Software developer motivation in a high maturity company: a case study , 2006, Softw. Process. Improv. Pract..

[71]  Sharan B. Merriam,et al.  Qualitative Research: A Guide to Design and Implementation , 2009 .

[72]  Robert M. Hierons,et al.  Do moods affect programmers’ debug performance? , 2011, Cognition, Technology & Work.