| Author Info |
| Abstract |
In this paper, I use coordination theory to analyze the software change process of a large mini-computer manufacturer and suggest alternative ways the dependences involved could be managed and thus alternative forms the process could take. Mechanisms analyzed include those for task assignment, resource sharing and managing dependences between modules of code. The organization studied assigned problem reports to engineers based on the module which appeared to be in error; engineers specialized in particular modules. The framework suggests alternative mechanisms including assignment to generalists based on workload or based on market-like bids. Modules of code were not shared, but rather "owned" by one engineer, thus reducing the need for coordination; a more elaborate code management system would be required if multiple engineers needed to work on the same modules. Finally, engineers managed dependences between modules informally, based on their personal knowledge of which other engineers used their code; alternatives include formally defining the interfaces between modules and tracking their users.
Software bug fixing provides a microcosm of coordination problems and solutions. Similar coordination problems arise in most processes and are managed by a similar range of mechanisms. For example, diagnosing but reports and assigning them to engineers may have interesting parallels to diagnosing patients and assigning them to specialists.
While the case presented does not formally test coordination theory, it does illustrate the potential of the coordination theory for exploring the space of organizational forms. Future work includes developing more rigorous techniques for such analyses, applying the techniques to a broader range of processes, identifying additional coordination problems and mechanisms and developing tools for collecting and comparing processes and perhaps automatically suggesting potential alternatives.
| Download Info |
If you experience problems downloading a file, check if you have the proper application to view it first. Information about this may be contained in the File-Format links below. In case of further problems read the IDEAS help page. Note that these files are not on the IDEAS site. Please be patient as the files may be large.
| Publisher Info |
Download reference. The following formats are available: HTML
(with abstract),
plain text
(with abstract),
BibTeX,
RIS (EndNote, RefMan, ProCite),
ReDIF
Contact details of provider:
Web page: http://ccs.mit.edu/wpmenu.html
For technical questions regarding this item, or to correct its listing, contact: (Thomas Krichel).
| Related research |
| Statistics |
Did you know? IDEAS is not the only service displaying RePEc data. Choose on RePEc which service fits your needs best.
This page was last updated on 2009-12-28.