The Case of Distributed Software Problem Management
Total Page:16
File Type:pdf, Size:1020Kb
INFORMATION, ACTIVITY AND SOCIAL ORDER IN DISTRIBUTED WORK: THE CASE OF DISTRIBUTED SOFTWARE PROBLEM MANAGEMENT Robert John Sandusky, Ph.D. Graduate School of Library and Information Science University of Illinois at Urbana-Champaign, 2005 Les Gasser, Advisor Results from a study of a global Free / Open Source Software (F/OSS) development organization show how distributed information practices contribute to the management of software problems. The study addressed these questions: (1) How do F/OSS development communities manage software problems? (2) What varieties of information and activity occur as part of software problem management? And (3) How are information, activity, and social order related in software problem management? A systematic random sample of 385 bug reports was drawn from a collection more than 182,000 bug reports held in this community’s bug report repository, with additional bug reports selected from the repository using theoretical sampling. The bug reports were treated as texts; content analytic and grounded theory procedures were used to develop categories of phenomena and new and revised theoretical constructs. The analysis of the data was informed by previous research into human information behavior, negotiation, collaboration, social and information contexts, software engineering, and sensemaking to provide insights into how this large, distributed organization utilizes information to produce successful, high-quality software. Contributions from this project include the first detailed, empirically grounded description of the information practices used by a distributed F/OSS development organization to manage software problems, including the first description of a fundamental information object, the bug report network; clearly drawn distinctions between the information management work necessary to support the community’s software problem management goals and the work that directly resolves software problems; identification of the processes and social arrangements that enable this community’s distributed collective software problem management practices; explication of software problem management as a distributed, communal sensemaking enterprise; description of the layers of context and nested processes necessary to support distributed, information-intensive work; and the description of a new class of human information behavior, distributed collective information practices. Throughout, the ways in which information, activity, social order, context, and process are mutually constitutive are identified and explained. Bug report networks are used as a primary example of how activity leads to new forms of information, re-orders existing information, affects social order, and contributes to the community’s efforts to bring problematic situations to closure. © 2005 by Robert John Sandusky. All rights reserved. INFORMATION, ACTIVITY AND SOCIAL ORDER IN DISTRIBUTED WORK: THE CASE OF DISTRIBUTED SOFTWARE PROBLEM MANAGEMENT BY ROBERT JOHN SANDUSKY B.A., Northern Illinois University, 1979 M.S., Northern Illinois University, 1983 DISSERTATION Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Library and Information Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2005 Urbana, Illinois ABSTRACT Results from a study of a global Free / Open Source Software (F/OSS) development organization show how distributed information practices contribute to the management of software problems. The study addressed these questions: (1) How do F/OSS development communities manage software problems? (2) What varieties of information and activity occur as part of software problem management? And (3) How are information, activity, and social order related in software problem management? A systematic random sample of 385 bug reports was drawn from a collection more than 182,000 bug reports held in this community’s bug report repository, with additional bug reports selected from the repository using theoretical sampling. The bug reports were treated as texts; content analytic and grounded theory procedures were used to develop categories of phenomena and new and revised theoretical constructs. The analysis of the data was informed by previous research into human information behavior, negotiation, collaboration, social and information contexts, software engineering, and sensemaking to provide insights into how this large, distributed organization utilizes information to produce successful, high-quality software. Contributions from this project include the first detailed, empirically grounded description of the information practices used by a distributed F/OSS development organization to manage software problems, including the first description of a fundamental information object, the bug report network; clearly drawn distinctions between the information management work necessary to support the community’s software problem management goals and the work that directly resolves software problems; identification of the processes and social arrangements that enable this community’s distributed collective software problem management practices; explication of software problem management as a distributed, communal sensemaking enterprise; description of the layers of context and nested processes necessary to support distributed, information-intensive work; and the description of a new class of human information behavior, distributed collective information practices. Throughout, the ways in which iii information, activity, social order, context, and process are mutually constitutive are identified and explained. Bug report networks are used as a primary example of how activity leads to new forms of information, re-orders existing information, affects social order, and contributes to the community’s efforts to bring problematic situations to closure. iv To my family v ACKNOWLEDGEMENTS This project would not have been possible without the support and encouragement of many people: my family, my friends, and my colleagues in the Graduate School of Library and Information Science. Lora, Charlie, and Kiera have supported me in every way throughout the process, being willing and eager to try new cities, schools, and circumstances. We have held together despite my distraction and absences from their life. This dissertation is in many ways theirs as well as mine. My mother and father continuously encouraged me and supported me throughout my academic and professional careers, for which I am grateful. Les Gasser, Geof Bowker, Mike Twidale, and Walt Scacchi, my committee members, were instrumental in helping me see this project through to completion. Geof Bowker, my advisor during the early years, was unfailingly enthusiastic which gave me boosts of confidence at many critical points. Les Gasser, my advisor throughout my dissertation phase, provided me with the opportunity to pursue this project which was a perfect fit with my background and interests. Both Geof and Les provided encouragement, ideas, challenges, and support throughout. Other people at the Graduate School of Library and Information Science and in other parts of the University who made a difference for me include Leigh Estabrook, Linda Smith, Leigh Star, Patricia Jones (Mechanical and Industrial Engineering), Chip Bruce, Karen Ruhleder, Bruce Schatz, and my fellow students Gabriel Ripoche, Kevin Powell, Laura Neumann, Cece Merkel, and Emily Ignacio. Finally, I thank Ann Peterson Bishop, who, in addition to being my mentor during the Digital Library Initiative days, was my friend and my coach throughout the hardest parts of the process. Some of the data collection, analysis, and presentation activities upon which this material is based were supported by the National Science Foundation ITR (Digital Society and Technologies) Program under Grant No. 0205346. Any opinions, findings, v i and conclusions or recommendations expressed in this material are those of the author and do not necessarily reflect the views of the National Science Foundation. v ii TABLE OF CONTENTS LIST OF TABLES....................................................................................................................................xii LIST OF FIGURES................................................................................................................................xiii CHAPTER ONE: INTRODUCTION................................................................................................1 Software Problems and Software Problem Management.............................................................4 Impact of Software Problems.....................................................................................................4 The Software Problem Management Process..........................................................................9 Problem Statement............................................................................................................................ 15 Research Questions........................................................................................................................... 18 Research Approach........................................................................................................................... 21 Benefits of the Research .................................................................................................................. 23 CHAPTER TWO: LITERATURE REVIEW ................................................................................. 26 Introduction