FLOW Mapping: Planning and Managing Communication in Distributed Teams
Kai Stapel, Eric Knauss, Kurt Schneider, Nico Zazworka

TL;DR
FLOW Mapping is a systematic approach designed to improve communication planning and management in distributed software development projects, addressing challenges beyond traditional artifacts.
Contribution
The paper introduces FLOW Mapping, a novel method for planning and managing information flows in distributed projects, demonstrated through a case study.
Findings
Effective communication planning facilitates project success.
FLOW Mapping enables measurement of conformance to communication strategies.
The approach is feasible and beneficial in distributed agile settings.
Abstract
Distributed software development is more difficult than co-located software development. One of the main reasons is that communication is more difficult in distributed settings. Defined processes and artifacts help, but cannot cover all information needs. Not communicating important project information, decisions and rationales can result in duplicate or extra work, delays or even project failure. Planning and managing a distributed project from an information flow perspective helps to facilitate available communication channels right from the start - beyond the documents and artifacts which are defined for a given development process. In this paper we propose FLOW Mapping, a systematic approach for planning and managing information flows in distributed projects. We demonstrate the feasibility of our approach with a case study in a distributed agile class room project. FLOW Mapping is…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
