Beyond Code: Leveraging Social Software to Bridge Global Development Gaps
13182_Social software in global software development.
This research explores the integration of "Social Software" (e.g., Wikis, Instant Messaging, Blogs) within Global Software Development (GSD) to foster team building. It frames social tools as essential infrastructure for maintaining informal communication and mutual awareness in geographically dispersed teams.
TL;DR
Global Software Development (GSD) often fails not because of bad code, but because of poor "social glue." This seminal paper from ICSE '10 argues that Social Software—tools like Wikis, blogs, and IM—is critical for building the trust and mutual awareness that physical distance destroys. By digitizing informal interactions, teams can maintain the social relationships necessary for technical success.
The "Awareness" Gap: Why Distance Kills Projects
In a traditional office, team building happens at the coffee machine. Developers share photos of their kids, discuss hobbies, or debate politics. These "informal ways" of connecting are not trivial; they build a foundation of trust and a shared understanding of work practices.
In Global Software Development (GSD), this layer of interaction is stripped away. The authors identify the lack of mutual awareness as a root cause of communication breakdowns. When you don't know who your colleagues are as people, it becomes significantly harder to coordinate complex technical tasks.
Methodology: Social Software as a Knowledge Repository
The authors propose that social software serves a dual purpose:
- Informal Communication Link: Providing digital spaces for non-work-related stories and personal expression.
- Unstructured Knowledge Repository: Capturing the "tacit" knowledge and behavioral patterns that formal documentation ignores.
The insight here is that Social Software creates a "Social Side" to software engineering. For instance, social bookmarking and Wikis allow for a bottom-up organization of knowledge that reflects the team's actual culture rather than a rigid management hierarchy.
Figure 1: The integration of social tools into the corporate context (Conceptual).
Evidence from the Field
The paper cites several emerging (at the time) trends in the industry:
- Wikis: Widely accepted for collaborative documentation.
- Instant Messaging (IM): Proved effective in global projects for quick, lightweight clarification.
- Social Bookmarking: Used in large-scale settings (like IBM) to support open-source-style knowledge sharing.
The authors hypothesize that these informal links lead to an "Alignment of Practices"—a state where distributed members naturally synchronize their work styles because they "know" each other, even without face-to-face contact.
Figure 2: The framework for investigating communication breakdowns via social software.
Critical Analysis & Conclusion
Takeaway
The core contribution of this work is the realization that technical coordination in GSD is a downstream effect of social healthy. Social software isn't just "leisure" software; it is a team-building infrastructure that acts as a prerequisite for professional cooperation.
Limitations
Published in 2010, the paper focuses on "Web 2.0" tools. It predates the explosion of dedicated platforms like Slack, Discord, or GitHub Discussions, and does not address the "noise" and "context switching" fatigue that modern social tools can cause.
Future Outlook
As we move into an era of AI-driven development, the "social" aspect may become even more vital. While AI can write code, it cannot (yet) build the cultural trust and alignment that Giuffrida and Dittrich argue is the backbone of global engineering success.