Social Network Analysis in Software Development Projects: A Systematic Literature Review

Project organization and management software development project management model is the best form of software development enterprises in China's understanding of software development project management has been greatly improved. Traditional software development projects have different characteristics, therefore how flexible application for software project management theory and strategies of the main research objectives of domestic software development project management. Our software in enterprise application software development project management, general shortcomings in implementation, this article on software research and development analysis and project management of implementation strategies.

A recent survey indicates that 53 % of software development projects are over budget, behind schedule, or deliver fewer features than originally specified. Statistics also show that 31 % of development projects end up being cancelled or terminated prematurely. Among those completed projects, only 61 % of them satisfy originally specified features and functions. In today's environment, one of the greatest challenges a project manager constantly face with is to keep the projects under control in terms of budget and development time frame. A successful software development project relies on many factors; it is not that easy to control all of them and continually keeping those entire factors all going well together. The goal of this paper is to introduce a mathematical model and prove that a software development team can rely on it to accurately predict, calculate the risks and their impacts on the success of the project. Our objective is to conceptualize the model into a scientific tool that can be used to understand and calculate the risks of a development project. Subsequently, the software development team can take appropriate actions to mitigate the risks, and as a result, the project manager have a better control of the budget and development time frame of the project. It is the author's believe that if we can identify and control problems at early stages, we can significantly increase the chance of success of the development project. The model and the software tool written by the author in this paper to calculate the risks and weight their impacts on a project can be used to identify problems and their potentials risk at early stage. The tool also allows a project manager to apply the model and obtain results without getting involved in too many mathematical calculations. Although the model introduced in this paper can generally provide an accurate picture of what, how, and when things may go wrong at the beginning of a typical software development project, there are areas need further fine tuned, especially when it is used for a particular industry or at later stages of software development cycle.

The increasing adoption of agile software development methodologies is amplifying the message that people are a first-order success factor of software projects. In this paper we describe a means to make certain people characteristics a first-class concern in software development projects. In particular, we present a systematic way of capturing, making explicit and effectively communicating human attitudes, beliefs and ways of thinking that influence individual and team work in software projects. Moreover, we provide an organised way to supplement and enhance software development methods, processes and project practice in order to explicitly take into account such human factors.

Software development is a global activity unconstrained by the bounds of time and space. A major effect of this increasing scale and distribution is that the shared understanding that developers previously acquired by formal and informal face-to-face meetings is difficult to obtain. This paper proposes a shared awareness model that uses information gathered automatically from developer IDE interactions to make explicit orderings of tasks, artefacts and developers that are relevant to particular work contexts in collaborative, and potentially distributed, software development projects. The research findings suggest that such a model can be used to: identify entities (developers, tasks, artefacts) most associated with a particular work context in a software development project; identify relevance relationships amongst tasks, developers and artefacts e.g. which developers and artefacts are currently most relevant to a task or which developers have contributed to a task over time; and, can be used to identify potential bottlenecks in a project through a `social graph' view. Furthermore, this awareness information is captured and provided as developers work in different locations and at different times.

Requirements volatility (RV) is one of the key risk sources in software development and maintenance projects because of the frequent changes made to the software. Human faults and errors are major factors contributing to requirement change in software development projects. As such, predicting requirements volatility is a challenge to risk management in the software area. Previous studies only focused on certain aspects of the human error in this area. This study specifically identifies and analyses the impact of human errors on requirements gathering and requirements volatility. It proposes a model based on responses to a survey questionnaire administered to 215 participants who have experience in software requirement gathering. Exploratory factor analysis (EFA) and structural equation modelling (SEM) were used to analyse the correlation of human errors and requirement volatility. The results of the analysis confirm the correlation between human errors and RV. The results show that human actions have a higher impact on RV compared to human perception. The study provides insights into software management to understand socio-technical aspects of requirements volatility in order to control risk management. Human actions and perceptions respectively are a root cause contributing to human errors that lead to RV.

Unified process, a leading software development methodology, allows project teams to incrementally build their software and structurally defines project roles, phases, iterations and disciplines. One of the issues that arise when applying unified process is absence of discipline for quality assurance and control. This research aims to define new discipline entitled “quality management of software development” and its processes, in order to produce modified version of unified process, suitable for continually controlling quality in software development projects. This discipline will integrate ISO 9126 “Software engineering – product quality”, which is an international standard for addressing software quality and quality control tools, as proposed by Project Management Book of Knowledge 2010. Main hypothesis of this research is that, by defining and integrating new discipline of quality management, project teams that employ this new, modified version of unified process, will be able to produce software of higher quality level. Experimental research is conducted on four software development projects, ranging from 2009 to 2010, two of which use standard, and two of which use modified unified process model. Research results show higher software quality levels in two projects that use modified unified process methodology.

Implementing software development successfully in an organization is possibly one of the most challenging issues that the industry faces today. Project failures and the lack of software quality have become a major concern for researchers and practitioners. For many software development projects as well as for many quality assurance departments, teamwork is extremely important. Therefore, nearly all organizations pay attention to teamwork which is essential for smooth operation of a project. It is believed that teamwork is crucial for the success or failure of a project. In addition to the importance of teamwork, team issues affecting its' performance also needs attention. Among these team issues, people issues are scarce in the literature. The research outlined in this paper investigated the factors which influence teamwork. It identified the importance of trust and how trust influences IT project teams and the role of project managers and team leaders in improving trust within teams. It also includes individual behaviors that affect trust within a team. A study of six project managers from two Australian organizations was conducted to investigate the factors which influence teamwork to result in project success and software quality. The results showed that trust is a central element of the many factors and that without trust in the team; teamwork will be negatively affected resulting in project failure and poor quality.

The increasing popularity of agile software development has significantly changed the way organizations plan, design, and implement software applications. However, considering the complexity involved with software development, the decision to choose an agile approach over the traditional waterfall approach is not straightforward. Organizations should carefully evaluate a variety of factors when choosing a development approach. In this teaching case study, the authors provide a discussion case to facilitate the students’ learning of using agile vs. traditional approaches in software development. This case study is developed based on experiences of multiple real-world software development projects and the literature on software development. It is designed to reflect the complexities students are likely to encounter in actual software development projects. The case can be used in undergraduate or graduate level management information systems courses that cover agile software development approaches. Students can gain an understanding of factors to consider when choosing a development approach, which tailors to the organization, the project environment, and the project team.

Software development projects face significant risks of going over budget, over schedule, and of failing to deliver expected benefits. These risks have endured despite methodological changes within the industry, such as the rise in popularity of Agile. This research looks outside of the software industry and seeks inspiration from film production, which has developed different management strategies to address challenges similar to those faced by software development projects.First, an analysis of film production project management reveals four principles, each evidenced by a set of practices used throughout the industry. Next, we identify sets of practices that would enable software development projects to also align to those same four principles. The synthesis of each principle from its set of supporting film production practices is then validated through structured interviews with veteran film producers. Lastly, the derivation of each principle to a parallel set of supporting practices within the context of software development is validated in a second series of interviews with experienced software development project managers.In total, this research identifies a set of software development project management practices that mirror film production practices. These practices offer a framework for software development project managers to consider when seeking to tailor existing methodologies, particularly in scenarios that present challenges similar to those encountered in film production.

The need for understanding Generation Y employees' attitudes and expectations that considerably differed from previous generations had been a focus of researchers in the last decades. IT industry and specifically software industry had been among the most popular employment areas of Generation Y professionals and hence Generation Y Software Developers constitutes the majority of the work force in the software industry. As known, software development is a project-based business where the project management methodologies and principles are utilized. Similar to other project based works, the effectiveness of human resources management and team development is the determinant of project success in software development. Therefore, to effectively manage and to adapt appropriate approaches for leading the project teams which include Generation Y software professionals, managers and leaders prior in need to understand their perspective. In this context, research aims to understand the expectations and attitudes of Generation Y Software Developer professionals in projects. The research is structured in two parts reflecting these dual aims. The first part of the research addresses the expectations of Y generation employees from project management and project environment in software development projects. The second part of the research explores the attitudes of Y generation Employees in software development project teams. Survey is conducted with the participation of 113 Generation Y Software Professionals who are employed in major software companies in Turkey. Basic concepts that are explored in the study are expectations from working environment, expectations from project type and content, leadership, motivation factors, challenges faced, perceptions on generation conflicts and the attitudes of Generation Y professionals towards project-based work and work environments. Software industry is dominated by project based management methods, perceptions and attitudes of Generation Y in projects are expected to provide practical guidelines to policy makers and HR professionals in developing solutions and tools for improving motivations and effectiveness of Generation Y employees.

Modeling, analysis, control, and management of complex social networks represent an important area of interdisciplinary research in an advanced digitalized world. In the last decade social networks have produced significant online applications which are running on top of a modern Internet infrastructure and have been identified as major driver of the fast growing Internet traffic. The "Second International Workshop on Modeling, Analysis and Management of Social Networks and Their Applications" (SOCNET 2018) held at Friedrich-Alexander-Universität Erlangen-Nürnberg, Germany, on February 28, 2018, has covered related research issues of social networks in modern information society. The Proceedings of SOCNET 2018 highlight the topics of a tutorial on "Network Analysis in Python" complementing the workshop program, present an invited talk "From the Age of Emperors to the Age of Empathy", and summarize the contributions of eight reviewed papers. The covered topics ranged from theoretical oriented studies focusing on the structural inference of topic networks, the modeling of group dynamics, and the analysis of emergency response networks to the application areas of social networks such as social media used in organizations or social network applications and their impact on modern information society. The Proceedings of SOCNET 2018 may stimulate the readers' future research on monitoring, modeling, and analysis of social networks and encourage their development efforts regarding social network applications of the next generation.

The aim of the study is a practical analysis of social network services as a place to store multimedia resources that allow you to store and share digital photos, audio and video recordings, text files, presentations, and organize resource discussions for free. They can be used as educational materials (educational videos, photos on various topics, audio and video recordings of scientists' speeches, eyewitnesses of events, etc.), as well as means to store student video, photo, audio files and creative works. Method. Theoretical materials of the research are the best practices of foreign and domestic scientists in the field of network communications and their impact on the future specialists preparing in geography and tourism, namely articles, monographs, abstracts, dissertations. The study uses the method of theoretical materials analysis, as well as methods of observation, abstraction in identifying the qualification characteristics of social Internet networks. Content analysis (analysis of the social networks community messages content); statistical and comparative information analysis was carried out. Empirical research on the social Internet networks lies in creating and filling a community on the social Internet network, as well as engaging students in that community. Results. In the research it was found out that social networks can be used to solve the following tasks: to organize the collective work of students in the classroom (and outside it), which will be favourable to the communication, to gain the team experience; to ensure the development of the students personalized learning environment; to promote students independent learning, as everyone works in his own rhythm; to promote informal communication between the tutor and the students; to change the tutor's role, who will become an assistant, friend, mentor; to create digital educational content of the disciplines. The scientific novelty of the obtained results lies in the fact that on the comprehensive analysis of social internet networks, internet blogs, tourist internet resources basis, their place and role in the information and educational environment of higher education institutions are determined, in particular: the specifics of the content, prospects and mechanisms of the development of the social Internet networks from the point of view of training future tourists are determined; the dependence of the functions of the Social Internet Network, Internet blogs on their structural elements is established. Practical significance. The obtained scientific results are used in the educational process of future specialists in the field of training "Tourism", with the educational qualification "tourism expert, organizer of excursion and animation activities" when teaching the disciplines "study of local lore and tourism", "tourist work", "recreational geography", "geography of Ukraine", "professional competencies in tourism business", "organization of tourist activities". The research practices can be used to conduct tourist, museum, local history, excursion and other types of student's practice.

A software metric is the measurement of a particular characteristic of a software or the measurement of a software project and process. In this paper we study how student project managers and team members observe metrics, like working hours, number of test cases, requirement statuses, regular reporting, and number of code commits, and which metrics they consider most important. The metrics that the teams reacted most often were team's working hours and requirements statuses. These metrics were also considered the most useful by the project managers. We propose a method to calculate defect rate of reporting metrics and combine this defect rate with the way the project teams used the metrics. It seems that when the teams were motivated to use metrics, observed them and reacted on base of the metrics, they also had less defects on reporting the metrics.

Antecedents and consequences of team memory in software development projects

Project management uses many tools, techniques, and methodologies in project development. PRINCE2 methodology set documentation which must be tailored to suit the occasion project. Since software projects may often fail due to lack of well-structured project management method, it is necessary to identify the key success factors of PRINCE2 method in software development project. The purpose of this research study is to identify key success factors of PRINCE2 project management method in software development project. The researcher undertakes a case study in an organisation where software project is implemented in PRINCE2 project management method. Data has been collected from questionnaires and face-to-face interviews. Documents review, and observation techniques were used as secondary data collection sources. The researcher has conducted template analysis with interview data and excels analysis with the questionnaires data. The researcher has then triangulated the data to get authentic and accurate findings. 20 factors have been identified as key success factors in this research study such as defined roles & responsibilities, scope management, manage by stages, well planning, top management support, time management, risk management, monitor project progress, change management, communication management, quality management, project team competency, managing product delivery, cost management, learn from experience, prioritizing task, assign work to right person, benefit realisation and being agile.