Contracting in software business

Analysis of evolving contract processes and relationships

Juhani Warsta

Department of Information Processing Science, University of Oulu

Abstract

The relationships between software producing companies, their customers and other parties involved have growing importance in the turbulent and fast developing business environment of today. The software industry itself is characterized by the Commercial-Off-The-Shelf (COTS), tailored, and Modified-Off-The-Shelf (MOTS) businesses modes. In this versatile context of cooperation, financing and acquisitions demand exact details of the ownership of the products, i.e. the Intellectual Property Rights of these products and services. Legal forms and contracting procedures are emerging as the critical issues for the development of the information technology industry.

This study addresses the problem of how software contracting has been approached and what concepts and models have been presented to understand it. Further, the question of the role of inter-organisational relationships (business-to-business) and intra-organisational process evolution in software contracting is discussed. The domains of interest and of relevance in this research are software development process, business process, legal process, and the contracting process itself, and the evolving interaction between these processes. The focus of this study is especially on contracting and on analysing the process of contracting, i.e. the dynamics, dependencies and elements of process related issues.

The empirical part of the study was completed by analysing twelve software producing companies - eight were Finnish firms established in Silicon Valley (USA) and the rest were local Finnish firms with international operations. Based on the empirical findings, a software-contracting model was elaborated to describe how the contracting processes form and evolve in the context of software business. The model gives more understanding of the evolving contract processes and relationships. Further, the research produced concepts of how to manage contracting processes in the software business.

Contributions of this study are, first, the well-defined model for contracting process in a software developing company. The elaborated model gives new insight into the elements, interrelationships and governance structures included in the contracting process and the relationship development between cooperating companies. Software companies can compare their contractual situation with the model. This enables them to develop their own processes further to respond to the present-day requirements. Secondly, the study specifies and introduces three different generic contracting networks for COTS, tailored, and MOTS business modes of software developing companies. It was established that these three business modes have similarities as well as differences in the application of software contracting processes. The COTS business relied firmly on multiform licensing practices, whereas the tailored business saw the framework contract as the main contractual tool and interestingly the MOTS business employed combinations of these two previous forms, i.e. both licensing and framework contracts.

This study evoked some interesting future research prospects. In order to create a more accurate overall view of the whole contracting process the research should be continued and take the interplay of both customer and supplier under closer scrutiny. Another important issue would be to examine the contracts used in these different business modes from a strict legal viewpoint and the possible transformation of the predominant legal practices.


Table of Contents
Preface
Abbreviations
1. Introduction
1.1. Research problem
1.2. Contributions
1.3. Structure of the dissertation
2. Contracting in software business
2.1. Contracting
2.1.1. Economics of contracting
2.1.2. Types of Contracts
2.1.3. Procurement and contract negotiations
2.2. Software business
2.2.1. Software business modes
2.2.2. Software development practices
2.3. Software contracting
2.3.1. Software development contracts
2.3.2. Software contract templates
2.3.3. Customer perspective – software acquisition standards
2.4. Summary
3. Process and relationship approach
3.1. Rationale of the process approach
3.1.1. Process definitions
3.1.2. Process characteristics
3.1.3. Process theory classification
3.2. Business processes and relationships
3.2.1. Business relationships
3.2.2. The features of relationships
3.2.3. The interdependencies of relationships
3.3. Processual relationship development models
3.3.1. Interaction process model
3.3.2. Customer-supplier relationship models
3.3.3. Formation of entrepreneurial dyads
3.4. Summary
4. Software contracting model
4.1. Software development and contracting interaction processes
4.1.1. Negotiation phase
4.1.2. Definition phase
4.1.3. Production phase
4.1.4. Assessment phase
4.2. Process breakdown structure
4.3. Elements of the software contracting process model
4.3.1. Supplier context
4.3.2. Customer context
4.3.3. Prerequisites and formation of relationship
4.3.4. Interaction processes
4.3.5. Output of interaction processes
4.3.6. Dissolution of the relationship
4.4. Processual dynamism included in the model
4.5. Summary
5. Empirical research design
5.1. Process research
5.2. Research methodology
5.2.1. Getting started
5.2.2. Selecting cases
5.2.3. Crafting instruments and protocols
5.2.4. Entering the field
5.2.5. Analysing data
5.2.6. Shaping hypotheses
5.2.7. Enfolding literature
5.2.8. Reaching closure
5.3. Reliability and validity of the study
5.4. Summary
6. Analysis of software contracting relationships and processes
6.1. Background for the analysis
6.2. Supplier and customer context
6.2.1. Environmental factors
6.2.2. Supplier and task characteristics
6.2.3. Organizational characteristics
6.3. Prerequisites and formation of relationship
6.3.1. Complementary needs and resources between parties
6.3.2. Personal awareness of the other party’s goals, needs and resources
6.3.3. Common interest in building a relationship
6.3.4. Formation stage of partnership development
6.4. Interaction processes and their outputs
6.4.1. Phases
6.4.2. Interaction processes
6.4.3. Used approach
6.4.4. COTS business relationship development
6.4.5. Tailored-software business relationship development
6.4.6. MOTS business relationship development
6.4.7. Other contracting issues
6.5. Dissolution of the relationship
6.5.1. Predisposing factors
6.5.2. Precipitating events
6.5.3. Attenuating factors
6.6. The relationship development
6.6.1. Change of stages
6.6.2. Analysis of the developing stage
6.6.3. Conclusions
6.7. Summary
7. Towards an evolutionary software contracting process
7.1. Contracts and their role in software business modes
7.2. Observations of process attributes and typologies
7.2.1. Process attributes
7.2.2. Process typologies
7.3. Advanced software contracting process model
7.3.1. Conceptual model
7.3.2. Augmented contractual model
7.3.3. Extended contracting process life cycle
7.4. Summary
8. Theoretical, empirical and managerial implications
8.1. Theoretical implications
8.1.1. Dyadic Interaction Model
8.1.2. Buyer-seller relationship development model
8.1.3. Change of process modes
8.1.4. Contract law issues
8.2. Empirical implications
8.3. Managerial implications
8.3.1. Business perspective
8.3.2. Contractual perspective
8.4. Summary
9. Conclusions
9.1. Research results and contributions
9.2. Limitations of the study
9.3. Recommendation for future research
References
A. List of interview topics and examples of interview questions
B. The process activity distribution.
C. List of software companies interviewed
D. Process activity descriptions
E. Development stage activities.
H. Software company without contracts, Case company H.
I. An example of Visual mapping strategy used to describe and analyse the cases.
List of Tables
1. A typology of governance structures (Ring & Van de Ven 1992, 490).
2. Common contract types (Warberg 1997, 16).
3. Arguments for and against licensing (Nooteboom 1999, 61).
4. Impact of process focus (Zahran 1998, 10).
5. Families of Ideal-Type Theories of Social change (Van de Ven & Poole 1995, 514).
6. Process of building theory from case study research (Eisenhardt 1989, 533).
7. Seven strategies for sensemaking (Langley 1999, 696).
8. The identification of elements needed to begin the formation stage of partnership development (Lappi 2001, 67).
9. Process activities observed in terms of software development phases and relationship development stage, percentual distribution.
10. Contractual characterisation of the three modes of software businesses.
11. Distribution of contracts.
12. Numerical characterizations of license contracts in Finland and the USA.
13. Process activities observed in terms of software contracting phases and process typology.
14. Instances observed in terms of relationship development stages and process typology.
15. Conditions for Operation of Change Theories, augmented with the right hand column (Van de Ven & Poole 1995, 525).
16. Distribution of process activities over the processes.
17. Comparison between the main phases of the ABC model and the NTNU model.
18. Distribution of the software development phases over stages.
19. Comparison between bad and good contract (Kilde 1998, 68).
20. Comparison of software business modes, augmented (italics) from (Alajoutsijärvi, Mannermaa et al. 1998) and (Tähtinen 1999, 21).
D-1. Process activity descriptions, Case A. [Channel and project business: COTS and MOTS]
D-2. Process activity descriptions, Case B. [Product and project business: COTS, ­Tailored and MOTS]
D-3. Process activity descriptions, Case C. [Product business: COTS]
D-4. Process activity descriptions, Case D. [Product and project business: MOTS]
D-5. TProcess activity descriptions, Case E. [Product business: COTS]
D-6. Process activity descriptions, Case F. [Project business: Tailored]
D-7. Process activity descriptions, Case G. [Product business: COTS]
D-8. Process activity descriptions, Case I. [Project business: Tailored]
D-9. Process activity descriptions, Case J. [Product business: COTS]
D-10. Table K. Process activity descriptions, Case K. [Channel and project business: COTS and MOTS]
D-11. Process activity descriptions, Case L. [Project business: Tailored]
D-12. Compacted process activities used in Excel-calculations, cases A - L.
List of Figures
1. Wealth formation in nexus of ownership, contract and indemnity (Pöyhönen 2000, 15).
2. Efficient governance (Williamson 1985, 79).
3. Gradual Forming of Contract by Grönfors in (Nystén-Haarala 1998, 113).
4. The Traditional Model for the Formation of Contracts through Negotiations (Nystén-Haarala 1998, 96).
5. The generic waterfall model of the software life cycle.
6. Spiral model adapted for the entire life cycle (Pressman 1997, 44).
7. A conceptual presentation of the flexible approach (Iansiti & MacCormack 1997, 110).
8. Competitive Acquisition (Marciniak & Reifer 1990, 53).
9. Project management"s central domains and the contract"s role in context of software company (Kilde 1998, 17).
10. NTNU model for implementation of software development project (Kilde 1999, 11).
11. Activities between the licensor, dealer and customer (Siira 1998, 59).
12. The organization of tailored software development projects (Tähtinen 1999, 30).
13. Transformation process model (Armistead, Harrison et al. 1996, 118).
14. Business process breakdown structure (Armistead, Harrison et al. 1996, 121).
15. Life cycle theory (Van de Ven & Poole 1995, 520).
16. Evolution theory (Van de Ven & Poole 1995, 520).
17. Dialectic theory (Van de Ven & Poole 1995, 520).
18. Teleological theory (Van de Ven & Poole 1995, 520).
19. An expanded process (Davies 1996, 223).
20. Core features of relationships (Holmlund & Törnroos 1997, 305).
21. Möller and Wilson Dyadic Interaction Model (1995b, 35).
22. Process framework of the development of cooperative interorganizational relationships (Ring & Van de Ven 1994, 97).
23. The development of buyer-seller relationships in business markets (Ford, Gadde et al. 1998, 29).
24. Combined software development and contracting interaction phases.
25. Software contracting process breakdown structure.
26. The conceptual software contracting process model.
27. The factors affecting the dissolution process (Tähtinen 1999, 113).
28. Processing of interview data from analysis to synthesis, (Hirsjärvi & Hurme 2000, 144).
29. Contract network and contract related issues in a COTS business relationship development.
30. Contract network and contract related issues in tailored software business relationship development.
31. An outline of one defined contracting process in a tailored software supplier"s internal environment according to the ISO inspection model used.
32. Unfolding of the assignment and order contract drafting.
33. Contract network and contract related issues in MOTS business relationship development.
34. Typical contractual structure in a software company.
35. Modification of interaction processes.
36. Augmented basic contractual model, ABC model.
37. The development of the software contracting process over time, the D-ABC model.