The Matrix of Control: Combining Process and Structure Approaches to Managing Software Development
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
The performance of firms in the software industry depends considerably on the quality of their software development processes. Managing software development is a challenging task, as management controls need to impose discipline and coordinate action to ensure goals are met while simultaneously incorporating autonomy to motivate software developers to be innovative and produce quality work. How should such firms manage software development projects so that their development processes are flexible and predictable--resulting in products that meet quality goals and that are delivered within budget and on time? The management literature suggests two approaches to control: the process approach and the structure approach. The process approach recommends control of activities through specifying methods (behavior control) and through specifying performance criteria (outcome control). In contrast, the structure approach recommends control through centrally devised standards for activities (standardization) and by the delegation of authority for decision-making (decentralization). This study synthesizes these two approaches to suggest that formal managerial control is exerted through a matrix of control comprising four modes: standardization of methods, standardization of performance criteria, decentralization of methods, and decentralization of performance criteria. We test the association of the modes of control with performance in a sample of 56 firms in the software industry in the United States. The results suggest that performance is enhanced by establishing uniform performance criteria across projects (standardization of performance criteria) while giving each project team the authority to make decisions with respect to methods (decentralization of methods). However, standardization of methods across all projects and decentralization of performance criteria by delegating the authority to make decisions about performance criteria to project teams were both not significantly related to performance. The matrix of control and its relationship to performance has theoretical and practical implications for managing software development. This model of control is also likely to be useful in other knowledge-work-intensive settings.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Information Systems Success: The Quest for the Dependent Variable
DeLone, W. H., & McLean, E. R. (1992) · Information Systems Research · doi:10.1287/isre.3.1.60 · Cited by 10,697
Product development: Past research, present findings and future directions
Brown, S. L., & Eisenhardt, K. M. (1995) · The Academy of Management Review · doi:10.2307/258850 · Cited by 3,777 · cited 1×
“An important assumption we make, drawing on the literature and accounts in the popular press [9, 15], is that the software industry is characterized by high levels of environmental uncertainty.”
BackgroundTightening the Iron Cage: Concertive Control in Self-Managing Teams
Barker, J. R. (1993) · Administrative Science Quarterly · doi:10.2307/2393374 · Cited by 2,305
Determinants of Coordination Modes within Organizations
Ven, A. H. V. D., Delbecq, A. L., & Koenig, R. (1976) · American Sociological Review · doi:10.2307/2094477 · Cited by 1,979
Explaining the Role of User Participation in Information System Use
Hartwick, J., & Barki, H. (1994) · Management Science · doi:10.1287/mnsc.40.4.440 · Cited by 1,540
Cited by
Six Sigma: Definition and underlying theory⋆
Schroeder, R. G., Linderman, K., Liedtke, C., & Choo, A. S. (2008) · Journal of Operations Management · doi:10.1016/j.jom.2007.06.007 · Cited by 868
Expertise Integration and Creativity in Information Systems Development
TIWANA, A., & MCLEAN, E. R. (2005) · Journal of Management Information Systems · doi:10.1080/07421222.2003.11045836 · Cited by 598
Deploying Common Systems Globally: The Dynamics of Control
Kirsch, L. J. (2004) · Information Systems Research · doi:10.1287/isre.1040.0036 · Cited by 406
If someone is watching, I'll do what I'm asked: mandatoriness, control, and information security
Boss, S. R., Kirsch, L. J., Angermeier, I., Shingler, R. A., & Boss, R. W. (2009) · European Journal of Information Systems · doi:10.1057/ejis.2009.8 · Cited by 403
Lean principles, learning, and knowledge work: Evidence from a software services provider
Staats, B. R., Brunner, D. J., & Upton, D. M. (2011) · Journal of Operations Management · doi:10.1016/j.jom.2010.11.005 · Cited by 390
Metadata
- Authors
- NIDUMOLU, S. R., & SUBRAMANI, M. R.
- Venue
- Journal of Management Information Systems
- Publisher
- Informa UK Limited
- Published
- 2003-12
- Volume
- 20
- Issue
- 3
- Pages
- 159-196
- ISSN
- 0742-1222 (ISSN-L)
- 1557-928X
- OpenAlex
- W1573203150
- Cited by
- 155
- References
- 5
- FWCI
- 10.58
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: The Matrix of Control: Combining Process and Structure Approaches to Managing Software Development. https://app.cochat.ai/papers/10.1080/07421222.2003.11045774
- The paper
- NIDUMOLU, S. R., & SUBRAMANI, M. R. (2003). The Matrix of Control: Combining Process and Structure Approaches to Managing Software Development. Journal of Management Information Systems. https://doi.org/10.1080/07421222.2003.11045774
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.