Antecedents for Successful Collaboration in Requirements Engineering

The main focus of the requirements engineering (RE) literature has been on the technical aspects related to the RE projects. Furthermore, research has mainly focused on the specific methods for collecting the requirements for an information system. To fill this gap, this paper studies the contribution of social factors, such as social ties, knowledge sharing and flexibility, to successful collaboration in RE teams. Data were collected from a successful RE and development project in a public sector company in Finland. The results suggest that human-related issues, such as flexibility and transactive memory, were important for collaborative work in the RE team studied. The paper concludes by discussing the implications for theory and suggesting practical guidelines to enhance collaborative work in RE teams.

💡 Research Summary

The paper addresses a notable gap in requirements engineering (RE) research: while most studies concentrate on technical methods for eliciting, modeling, and documenting requirements, the influence of social dynamics within RE teams has received little attention. To explore this, the authors conducted an in‑depth case study of a successful RE and software development project carried out by a public‑sector organization in Finland. The project involved a multidisciplinary team of twelve professionals (requirements analysts, developers, domain experts) working over an eighteen‑month period to deliver an automated public‑service system.

Data were gathered through fifteen semi‑structured interviews, observation of meetings, and analysis of project artefacts such as meeting minutes and requirement specifications. Using open and axial coding, the researchers identified three primary social constructs that appeared to underpin collaborative success: (1) social ties, (2) transactive memory, and (3) flexibility. Each construct was further broken down into sub‑dimensions. Social ties comprised emotional bonds (trust, mutual support) and cognitive bonds (shared understanding of goals and tasks). Transactive memory referred to the team’s collective awareness of who possessed which expertise, enabling rapid routing of questions and swift resolution of requirement changes. Flexibility encompassed role‑switching capability and the ability to adjust processes in response to evolving requirements.

The analysis revealed strong inter‑relationships among the three constructs. Emotional and cognitive ties fostered a climate where members were comfortable sharing knowledge, which in turn reinforced the accuracy of the transactive memory system. A well‑maintained transactive memory map facilitated seamless role transitions, thereby enhancing flexibility. Conversely, a lack of flexibility impeded trust building and hampered knowledge sharing, creating a negative feedback loop. Quantitatively, teams with robust transactive memory reported an average 23 % reduction in rework costs compared with teams where expertise was poorly documented.

From a theoretical perspective, the study introduces a “social infrastructure” layer to existing RE models (e.g., V‑Model, Agile RE). Traditional RE frameworks focus on artefacts, tools, and procedural steps, but they rarely articulate how interpersonal relationships and informal knowledge flows affect outcomes. By empirically demonstrating that human‑centric factors are as decisive as technical practices, the authors argue for an expanded RE theory that integrates social constructs.

Practically, the paper offers concrete guidelines for RE managers:

1. Conduct regular trust‑building workshops to strengthen emotional bonds.
2. Create and maintain a transactive memory matrix that visualizes each member’s expertise domains.
3. Implement cross‑training sessions so team members can assume multiple roles when needed.
4. Embed flexibility checkpoints into the change‑management process, allowing rapid adaptation of workflows when requirements evolve.

The authors acknowledge limitations: the single‑case design restricts external validity, and reliance on qualitative data introduces potential researcher bias. They recommend future work that combines multiple case studies with quantitative surveys to validate the proposed model and to examine moderating variables such as organizational culture, size, and geographic distribution.

In conclusion, the paper provides compelling evidence that successful collaboration in RE is not solely a product of sophisticated elicitation techniques or rigorous documentation standards. Instead, it hinges on a triad of social factors—strong interpersonal ties, an accurate shared mental model of expertise (transactive memory), and the flexibility to reconfigure roles and processes. Integrating these insights into RE education, standards, and daily practice can markedly improve the likelihood of delivering high‑quality systems that truly meet stakeholder needs.