Search results

This paper aims to investigate the relationship of software company culture and core values and project management methodologies on the demand for corporate real estate (CRE), impacting decisions regarding location, square footage, office design and amenities.

A researcher-administered survey was designed with the assistance of a purposive sample of brokers, architects and interior designers to elicit responses from the CRE officers in software companies at four stages of growth, from small, entrepreneurial startups to large, publicly traded software companies, located in the same metropolitan area of the USA. Quantitative responses are summarized with traditional statistics and data visualizations. Linguistic analysis, including sentiment analysis and keyword relevance, was performed on the unstructured, English text responses.

Differences exist in the office layouts, amenities and locations across the four software company size categories studied. Linguistic analysis of company descriptions of office design, culture and core values, and the relationship between the two, provide another way for brokers, investors and other stakeholders to understand company perspectives and communication idioms related to CRE needs. The research was unable to show any differences in any dependent variable based on software project management methodologies due to sampling limitations.

This study is limited by the sample size of the participating software companies based on access to company leadership. Results are not generalizable.

Architects, investors, brokers and lenders may find value in using this study’s approach to better understand the needs of software technology clients. Specifically, stakeholders may find value in examining the linkage from software company size, culture and core values to CRE office layout, amenities and location.

The qualitative findings suggest that software company culture and core values and company size influence the design of the CRE demanded by software companies. Multivariate data visualization was designed to communicate longitudinal CRE data. Linguistic analysis was used to extract the emotional content and relevance scores from company descriptions of office design, company culture and core values and the reported effect of culture and core values on office design. Findings may be beneficial for stakeholders involved in the design, location and future CRE investments, and they suggest the need for future research on a larger sample.

This paper reports on the results of an investigation into how the software development process is initially established within software product start‐ups.

The study employs a grounded theory approach to characterize the experiences of small software organizations in developing processes to support their software development activity. Using the indigenous Irish software product industry as a test‐bed, the authors' examine how software development processes are established in software product start‐ups and the major factors that influence the make up of these processes.

The results show that the previous experience of the person tasked with managing the development work is the prime influencer on the process a company initially uses. Other influencers include the market sector in which the company is operating, the style of management used and the size and scale of the company operations.

The model has particular implications for start‐up software product organisations that wish to successfully manage their product development from an early stage.

The purpose of this article is to examine why US companies outsource software development offshore and to present the factors to be considered to determine if the benefits of offshore outsourcing outweigh the drawbacks. Is offshoring worth it in terms of cost savings and quality? What are the risks associated with offshoring software development, and how can you hedge against such risks? What types of software should be considered for offshoring? How can you recognize the danger signs of offshore work going awry? Are there alternatives to outsourcing software development offshore, or are there alternative ways to offshore? Offshore outsourcing of software development may not be worth the risk in all cases. However, in the cases that it is worth moving offshore, this paper makes suggestions about how to help ensure success. This article presents advantages, disadvantages, risks and alternatives to offshore outsourcing of software development. Also, it provides alternatives for offshore outsourcing that will be useful for any company or individual considering offshore outsourcing.

The purpose of this paper is to contribute to the literature about the commercial involvement in open source software, levels of this involvement and consequences of attempting to mix various logics of action.

This paper uses the case study approach based on mixed methods: literature reviews and news searches, electronic surveys, qualitative interviews and observations. It combines discussions from several research projects as well as previous publications to present the scope of commercial choices within open source software and their consequences.

The findings show that higher levels of involvement in open source software communities poses important questions about the balance between economic, technological, and social logics as well as the benefits of being autonomous, having access to collaborative networks and minimizing risks related to free-riding. There are six levels of commercial involvement in open source communities, and each of them is characterized by a different dilemma.

The paper sheds light on the various level of involvement of business in open source movement and emphasize that the popularized “open innovation” concept is only the first step in real involvement and paradigm shift.

The purpose of this paper is to address the need of a reengineering of the software development process in a Mexican technology services company. In general, the main risk faced by small- and medium-sized software developers (SMEs) is the inability to meet delivery times or to adjust to project requirements, whether through lack of follow-up on the critical activities of the development process or through an inadequate distribution of workloads among members of the project team.

The methodology used to carry out the reengineering of the software development process is Hammer and Champy, which consists of six stages: introduction to the current situation of the company and the need for change; identification of the business processes; selection of the business process to be redesigned; understanding of the process selected; proposal for reengineering the business process selected; and the results of the comparison between the current situation of the process and the proposed reengineering of the process through the use of Business Process Model and Notation (BPMN 2.0).

Based on the results, the paper shows the importance of the analysis and implementation of the reengineering in a software development company. It describes step-by-step how to apply the methodology of Hammer and Champy in a business process through simulated scenarios, using BPMN 2.0. By carrying out the implementation of the proposed reengineering, the company would therefore save 45.12 percent of costs, 41.17 percent of time, and a better distribution of resources, at the same time guaranteeing the satisfaction of its clients.

The study addresses the current needs of small- and medium-sized software developers, providing a step-by-step guide to the implementation of a process reengineering methodology, performing an analysis and modeling of processes in BPMN 2.0 and providing results through a simulation of the critical process, with the aim to observe the flow of activities and the significant improvements that would be achieved by implementing the reengineering proposal. This simulation schema allows business owners to observe the potential of the changes and to verify the positive impact they would have on the company before beginning to make operational changes in the organization.

How are institutional logics transgressed in the organizational fields of open source software and of commercial proprietary software, respectively, by developing a new practice of commercial open source software? I argue that by combining a Critique of Ideology Critique and a Critique of New Institutional Organizational Theory, we become better equipped for understanding institutional change in organizations applying concepts such as institutional entrepreneurs, discursive devices, and meaning arenas. The analysis show that many institutional entrepreneurs apply discursive devices to convince actors in the two organizational fields of the legitimacy of the new practice. This happens in many different meaning arenas such as in the market, in the public discourse, and in concrete open source projects. I advance the assumption that a relation established between institutional entrepreneurs of different legitimacy in the two original fields renders possible their institutional work.

The purpose of this paper is to develop and evaluate a concise framework to examine how global software companies with successful knowledge management (KM) programs create KM‐enabled value.

The framework was evaluated at three global software companies with successful KM programs. Data were generated based on 20 interviews with various individuals involved with the KM programs of three companies. Interviews were content analyzed by four coders who sorted the data into meaningful categories. Inter‐coder agreement was significant.

The paper provides evidence of various strategic, technological, and cultural issues influencing the success of KM programs in global software firms. Firms with successful KM programs typically develop three specific capabilities to address these issues. These capabilities, namely, Articulating the KM Strategic Intent, Facilitating the Knowledge Flows to Enable Innovation, and Assessing KM Value, when developed simultaneously, help firms create KM‐enabled value.

Interviews were limited to three companies in the software industry. Future interpretivist studies would benefit from a larger and more diverse sample.

It is suggested that software firms develop specific capabilities to create KM‐enabled value. To provide clear benchmarks for developing these capabilities, a “KM implementation worksheet” is provided.

KM‐enabled value creation is discussed from a unique perspective developed by integrating literature on knowledge‐based view and knowledge management. The paper conducts initial evaluation of the new perspective and provides a roadmap for future research endeavors. Also provided is practical help in the form of a worksheet for practitioners.

The purpose of this paper is to increase the knowledge of brand building in software SMEs.

The empirical method used is a multi‐case study. Data were collected from 20 companies in the software industry through in‐depth interviews. The data were analyzed using systematic coding and categorization of qualitative evidence.

The study identified five special characteristics of brand building in software SMEs, relating to goals and perceived benefits of brand building; resources in brand building; external and internal cooperation in brand building; means and communication in brand building; and the process of product brand building and its connection to software product development.

The scientific contribution of this empirical study relates to two aspects of brand management: branding in software business and branding in SMEs. A vast amount of literature exists on “brands”, “software business” and “SMEs”, but there is very little on “branding in software business” or “branding in SMEs”. Unarguably, there are two significant knowledge gaps in the literature, and they relate to branding in software and SME industries. Both theoretical and managerial knowledge is needed. This study corresponds to this need by increasing the knowledge of brand building in software SMEs with an empirical study. The present study is characterized by the general limitations of a case study. The results lack statistical reliability, they apply primarily in the case companies examined, and no direct generalizations should be made without further quantitative study.

Directors of SMEs often think that branding is just for big companies, but small companies with limited resources can brand their products and services as well. However, the means of branding are often different. The present study encourages SMEs to systematically think of the potential advantages of branding for their business, and develop creative, targeted, and affordable approaches for brand building.

The present empirical study makes an original contribution to the literature by increasing the knowledge of branding in the context of both SMEs and software business.

Software development activities have been identified as a ‘window of opportunity’ for latecomer companies. Based on a critical literature review, this paper argues that studies are yet to scrutinise the exact nature and extent of the capabilities, which the latecomer companies have been able to develop. The main proposition advanced by this research is that the analyses need to investigate the technological capabilities, which the latecomer companies have been able to accumulate. This study outlines the specifics in analysing technological capabilities in latecomer software companies and improves our understanding about the complexity in developing software industries in latecomer context.

The learning outcomes of this study include: recognizing the strategic inflexion points and related business and strategic perspectives in the life of an organization; understanding sources of sustained competitive advantage and connect it with resource-based view for internal analysis; applying dynamic capability theory to identify capabilities that help an IT company stay relevant in an IT sector characterized by VUCA (an acronym for volatility, uncertainty, complexity and ambiguity) environment; analyzing the multi-dimensional and multi-contextual challenge an organization faces, or is likely to face, in the foreseeable future and the possible ways it addresses or should address them; evaluating strategies adopted at various points of an organization’s journey for their effectiveness; and helping a company co-create value for its customers.

This case of Nitor Infotech Private Limited (Nitor), a mid-sized software product outsourcing company, outlines its decade-long journey, highlighting its achievements. While the company has consistently grown by leveraging its expertise in software product engineering and its domain knowledge in the healthcare segment, it entered into a stage of its life cycle where it had to develop a long-term strategy to effectively compete in the product engineering market. Nitor’s strategy was built around product engineering and outsourced product development. The two major choices for a software company were either to develop its own product and thereby own the intellectual property (IP) or to develop modules which would be part of a product that would be owned by a client. In the latter case, the IP would be held by the client. So far Nitor chose to follow the second option by developing components for its client’s products. Although this strategy allowed it to develop expertise in a particular domain, and serve different customers in a particular market, the chances of a competitor attacking its position was high. On the other hand, if it developed its own product, it can create its own brand name and can sell packaged software to several different customers. However, the challenge with the latter is that the cost of marketing could be very high. The choice for the company in the future is to decide on selecting a specific strategy to expand its international business.

This case is appropriate for an undergraduate and postgraduate management course in the area of strategic management. The level of difficulty can be from medium to high depending on the learning level. Knowledge of management fundamentals is not a prerequisite but is desirable for case analysis.

Teaching notes are available for educators only. Please contact your library to gain login details or email support@emeraldinsight.com to request teaching notes.

CSS 11: Strategy