Search results

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.

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.

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.

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.

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.

The article warns that genuine business agility is not easily achieved despite the many consultants offering their services as specialists. It lays out the elements of the best practice approach – the methodology of Agile management.

Using Toyota as an example, the article show how one company is taking an innovative approach to agile team work and decision making.

The concept of Agile management includes both operational agility – making the existing business more focused on customer value – and strategic agility – generating new products and services to bring in new customers.

The shadow of Agile management done too hastily or badly has fostered widespread cynicism.

The article is a clarion call to wake up bureaucratic organizations that pass decisions down a lengthy chain of command. The need now is to have decisions made as close as possible to those who have the best information to make the best decision, which often requires the teams themselves to be the deciders. 10;Leadership becomes a function shared by all the people participating in the team. The team itself becomes the leadership.

The purpose of this paper is to propose Knowledge4Scrum, a novel knowledge management tool for agile distributed teams. Agile software development (ASD) refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The two most widely used methodologies based on the agile philosophy are scrum and extreme programming. Whichever methodology is considered, agile teams usually consist of few members and are collocated under the same roof. However, nowadays, agile practices for distributed development are gaining much momentum. The main reasons behind such practice are cheaper skilled labour, minimizing production cost, reducing time to market and increasing the quality and performance of projects. Along with the benefits obtained through globally distributed development, there are, however, many difficulties faced by various organisations. These problems are caused mostly due to distance, time and cultural differences. To meet up with the level of complexity of projects, ASD also has to keep up with many challenges, especially in cases of distributed teams. Four major challenges have been identified. First, the introduction of global software development entails a number of difficulties, especially related to knowledge sharing. For instance, lack of transparency is frequently observed within such teams, whereby a team member is totally unaware of the activities of his/her colleagues. Second, the unavailability of team members due to time zone differences adds up to the list of problems confronted by distributed teams. Third, there can be misunderstanding amongst the team member due to communication problems, especially in cases where the mother language of the team members is different. Fourth, a common issue faced by distributed teams is the loss of knowledge when an employee resigns from his/her post.

Based on the main problems outlined above, what has been proposed is Knowledge4Scrum, a novel knowledge management tool for agile distributed teams. Knowledge4Scrum will act as a global repository for knowledge sharing in Scrum distributed teams with the possibility of creating new knowledge through data mining techniques. Valid past projects data have been collected to train and test the data mining models. The research also investigates the suitability of knowledge management in Scrum distributed teams to address the various challenges addressed above.

Knowledge4Scrum supports the four knowledge management processes, namely, knowledge creation/acquisition, knowledge storage, knowledge dissemination and knowledge application. It has been found that the aforementioned tool satisfactorily addressed issues of distance, time and cultural differences that crop-up in distributed development teams. Data mining has been the main aspect for the knowledge creation and application processes, whereby new knowledge has been determined by examining and extracting patterns from existing data found in the repository.

A major feature of the Knowledge4Scrum tool lies in the knowledge creation and application section, where a number of data mining techniques have been utilised to identify trends and patterns in past data collected. When compared to the COnstructive COst MOdel to estimate project duration, Knowledge4Scrum gives more than satisfactory results. Such functionalities will actually help managers for future project planning and in decision-making.

Organizational culture has an impact on various activities in organizations, including project management (PM). The aim of the study is to answer the following research questions: RQ1: what significance is attributed to organizational culture compared to the objective project characteristics when choosing the dominant PM methodology in organizations? RQ2: which type of organizational culture is preferred for successful implementation of different PM methodologies? RQ3: what kind (if any) of relationship exists between the dominant type of organizational culture in organizations and the dominant PM methodology?

The author surveyed 100 project managers working in the financial industry in Poland with the use of personal structured interviews. The competing values framework (CVF) concept authored by Cameron and Quinn was used.

Project managers find organizational culture more important than objective project characteristics when choosing the dominant PM methodology in an organization. Although statistical analysis revealed a significant relationship between the preferred type of organizational culture and PM methodology, there is no significant relationship between the existing type of organizational culture and the PM methodology which prevails in the company.

Future research should investigate other industries and other typologies of organizational culture.

The paper provides recommendations for management practice on how to shape organizational culture in the context of successful PM with the application of different PM methodologies.

This study fills a gap in the theory of PM by identifying and empirically verifying the theoretical linkage between the type of organizational culture and PM methodology.

Digital service innovation (DSI) is a type of technological innovation that is recognized in practice in the innovation structure of companies. Given the breadth of digital technologies that enable digital services and the variety of these services, analysis is needed to discern the nature of these services, as well as the process that culminates in co-innovation. The literature on DSI is fragmented and spread across multiple research areas. This fragmentation impedes conceptualization of the elements that constitute DSI. This paper describes the nature of DSI through the process and elements of initiation, adoption and routinization of DSI in the context of digital service platforms (DSPs).

This paper presents a single exploratory case study of a provider of a leading digital solution in customer relations. The data analysis is based on abductive reasoning.

The paper conceptualizes the nature of DSI and describes the process and elements of DSI (phases, actors, functions and interactions). It contributes to building a common language for DSI research in service management. The analysis shows that DSI in DSPs is synonymous with co-innovation. This paper offers insight into how co-innovation occurs, using hybrid agile methodologies with the coordination of multiple actors and multilateral interactions.

The originality and value of the study reside in its conceptualization and analysis of what is meant by DSI. The components of the service and the technological requirements for not only provision but also ideation and development appear to be inseparable. The study unveils the mechanisms that turn a digital service solution into a co-innovative proposal. This knowledge can facilitate scalability in digital services.

The purpose of this paper is to present an innovative agile methodology that proposes fundamental changes in managing the development of in-house information systems in small- and medium-sized enterprises (SMEs) and benchmarks it with one of two database technologies enabling these systems to be both efficient and competitive.

The objectives are achieved by presenting an elaborated design of the agile methodology that manages the system development process by addressing three basic components: roles played by system players, process needed to fulfill the system development, and artifacts to document the project. A case study is conducted as a proof of the effectiveness of the proposed methodology and measures whether the selection of the database technology affects the effectiveness of the system development process.

Results show that, compared with traditional methodologies, the proposed methodology reduced the cost of system development and testing by 30 percent and enhanced the IT – business alliance. Further, this work found that the selection of a suitable database technology is strongly related to the complexity and interrelationships between the data used.

Such research did not receive the needed attention (Hunter, 2004) even in the past decade. Successful adoption of IT by companies could be in the form of customized IS which could be expensive for SMEs to adopt due to a lack in technical expertise and financial resources. The proposed methodology has the potential to promote sustainable development through helping SMEs in reducing the time and cost of IT project development.

Drawing on goal-setting theory and team effectiveness theory, the study aims to examine the impact of agile taskwork and agile teamwork on team performance. In addition, it investigates the mediating effect of project commitment on the impact of agile taskwork and agile teamwork on team performance. Furthermore, the study also tests the moderating role of career level on the impact of agile taskwork and agile teamwork on team performance.

Survey data were collected from 563 employees working in 290 information technology (IT) companies in India using a self-reporting structured questionnaire. Partial least squares path modeling was used to test the hypothesized model, and the Process macro was used to test the moderating effect.

The results show that agile taskwork and agile teamwork positively affect team performance and project commitment, and project commitment positively impacts team performance. Furthermore, project commitment fully mediates the relationship between agile taskwork and team performance and partially mediates the relationship between agile teamwork and team performance. Furthermore, the career level negatively moderates the impact of agile taskwork and agile teamwork on team performance.

The study shows the importance of agile work practices and project commitment to enhance team performance. Thus, the study provides managers with two strategies to improve their team performance.

There is a scarcity of research examining the distinct effects of agile taskwork and agile teamwork on team performance and the mediating role of project commitment in these relationships. Furthermore, as per the empirical evidence, no previous research has empirically examined the moderating role of career level in the agile taskwork-team performance and agile teamwork-team performance relationships.

Agile project management methods are on the rise compared to linear approaches. The demand for the demonstrable resilience of enterprise processes is likewise strongly increasing in many domains. This paper explores the potential contribution of agility within the domain of agile project management to the resilience of the operating model of an organization.

The article builds upon case studies and semi-structured interviews at selected larger Danish enterprises.

Responding to disruptions favors adaptive and flexible approaches, which are more achievable with agile methods. By exploring the patterns of agility and resilience throughout case studies, the authors derive at a 7-step approach for considering the potentials of agility to ensure the resilience of the operating model from the top level of leadership to the foundational level of technology.

This article seeks to contribute to a more profound understanding of the impact, potential and actionability of agile project management in the light of operational resilience.

It is demonstrated that agile methods are attractive for ensuring the constitutive elements of the resilience of the operating model in terms of conscious contingencies and choices involving (rapid) changes.

During the COVID-19 period, agility has been a key instrument in ensuring business survival, e.g. by switching markets, products or sales channels.

Agility has the potential to build a strategic dimension of resilience, a synergistic relationship, which is linked to the responsiveness of an organization to change promptly, with a view toward renewal and transformation.

This paper aims to present a conceptual framework of how software teams can leverage the implicit information of implemented acceptance tests to cater to the needs of decision makers. The research questions on this framework were how business stakeholders can receive project status information in an intuitive way and how this framework can guarantee the traceability of tests to requirements.

The conceptual framework delineates the design of an acceptance test framework in three aspects: how the requirements model reflects the evolving states of requirement maturity over a project, how the acceptance test model becomes synchronized with the requirements model without a traceability matrix and how the acceptance test model communicates business value to the decision makers.

In an industrial case study, the presented framework yielded the positive effects of intuitive understanding by business stakeholders, high test coverage of requirements and distinctly reduced manual quality assurance (QA) work by automated testing for browsers and mobile devices.

The presented framework can help to convince business stakeholders to approve the budget for building a testing framework because it delivers them value as a status reporting tool.

This paper is the first to describe a step-by-step approach to solving a critical problem that IT departments frequently face. The solution consists in a new way of transforming the perception of a technical framework into a reporting tool for business information by intuitive design. The idea of mapping hierarchically corresponding abstraction layers can be transferred to other engineering domains.

The concept of workforce agility has become increasingly popular in recent years. However, defining it has sparked much discussion and ambiguity. Recognizing this ambiguity, this paper aims to inductively develop a behavioral taxonomy of workforce agility.

The authors interviewed 36 experts in the field of agility and used concept mapping and the critical incident technique to create a behavioral taxonomy.

The authors identified a behavioral taxonomy consisting of ten dimensions: (1) accepting changes, (2) decision making, (3) creating transparency, (4) collaboration, (5) reflection, (6) user centricity, (7) iteration, (8) testing, (9) self-organization, and (10) learning.

The authors’ research contributes to the literature in that it offers an inductively developed behavioral taxonomy of workforce agility with ten dimensions. It further adds to the literature by tying the notion of workforce agility to the performance literature.

The authors’ results suggest that it might be beneficial for companies to take all workforce agility dimensions into account when creating an agile culture, starting agile projects, integrating agility into hiring decisions or evaluating employee performance.

This paper uses an inductive approach to define workforce agility as a set of behavioral dimensions, integrating the scientific as well as the practitioner literature on agility.