Search results
1 – 10 of over 9000Kai Li, Lulu Xia, Nenggui Zhao and Tao Zhou
The purpose of this paper is to compare the pricing decisions and earning potential of the software supplier and the smart device manufacturer in different software promotion…
Abstract
Purpose
The purpose of this paper is to compare the pricing decisions and earning potential of the software supplier and the smart device manufacturer in different software promotion strategies.
Design/methodology/approach
Based on game theory, the authors formulate two promotion models, that is, the supplier implements software promotion activities individually (SP model) or outsources the promotion activity to the manufacturer under profit-sharing contract (MP model) when taking different channel power structures into consideration. Besides, in order to test the robustness of the conclusions, the authors also extend the basic model to the following situations: (1) the customers have different price elasticity toward service fee and product price; (2) the revenue sharing contract is employed by the supply chain members; and (3) the manufacturer's product promotion practice is taken into consideration.
Findings
The optimal service fee (product price) of the supplier (manufacturer) under SP model is always lower (higher) than that under MP model. Surprisingly, if the supplier is the channel leader and the profit sharing ratio exceeds certain threshold, the manufacturer's profit decreases in profit sharing ratio, which remains robust in three extension models. Moreover, the supply chain's profit in supplier-led game is always lower than that in Nash game irrespective of the promotion strategy in profit sharing context. When revenue sharing contract is adopted, the result holds only when the revenue sharing ratio is relatively low.
Originality/value
The authors originally explore two promotion strategies of the software supplier when taking the channel power structures into considerations, which has not been explored in the literature to the best of the authors' knowledge.
Details
Keywords
Cost-benefit (C/B) analysis helps to determine the economic feasibility of business software investments. Research literature and published practices do not recognize substantial…
Abstract
Purpose
Cost-benefit (C/B) analysis helps to determine the economic feasibility of business software investments. Research literature and published practices do not recognize substantial software maintenance costs in C/B analysis. Current analyses emphasize the benefits of an initial investment but do not consider the recurring benefits of each enhancement during the software lifecycle. Such analyses could lead to incorrect investment decisions and lost business opportunities. This article aims to review current research on software lifecycle costs and develop a theoretically sound C/B analysis.
Design/methodology/approach
This article reviews current C/B analyses and discusses their shortcomings in treating the significant recurring maintenance costs. It analyzes the findings of various studies on software maintenance and synthesizes these findings to identify the nature of various maintenance costs and their benefits. Based on the synthesis, it theorizes various cost and benefit elements for inclusion in a revised C/B analysis.
Findings
This article identifies each recurring maintenance cost relevant to C/B analysis. It also identifies recurring benefits from each enhancement that hitherto have been omitted. Finally, this article discusses how these costs and benefits should be treated in the revised C/Bs analysis.
Research limitations/implications
This is a conceptual paper proposing a new C/B analysis and requires an empirical validation.
Practical implications
This article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.
Originality/value
This article provides a revision of the C/B analysis that is long overdue. It will help to justify a software investment correctly, rank software projects that compete for limited funds and help create a sound software project portfolio. Since 20% of software products may incur 80% of software investment, this analysis will help to make correct software investments and avoid lost business opportunities. This article also describes a practical method to use the revised C/B analysis.
Details
Keywords
In socio-technical transition theory, resistance by existing technology and regime resistance plays a key role. The resistance is in the form of intentional improvements;…
Abstract
Purpose
In socio-technical transition theory, resistance by existing technology and regime resistance plays a key role. The resistance is in the form of intentional improvements; eventually, the regime destabilizes and adopts the new technology, referred to as the sailing-ship effect. Researchers used a structural view and examined it as a strategic action and its relationship with new technology (competitive/symbiotic) in non-fast-changing sailing systems. This study uses a microlevel view and examines it in a fast-changing where products/services are developed by integrating existing technology with new product innovations; their success depends on addressing technical/market uncertainty. This study examines the sailing-ship effect in a fast-changing system and contributes to the socio-technical transition theory.
Design/methodology/approach
The authors need to examine the phenomena of the sailing-ship effect in its setting, and a case-study method is appropriate. The selected case provided diverse analytic and heuristic perspectives to examine the phenomena; therefore, it was a single case study.
Findings
In an IT scenario, the strategic actions decide and realize agility and competitive advantage by formulating appropriate goals with required budgets and coevolutionary changes to resources at product, process and organizational levels, addressing technical/market uncertainty. Moreover, the agility displayed by strategic actions determines the relationship with new technology, which is interspersed. Finally, it provided insights into struggle, navigation and negotiations, forming strategic actions to display the sailing-ship effect.
Research limitations/implications
The study selected a Banking Financial Services and Insurance product of an IT Services company. As start-ups exhibit inherent (emergent) agility, the authors can examine agility as a combination of emergent and strategic actions by selecting a start-up.
Practical implications
The study highlights the strategic actions specific to an IT services company. It developed its product and services by steering clear from IT innovations such as native cloud and continuous deployment. It improved its products/services with necessary organizational changes and achieved the desired agility and competitive advantage. Therefore, organizations devise appropriate strategic actions to combat the sailing-ship effect apart from setting goals and selecting IT innovations.
Originality/value
The study expands the socio-technical transition theory by selecting a fast-changing system. It provided insights into the relationship between existing and new technology and the strategic actions necessary to manage technical and market uncertainty and achieve the desired competitive advantage, or the sailing-ship effect.
Details
Keywords
Shekhar Rathor, Weidong Xia and Dinesh Batra
Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles…
Abstract
Purpose
Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).
Design/methodology/approach
Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.
Findings
The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.
Originality/value
The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.
Details
Keywords
Martin Dietze and Marion Kahrens
This paper aims to close the gap between the generic concept of knowledge activities (KAs) and implementing them in the context of software engineering organisations concentrating…
Abstract
Purpose
This paper aims to close the gap between the generic concept of knowledge activities (KAs) and implementing them in the context of software engineering organisations concentrating on the non-technical aspects, such as team organisation and practices.
Design/methodology/approach
This qualitative research used a questionnaire with practitioners such as software developers and team leads who were asked to provide feedback on a set of team practices and measures typically used in software engineering projects and assess their relation to the activities of acquiring, codifying, storing, maintaining, transferring and creating knowledge. The obtained results were analysed using frequency analysis and further descriptive statistics yielding a matrix linking the investigated team practices and measures to KAs.
Findings
Team practices and measures commonly applied in software engineering can be facilitated to trigger particular KAs. While most of these team practices and measures originate from agile methods, they are not restricted to these. A purposeful composition can help in assembling a balanced set of KAs aimed at fostering given knowledge goals in software engineering organisations.
Practical implications
By bridging the communication and terminology gap between knowledge management research and software engineering practitioners, this work lays the foundation for assessing software teams’ knowledge profiles more easily and creating prerequisites for implementing knowledge management by facilitating common practices and measures often already part of their daily work. Hence, overhead can be avoided when implementing knowledge management.
Originality/value
To the best of the authors’ knowledge, this is the first study investigating application and relevance of KAs in the software industry by linking them to practices and measures well-accepted in software engineering, thus providing the necessary vocabulary for the implementation of knowledge management in software development teams.
Details
Keywords
Adriano Rehder, João Valsecchi Souza, Roberto Marx and Mario Sergio Salerno
Agile methods are increasingly being applied in the contexts of innovation beyond traditional information technology (IT) and physical product development projects, such as when…
Abstract
Purpose
Agile methods are increasingly being applied in the contexts of innovation beyond traditional information technology (IT) and physical product development projects, such as when process improvements are being implemented. Nevertheless, this phenomenon is still recent and little addressed in the literature, with few descriptions of empirical cases. This study aims to address this gap.
Design/methodology/approach
This multiple case study aims to present and discuss the application of Agile practices embedded in large companies’ innovation value chains, focusing on improvements of business processes. The following research question is pursued: How are large companies applying elements of Agile methods to their innovation processes when implementing incremental improvements in their operational processes? Based on the idea that the Agile-Stage-Gate model is an alternative to this challenge, this study investigates the application of this hybrid model in two large Brazilian companies by presenting their idiosyncrasies, lessons learned, adaptations, challenges and benefits.
Findings
Overall, it was observed that the experience with the application of the Agile-Stage-Gate model is positive for these companies, with better customer engagement, easier project control and increased productivity of the project team.
Originality/value
For those aiming to implement the Agile-Stage-Gate model, this paper identifies the main adaptations made in order to combine the purist approaches and critical success factors for its implementation.
Details
Keywords
Stephan Kudyba and Agnel D Cruz
Digital transformations of business processes are on the rise and the result is a need for a better understanding of how the elements of intellectual capital (IC) play a role in…
Abstract
Purpose
Digital transformations of business processes are on the rise and the result is a need for a better understanding of how the elements of intellectual capital (IC) play a role in achieving successful digital project outcomes. New structural capital in the form of digital technologies must be identified and understood. Evolving skills of human capital in assimilating digital elements must also be considered, while collaboration within the development process involving relational capital provides a critical integration among these IC elements. This study illustrates the importance of identifying and managing the integration of IC components within an agile project management framework that are essential to achieving success for a digital initiative. More specifically, this study describes the process by which a multinational technology-based products company successfully developed a dynamic decision support platform utilizing an agile approach to guide a project management team to better manage the company's operations.
Design/methodology/approach
This study focuses on a case analysis approach of a multinational commercial and consumer products company. The paper presents existing research on the evolving state of project management for digital initiatives and focuses on agile methods. This study then delves into the case analysis that illustrates how IC played an integral role in the company successfully developing effective decision support involving an interactive dashboard using agile Project Management (PM), which enabled the project management team to better manage resources.
Findings
An examination at the case level illustrates that effective management and integration of IC has positive effects on project outcomes. While a balanced approach is evident as a requirement, the unique characteristics of the agile project management approach entails greater emphasis on select elements to adapt to a more dynamic development process.
Originality/value
This work depicts the complexities in providing analytic-based decision support in an agile/flexible project management scenario. This work adds to existing research by illustrating elements within IC categories and the elements' interdependencies that play an essential role in achieving success in this more flexible project environment.
Details
Keywords
Dale T. Eesley, Yukti Sharma, Ramendra Singh and Birud Sindhav
Entrepreneurship literature recognizes the founder’s involvement as a salient factor in determining the success of startups. Nevertheless, its role in conjunction with the…
Abstract
Purpose
Entrepreneurship literature recognizes the founder’s involvement as a salient factor in determining the success of startups. Nevertheless, its role in conjunction with the marketing roles of founders has been relatively unexplored. Very little is known about how founder’s involvement in marketing tasks (i.e. developing products, sales and customers) helps attain success in early startups. To fill this knowledge gap, this study aims to qualitatively investigate the founder’s involvement under three vital functional areas (i.e. sales, customer development and product development) and also explain their entwined nature of the relationship as the early-stage startups grow to become a scalable businesses.
Design/methodology/approach
This study used purposive sampling for conducting in-depth interviews with 11 startup founders in the midwestern city of the USA. A constant comparative method was used to code the interview transcripts, while juxtaposing them with extant literature.
Findings
Using three levels of axial coding, this study identified 32 descriptive codes, 11 aggregate codes and 2 interpretive codes. Following this, the authors present five propositions that illustrate the relationship between founders’ involvement, customer development, product development and sales.
Practical implications
This study offers guidelines to founders on how they could generate initial sales, identify early customers and build and sustain mutually beneficial relationships with them.
Originality/value
This study contributes to the extant literature on entrepreneurship and innovation literature. It presents motivation and potential processes, including systematic activities performed by founders in generating sales in conjunction with customer development and product development, thereby making a novel contribution.
Details
Keywords
Ia Williamsson and Linda Askenäs
This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.
Abstract
Purpose
This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.
Design/methodology/approach
This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.
Findings
The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.
Originality/value
Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.
Details
Keywords
Ewa Sońta-Drączkowska and Agnieszka Krogulec
This study seeks to illuminate the managerial tensions inherent in implementing scaled agile (on the organizational, top management, middle management and team levels) and to…
Abstract
Purpose
This study seeks to illuminate the managerial tensions inherent in implementing scaled agile (on the organizational, top management, middle management and team levels) and to frame these challenges within the broader context of project management.
Design/methodology/approach
The study adopts a grounded theory approach and delves into a qualitative dataset sourced from 34 interviews with subject matter experts actively engaged in scaling agile initiatives within large organizations spanning various industries. Additionally, the data have been enriched through a comprehensive literature review of the existing body of knowledge on scaling agile.
Findings
As a result of our investigation, we propose a framework of managerial tensions in scaling agile in large corporate settings and a series of research propositions and questions that may contribute significantly to the body of knowledge surrounding the phenomenon of “deprojectification” and propose agenda for the future studies in the field of project management.
Research limitations/implications
The study also carries significant managerial implications. Firstly, based on the insights from the practice of scaling agile in large corporate setting, management can build awareness of the challenges inherent of transitioning to agile practices. This may help to anticipate the possible problems and proactively develop strategies how to address them. Secondly, management can be instructed about contingencies inherent in scaling agile, along with the potential disfunctions and side effects (unintended outcomes) that may emerge during the transition process. Thirdly, project management practitioners can gain insights on how scaling agile may cause shifts in the approach to managing projects, project team management and competencies that need to be developed to cope with environments where various approaches to managing projects coexist.
Practical implications
These insights can aid in the agile transition process, beginning with directing managerial attention toward contextual factors and progressing through potential challenges at the organizational, top management, middle management and team levels. Furthermore, the study highlights possible dysfunctionalities and side effects of scaling agile, shedding light on the “dark side” of agile.
Originality/value
The study contributes to the expansion of the empirical database on the implementation of agile practices in large organizational settings. It plays a role in defining and delineating the phenomenon of scaling agile within the context of project management and outlines a research agenda for future project management studies. Additionally, our study adds to the ongoing discourse surrounding the “deprojectification” effect that can occur during the scaling of agile. Lastly, it establishes connections between project management and software development literature regarding the implementation of agile at scale.
Details