![Skillset requirements [16]](https://www.researchgate.net/profile/Anita-Hidayati-2/publication/339778558/figure/tbl1/AS:958780372160518@1605602462245/Skillset-requirements-16_Q320.jpg)
Content uploaded by Anita Hidayati
Author content
All content in this area was uploaded by Anita Hidayati on Nov 17, 2020
Content may be subject to copyright.
A preview of the PDF is not available
Hard and Soft Skills for Scrum Global Software Development Teams
Figures
Figures - uploaded by Anita Hidayati
Author content
All figure content in this area was uploaded by Anita Hidayati
Content may be subject to copyright.
... Аналіз досліджень та публікацій. Результати багатьох досліджень підтверджують, що нині існує зростаюча потреба студентів у розвитку не лише технічних компетенцій, але також і так званих м'яких (соціальних) навичок для ефективного та дієвого виконання професійної діяльності у глобалізованому світі [1][2][3][4][5][6][7][8]. Актуальність проблеми у контексті підготовки PhD з інженерії програмного забезпечення розглянуто у роботі [2]. ...
... У роботі [7] автори намагаються виявити найбільш важливі технічні і нетехнічні навички при роботі в команді з розробки програмного забезпечення за методологією Scrum. В своєму дослідженні вони аналізують літературні джерела, проводять анкетування студентів, обговорюють питання в фокус-групах фахівців. ...
... Among these skills, the following stand out [22,37]: effective communication skills, teamwork, conflict resolution, leadership, and resilience. capacitação, como cursos, treinamentos, workshops [17,37]. Hard skills are technical abilities acquired through training, such as courses, workshops, and training programs [17,37]. ...
... capacitação, como cursos, treinamentos, workshops [17,37]. Hard skills are technical abilities acquired through training, such as courses, workshops, and training programs [17,37]. Notable hard skills in software testing include knowledge of programming and testing languages, automation tools, and collaborative software [12,37]. ...
The development of skills and competencies required by computing professionals plays a crucial role in ensuring the quality of software products before their implementation. In particular, the software industry has increasingly sought professionals with management, communication, innovation, and social skills. There needs to be more comprehensive research in the literature that addresses both the technical skills (hard skills) and the behavioral skills (soft skills)required by software testing professionals. This paper presents the results of a survey conducted with 101 software testing professionals. The goal was to highlight information about the soft and hard skills that are important for professionals who work with software testing. In addition, we identified the tools and programming languages employed to support the activity testing software. The results of this work provide valuable insights into the most relevant technical and behavioral skills for testing professionals, which are required for them to perform their jobs efficiently and effectively.
... Additionally, (1) frontend web technologies and frameworks, (2) backend web technologies and frameworks, and (3) web design and tools were identified as separate technical skills of web developers. Programming and technical skills should be a unified single skill [71,72]. ...
Human skills are a critical factor in the success or failure of a digital project. Limited studies have been conducted to identify the industry demand for skills of scrum roles (product owner, scrum master, web developer) and levels (entry, associate, mid-senior). The evaluation of skills over time benefits both decision-makers and associated team members, which leads to successful project completions. The aim of this research is to improve decision making concerning the level-specific skills of selected scrum roles for digital projects. The study identifies major and minor skills, patterns, and relationships between levels, and formulates the mathematical equations as the most important inputs to the skill-driven model’s implementation and evaluation. Both qualitative and quantitative research methods were used to analyse 900 surveyed job advertisements published on LinkedIn in Europe. Descriptive analysis was used to analyse quantitative data while the deductive approach was followed with thematic analysis. There are required skill sets for each level of roles, level-specific skills, industry-demanded skills, and formulas related to the initial and individual skill ratings that are investigated. A new mechanism for evaluation is introduced based on “the time spent with skills”. As a result, the proposed model is implemented by feeding research findings into the Mendix programming platform. The skill-driven model is a decision-support solution in software project management to evaluate skills which assist in assigning the right person to the right digital project. Further investigation on different job portals can help to improve the accuracy of industry standards and reduce the lack of progression skills by overcoming limitations identified in this paper.
... The sprint is the central component of software development, during which a finished, ready-to-use, and possibly release-ready product increment is developed [19]. Right after the preceding sprint, a new sprint starts. ...
Accessibility modifications are required for individuals with situational, temporary, or permanent impairments to properly interact with web applications. Incorporating accessibility guidelines, such as the Web Content Accessibility Guidelines (WCAG), into software development, along with the software development life cycle and other paradigms, poses challenges. The linear progression of steps in a conventional software development process leads to the identification of problems at a later stage because testing is typically conducted toward the end. Limited attention to accessibility until the final development phase results in prolonged efforts, increased resource allocation, and higher expenses to address accessibility issues. Consequently, numerous software applications remain inaccessible to users with impairments. This study focuses on a Shift Left-based model to improve accessibility in the software development process. Employing the Shift Left a11y Model that emphasizes early integration for accessibility and coupling it with the Extreme Programming Development Life Cycle would enhance the integration of various testing practices and facilitate the development of software that is accessible to all users, including those with impairments. Keywords: Accessibility, accessible software, shift-left, model, methodology for accessible software
Digitalisation in Ukraine and the world changes products, services, and business processes, affecting the number and quality of jobs due to the need for digital skills. Employers are requiring new skills from candidates in job profiles for existing managerial positions. The purpose of this study was to investigate the impact of soft skills, hard skills, and digital skills on managers in the era of digitalisation based on the analysis of business requirements. The following methods were used: theoretical generalisation and comparison (disclosure of the content of each group of skills), analysis (skills most frequently and most demanded by employers), statistical method (summary and grouping of data collected from the job search portal), synthesis (combination of different types of information), and concretisation (identification of problems in the legislative and regulatory framework of Ukraine). The study established the ratio of skill groups in the analysed positions: sales manager, HR manager, and logistics manager mainly need the following skill groups: soft and hard, but to varying degrees. Soft skills are essential for the positions of sales manager and HR manager, while hard skills prevail for the position of logistics manager. Only project managers need hard skills and digital skills because of their specificity. To provide a better understanding and visualisation of complex information about competencies or skill levels, the authors first introduced a “three-zone competency stoplight” and a colour matrix of the result of soft, hard, and digital skills requirements of employers by position. Three skills groups are proposed to be represented in different colours: orange (soft), pink (hard), and green (digital), which will allow businesses to use this visualisation to see the zones that correspond to their job offers and understand what skills they will require from candidates for the relevant position and to what extent. The practical significance of the study is the possibility of using its results in the development of educational programmes for planning the development of necessary disciplines
Background: Global Software Engineering (GSE) extends geographical, temporal, and cultural boundaries in distributed environments. Over the past two decades, GSE research has evolved to manage software development for distributed teams. The COVID-19 pandemic highlights the need for comprehensive research, particularly during the software design phase, to support team collaboration in distributed development. Aim: This study systematically analyzes the evolution of research emphasis in the GSE field, specifically exploring on whether the research focuses increasing on software design due to the global pandemic. Method: We systematically analyzed the existing literature in two phases. In the first phase of our study, we mapped GSE research over the two decades leading to the pandemic (2000–2020). In the second phase, we used the forward snowballing approach to examine the literature on the software design phase published between 2020 and 2022. Results: The analysis of 592 research studies in the two phases reveals various trends in GSE research. Evaluation research is the most explored research type in methods and processes, and human aspects of development. Despite the paradigm shift caused by the COVID-19 pandemic that increased reliance on distributed teams, results show that while software organizations are extensively studied across all software engineering phases, the software design phase remains one of the least explored areas. Conclusion: This work highlights the evolving GSE research trends, emphasizing the rising significance of collaborative software design in distributed settings. Our findings address current research gaps and underscore the need for further research on software design activities. This contribution envisions a more collaborative, adaptable GSE field, guiding future research to support distributed teams.
A trend in information systems development is for globally distributed teams to use agile methods and frameworks such as Scrum. In globally distributed (GD) software development, a known challenge is effective team communication. Researchers, however, cannot evaluate effective communication in GD teams using Scrum unless they know what effective communication means in that context. This qualitative study contributes a theoretical model of effective communication in GD Scrum teams and practical guidance for practitioners. Ten industry professionals working in GD Scrum teams were interviewed to capture their understanding of effective communication. Qualitative content analysis was used to analyse the interviews and form a basis for the model and the practical guidance. This novel model consists of communication transparency, communication quality, and communication discipline, which together lead to the alignment of team understanding (i.e., a team-level shared mental model). This theoretical model lays the ground for future research into the effect of Scrum practices on communication in GD contexts, and the effect of communication on team and project success. For practitioners, this study contributes 11 practical actions that professionals recommend for improving and sustaining effective communication.
Present-day Software Engineering working environment is highly international. Teams are commonly formed of people from different nationalities and cultural backgrounds. The teams’ productivity and efficiency depend significantly on its members’ international communication and collaboration competences. Therefore, understanding the required competences is essential. The software organizations hiring new software engineers need to be able to define and describe the competences, and the junior software engineers applying their first jobs should know what competences they need to possess and demonstrate. In this study, to increase understanding of necessary communication and collaboration competences in the international Software Engineering working environment, competences were, first, analyzed from the job ads applicable to junior software engineers and, second, identified by a literature review. The results were compared to identify what competences junior software engineers should learn and demonstrate, to be competent in the international software engineer job markets. The job ad findings show that the international operational environment expects extensive competence in collaboration, high competence in English, and considerable competence in local language and communication. Intercultural competence and other languages are hardly expected. The literature review emphasizes inter-related communication, collaboration, intercultural, and language competences at different levels. Eventually, junior software engineers should demonstrate a tolerant and adaptable attitude, cooperativeness, independence, openness, courage to influence, oral and written social interaction skills, fluent professional English and local language communication skills as well as field-specific and general collaboration methods. The findings benefit juniors, Software Engineering education, and thus employers, by providing the international working environment with more competent jobseekers.
Agile Scrum Software development methodology has been accepted widely by the Software Engineering (SE) community. This is mainly due to agile principles that emphasize on rapid development process which enables working quality software to be delivered on time. Successful Agile Scrum project depends on the high-performance of team members that assigned to a specific software project. Therefore, Scrum project highly demand the right person to be assigned as a team member. Due to this, skill sets requirements among team members are significant for the project manager to select the best team. There are two types of skills for team members that need to be identified-hard skills and soft skills. Thus, this study aims to define each of the skills set requirements based on review of literature and expert's opinions. It is hoped that the defined skills set requirements can serve as a guideline to develop a comprehensive Agile team formation method.
Context: Developing software in distributed development environments exhibits coordination, control and communication challenges. Agile practices, which demand frequent communication and self-organization between remote sites, are increasingly found in global software development (GSD) to mitigate said challenges. Objective: We aim to provide detailed insight into what is reported on the successful application of agile practices in GSD from 1999 to 2016 and also identify the most frequently applied agile practices and reported distribution scenarios. We further strive to uncover research opportunities and gaps in the field of agile GSD. Method: We build our systematic literature review on top of a previous review, which investigated studies published between 1999 and 2009, and extend the review by years 2010-2016, for which we conduct both a quantitative and a qualitative analysis. Results: Our results show that the majority of the cases studied is global and involves complex distribution scenarios with Scrum or combined Scrum/Extreme Programming being the most used agile methods. Key results include that in contrast to 1999-2009, where four Extreme Programming practices were among the ten most frequently used agile practices, in 2010-2016 Scrum is in the center of agile GSD implementations with eight Scrum-based practices in the top ten agile practices used in GSD. Conclusion: Agile GSD is a maturing research field with higher quality contributions and a greater variety of publication types and methods from 2010 to 2016 than before from 1999 to 2009. However, researchers need to report full empirical contextual details of their studied cases in order to improve the generalizability of results and allow the future creation of stronger frameworks to drive the implementation of agile practices in GSD.
Context: Follow the Sun (FTS) development is a special case of Global Software Development. It is applied in the context of global projects to reduce the software development life-cycle duration.
A number of studies have attempted to aggregate a better understanding of FTS development, but it is still an immature research area.
Objective: This paper aims to investigate the existing empirical evidence about FTS research with a focus on identifying what research has been conducted in the area and which results have been obtained.
Method: To achieve this goal, we performed a systematic mapping study to answer our research questions: “Which FTS studies have been published in the literature?” and “What empirical support is provided for them?” We investigated papers published between 1990 and 2017. The synthesis was made through classifying the papers into different categories (research topics, research methods, conferences and journals venues for FTS research, and countries involved in FTS research).
Results: We selected 57 papers using a predefined search strategy. The majority of the papers discussing FTS were published in the International Conference on Global Software Engineering
(ICGSE). The main research topic addressed is processes and organization development for FTS. Case studies combined with the interview as a research sub-method is adopted in the most studies performed in FTS. The majority of the existing research and the most active researchers in this topic are from the United States and Brazil. However, India and the United States are the countries that appear most often in the studies conducted to investigate FTS.
Conclusion: Our findings suggest that FTS software development is an up-to-date research topic in Software Engineering. However, little information about FTS has been published over the last few years. The emergent need in this research is the development of evaluation research for testing FTS feasibility and effectiveness in practice.
Scrum, an agile software development method, has gained major interest among software development organizations. The scrum master should be well equipped with specific leadership traits and exhibit leadership behavior to effectively manage his/her team. However, in a distributed team, which is spread across geographies, having scrum master to lead the project team at each location is not viable. Therefore, every member in the team is expected to have the capability to become one. This paper aims to explore the leadership mechanisms desired for effective functioning of distributed self-organized scrum team members, leading to project success and overall customer satisfaction.
A qualitative research methodology with an open-ended questionnaire is followed by semi-structured in-depth interviews. The unit of analysis is a scrum master.
The qualitative findings unearth the kind of leadership mechanisms required for scrum masters and the team members in a self-organizing scrum team, leading to their project success and customer satisfaction. It includes a set of leadership approaches and behaviors explicitly related to the role of scrum masters. Both inductive and deductive approaches are used to develop a leadership framework applicable for distributed self-organized scrum teams.
The proposed framework can be empirically tested with a large number of teams and more software organizations.
Organizations can use these identified specific leadership approaches and behaviors as parameters for identifying and selecting the potential scrum masters. They can be further trained on them to be an effective scrum master.
There is scant literature on the leadership mechanisms necessary for distributed scrum teams and their impact on project performance. This paper addresses this gap.
Global outsourcing is a growing trend among independent software vendors. In these projects like other distributed work, distances have negative effects on communication and coordination, directly impacting performance. We present a normative model designed to address this issue by improving communication and knowledge exchange. The model consists of six distinct practices and a tool blueprint, each coming with practical guidelines. It is based in part on two case studies of Dutch software vendors who have successfully outsourced part of their activities to an Eastern European outsourcing vendor, and validated by a panel of six experts from industry and the scientific community. It is concluded that knowledge exchange in global software outsourcing is a by-product of efforts to enhance communication and coordination, rather than specific technical solutions. By committing to sharing knowledge, emphasizing transparency and integrating the outsourcing team into their organizations, customers from the product software business can realize the benefits of global outsourcing.
In this paper, an approach for information systems reverse engineering is proposed and applied. The aim is to support a unified perspective to the reverse engineering process of both data and software. At the state of the art, indeed, many methods, techniques, and tools for software reverse engineering have been proposed to support program comprehension, software maintenance, and software evolution. Other approaches and tools have been proposed for data reverse engineering, with the aim, for example, to provide complete and up-to-date documentation of legacy databases. However, the two engineering communities often worked independently, and very few approaches addressed the reverse engineering of both data and software as information system's constituencies. Hence, a higher integration is needed to support a better co-evolution of databases and programs, in an environment often characterized by high availability of data and volatility of information flows. Accordingly, the approach we propose leverages the detection of object-relational mapping design patterns to build a conceptual schema of the software under analysis. Then, the conceptual schema is mapped to the domain model of the system, to support the design of the evolution of the information system itself. The approach is evaluated on two large-scale open-source enterprise applications. Copyright © 2014 John Wiley & Sons, Ltd.
Context:
The way global software development (GSD) activities are managed impacts knowledge transactions between team members. The first is captured in governance decisions, and the latter in a transactive memory system (TMS), a shared cognitive system for encoding, storing and retrieving knowledge between members of a group.
Objective:
We seek to identify how different governance decisions (such as business strategy, team configuration, task allocation) affect the structure of transactive memory systems as well as the processes developed within those systems.
Method:
We use both a quantitative and a qualitative approach. We collect quantitative data through an online survey to identify transactive memory systems. We analyze transactive memory structures using social network analysis techniques and we build a latent variable model to measure transactive memory processes. We further support and triangulate our results by means of interviews, which also help us examine the GSD governance modes of the participating projects. We analyze governance modes, as set of decisions based on three aspects; business strategy, team structure and composition, and task allocation.
Results:
Our results suggest that different governance decisions have a different impact on transactive memory systems. Offshore insourcing as a business strategy, for instance, creates tightly-connected clusters, which in turn leads to better developed transactive memory processes. We also find that within the composition and structure of GSD teams, there are boundary spanners (formal or informal) who have a better overview of the network’s activities and become central members within their network. An interesting mapping between task allocation and the composition of the network core suggests that the way tasks are allocated among distributed teams is an indicator of where expertise resides.
Conclusion:
We present an analytical method to examine GSD governance decisions and their effect on transactive memory systems. Our method can be used from both practitioners and researchers as a “cause and effect” tool for improving collaboration of global software teams.
Background
In Global Software Development (GSD), informal communication and knowledge sharing play an important role. Social Software (SoSo) has the potential to support and foster this key responsibility. Research on the use of SoSo in GSD is still at an early stage: although a number of empirical studies on the usage of SoSo are available in related fields, there exists no comprehensive overview of what has been investigated to date across them.Objective
The aim of this review is to map empirical studies on the usage of SoSo in Software Engineering projects and in distributed teams, and to highlight the findings of research works which could prove to be beneficial for GSD researchers and practitioners.MethodA Systematic Mapping Study is conducted using a broad search string that allows identifying a variety of studies which can be beneficial for GSD. Papers have been retrieved through a combination of automatic search and snowballing, hence a wide quantitative map of the research area is provided. Additionally, text extracts from the studies are qualitatively synthesised to investigate benefits and challenges of the use of SoSo.ResultsSoSo is reported as being chiefly used as a support for collaborative work, fostering awareness, knowledge management and coordination among team members. Contrary to the evident high importance of the social aspects offered by SoSo, socialisation is not the most important usage reported.Conclusions
This review reports how SoSo is used in GSD and how it is capable of supporting GSD teams. Four emerging themes in global software engineering were identified: the appropriation and development of usage structures; understanding how an ecology of communication channels and tools are used by teams; the role played by SoSo either as a subtext or as an explicit goal; and finally, the surprising low percentage of observational studies.