[Paper Review] FLOW-Methode - Methodenbeschreibung zur Anwendung von FLOW

Kai Stapel, Kurt Schneider|arXiv (Cornell University)|Feb 27, 2012

Business Process Modeling and Analysis10 references4 citations

TL;DR

The FLOW-Methode proposes a methodology for modeling information and experience flows in software projects, independent of development methodology (agile or traditional). It emphasizes timely and accurate routing of requirements, design decisions, and tacit knowledge, addressing the critical issue that much valuable experience remains undocumented. The key contribution is a unified framework for visualizing and managing flow dynamics across diverse project contexts.

ABSTRACT

Information of many kinds is flowing in software projects and organizations. Requirements have to flow from the customer to the developers. Testers need to know the requirements as well. Boundary conditions and design decisions have to be at the right place at the right time. Information flow analysis with FLOW facilitates modeling of mode and route of the flow of information and experience independent of the development methodology. Experience often acts as a control factor, because experienced developers can process and route information more efficiently. Therefore, experience needs to be at the right place at the right time, too. However, most valuable experiences never get documented. Since information and experience is flowing in agile as well as in traditional environments, the FLOW method does not distinguish between agile and traditional, but only between how the flows are shaped. ---- In Softwareprojekten fließen vielerlei Informationen. Anforderungen müssen vom Kunden zu den Entwicklern gelangen. Auch Tester müssen die Anforderungen kennen. Randbedingungen und Entwurfsentscheidungen müssen zur rechten Zeit am rechten Ort sein. Die Informationsflussanalyse mit FLOW ermöglicht es, unabhängig von der Entwicklungsmethode zu modellieren, wie und auf welchem Wege Informationen und Erfahrungen fließen. Erfahrungen spielen dabei oft die Rolle von Steuergrößen, denn erfahrene Mitarbeiter können Informationen kompetenter bearbeiten und weiterleiten. Auch die Erfahrungen müssen in geeigneter Form zur rechten Zeit am rechten Ort sein. Viele Erfahrungen werden aber nie dokumentiert. Da Informationen und Erfahrungen sowohl in agilen als auch in traditionellen Umgebungen fließen müssen, wird in FLOW ein Modell aufgebaut, das nicht nach agil, traditionell oder anderen Bezeichnungen unterscheidet, sondern einzig danach, wie die Flüsse gestaltet sind.

Motivation & Objective

• To address the challenge of inefficient and undocumented information and experience flows in software development.
• To develop a methodology that is independent of specific development methodologies (agile or traditional), focusing solely on flow characteristics.
• To ensure that critical information and experienced knowledge reach the right people at the right time.
• To model how information and experience flow through teams, with a focus on control factors like experienced developers.
• To provide a practical framework for organizations to improve communication and knowledge transfer in software projects.

Proposed method

• The FLOW-Methode uses a flow modeling approach to represent the movement of information and experience through software projects.
• It distinguishes between different types of flows: requirements, design decisions, boundary conditions, and tacit experience.
• The method is based on identifying flow sources, targets, and routes, independent of the underlying development methodology.
• It incorporates the role of experienced individuals as key control factors in routing and processing information efficiently.
• The framework supports visualization of flow paths, enabling teams to analyze and optimize information distribution.
• It is designed to be applied in both agile and traditional software development environments without methodological bias.

Experimental results

Research questions

• RQ1 How can information and experience flows be modeled independently of the underlying software development methodology?
• RQ2 What role do experienced developers play in controlling and optimizing information flow in software projects?
• RQ3 Why is undocumented experience a critical bottleneck in software development, and how can it be systematically addressed?
• RQ4 How can the timing and location of information delivery be ensured to improve project outcomes?
• RQ5 What are the key structural and behavioral characteristics of effective information and experience flows in software projects?

Key findings

• The FLOW-Methode successfully models information and experience flows without dependency on agile or traditional methodologies.
• Experienced developers act as critical control factors, significantly improving the efficiency and accuracy of information routing.
• A substantial portion of valuable experience remains undocumented, creating a major gap in knowledge transfer.
• The method enables organizations to visualize and analyze flow patterns, identifying bottlenecks and inefficiencies.
• The framework supports improved alignment of information delivery with project needs, enhancing team coordination.
• The approach is applicable across diverse project contexts, demonstrating flexibility and scalability in real-world settings.