A framework to study requirements-driven collaboration among agile teams: Findings from two case studies

A framework is proposed to study requirements-driven collaboration among agile teams.Also, it finds the impact of their collaboration patterns on the iteration performance.Collaboration is translated in terms of communication and awareness.Two case studies were conducted to implement the framework.The results aid the project managers to learn about their teams' collaboration health. Stakeholders' collaboration is required to develop requirements in agile software development. Requirements engineering and agile methods share common grounds as they both focus on stakeholder collaboration. The key issue is finding a way to study collaboration driven by requirements in geographically distributed agile teams. In this paper, we aim to propose a framework to study collaboration driven by requirements among agile teams and determine the impact of their collaboration patterns on the iteration performance. We define collaboration in terms of communication as information exchange among members, and awareness knowledge of others. Two case studies were conducted to examine communication and awareness network patterns among distributed agile teams. Data were collected through questionnaires, semi-structured interviews and onsite observation. The findings revealed that the framework aids in determining the core members, collaboration trends, clustering tendency, communication and awareness reciprocity of the teams, small worldliness and centralisation behaviour of the networks and iteration performance of the agile teams. The framework has implications for the industrial practitioners, i.e. managers to learn about their team's collaboration in order to take measures for performance improvement. At the same time, the researchers can use this framework to study other social aspects in variable settings to produce more empirical results.

[1]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[2]  Mira Kajko-Mattsson,et al.  Classes of Distributed Agile Development Problems , 2010, 2010 Agile Conference.

[3]  Sherlock A. Licorish,et al.  Understanding the attitudes, knowledge sharing behaviors and task performance of core developers: A longitudinal study , 2014, Inf. Softw. Technol..

[4]  R. Hanneman Introduction to Social Network Methods , 2001 .

[5]  Sabrina Marczak,et al.  A systematic literature review on agile requirements engineering practices and challenges , 2015, Comput. Hum. Behav..

[6]  Sabrina Marczak,et al.  Studying relevant socio-technical aspects of requirements-driven collaboration in agile teams , 2013, 2013 3rd International Workshop on Empirical Requirements Engineering (EmpiRE).

[7]  Daniela E. Damian,et al.  Requirements-Driven Collaboration: Leveraging the Invisible Relationships between Requirements and People , 2010, Collaborative Software Engineering.

[8]  Daniela E. Damian,et al.  Awareness in the Wild: Why Communication Breakdowns Occur , 2007, International Conference on Global Software Engineering (ICGSE 2007).

[9]  Jon M. Kleinberg,et al.  The small-world phenomenon: an algorithmic perspective , 2000, STOC '00.

[10]  Daniela Cruzes,et al.  Interpretative case studies on agile team productivity and management , 2013, Inf. Softw. Technol..

[11]  Maya Daneva,et al.  Handling requirements dependencies in agile projects: A focus group with agile software development practitioners , 2013, IEEE 7th International Conference on Research Challenges in Information Science (RCIS).

[12]  Sabrina Marczak,et al.  Identifying and Reviewing the Most Relevant Socio-technical Aspects of Requirements-Driven Collaboration in Agile Teams , .

[13]  Pekka Abrahamsson,et al.  The impact of agile practices on communication in software development , 2008, Empirical Software Engineering.

[14]  Meghann L. Drury-Grogan Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors , 2014, Inf. Softw. Technol..

[15]  Helen Sharp,et al.  An ethnography of XP practice , 2003, PPIG.

[16]  James A. McHugh,et al.  Algorithmic Graph Theory , 1986 .

[17]  Helen Sharp,et al.  Organisational culture and XP: three case studies , 2005, Agile Development Conference (ADC'05).

[18]  Kate Ehrlich,et al.  The Impact of the Structure of Communication Patterns in Global Software Development : An Empirical Analysis of a Project Using Agile Methods , 2011 .

[19]  Juhani Iivari,et al.  The relationship between organizational culture and the deployment of agile methods , 2011, Inf. Softw. Technol..

[20]  Susan S. McElfish Identifying Cultural Changes Necessary in Traditional Plan-Driven Software Development Organizations when Preparing to Adopt Agile Principles , 2011 .

[21]  Björn Regnell,et al.  Overscoping: Reasons and consequences — A case study on decision making in software product management , 2010, 2010 Fourth International Workshop on Software Product Management.

[22]  Pearl Brereton,et al.  Protocol for a Tertiary study of Systematic Literature Reviews and Evidence-based Guidelines in IT and Software Engineering , 2009 .

[23]  Gitte Tjørnehøj,et al.  Trust in agile teams in distributed software development , 2012 .

[24]  Kate Ehrlich,et al.  Leveraging expertise in global software teams: Going outside boundaries , 2006, 2006 IEEE International Conference on Global Software Engineering (ICGSE'06).

[25]  Gino Cattani,et al.  A Core/Periphery Perspective on Individual Creative Performance: Social Networks and Cinematic Achievements in the Hollywood Film Industry , 2008, Organ. Sci..

[26]  L. Freeman,et al.  Centrality in social networks: ii. experimental results☆ , 1979 .

[27]  Alok Mishra,et al.  Strength of shoulder during one-handed pushing in constrained conditions , 2009 .

[28]  James D. Herbsleb,et al.  Communication networks in geographically distributed software development , 2008, CSCW.

[29]  Guillermo Owen,et al.  Centrality and power in social networks: a game theoretic approach , 2003, Math. Soc. Sci..

[30]  Jean Hartley,et al.  Case study research , 2004 .

[31]  Jessica L. Myers,et al.  Guidelines for performing systematic reviews in the development of toxicity factors , 2017, Regulatory toxicology and pharmacology : RTP.

[32]  Kieran Conboy,et al.  Agile Practices: The Impact on Trust in Software Project Teams , 2012, IEEE Software.

[33]  Seija Komi-Sirviö,et al.  Lessons learned by participants of distributed software development , 2005 .

[34]  Mark Summers Insights into an Agile Adventure with Offshore Partners , 2008, Agile 2008 Conference.

[35]  Stephen P. Borgatti,et al.  Identifying sets of key players in a social network , 2006, Comput. Math. Organ. Theory.

[36]  James D. Herbsleb,et al.  Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development , 2007, Organ. Sci..

[37]  Bashar Nuseibeh,et al.  Communication patterns of agile requirements engineering , 2011 .

[38]  James D. Herbsleb,et al.  Splitting the organization and integrating the code: Conway's law revisited , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[39]  Björn Regnell,et al.  Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[40]  A. Belianin,et al.  A Game-Theoretic Approach , 2001 .

[41]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[42]  Bruce Hoppe,et al.  Social network analysis and the evaluation of leadership networks , 2010 .

[43]  Raymond T. Sparrowe,et al.  Social Networks and the Performance of Individuals and Groups , 2001 .