Looking for Reasons behind Success in Dealing with Requirements Change

During development, requirements of software systems are subject to change. Unfortunately, managing changing requirements can take a lot of time and effort. Yet some companies show a better management of changes in requirements than others. Why? What is it that makes some projects deal with changing requirements better than others? We pursue the long term goal of understanding the mechanisms used to successfully deal with change in requirements. In this paper we gather knowledge about the state-of-the-art and the state-of-practice. We studied eight software development projects in four different companies --large and small, inclined toward structured and toward agile principles of development--, interviewing their project managers and analyzing their answers. Our findings include a list of practical (rather than theoretical) factors affecting the ability to cope with small changes in requirements. Results suggest a central role of size as a factor determining the flexibility showed either by the organization or by the software development team. We report the research method used and validate our results via expert interviews, who could relate to our findings

Increasing the value of research: a comparison of the literature on critical success factors for projects, IT projects and enterprise resource planning projects

Since the beginning of modern project management in the 1960s, academic researchers have sought to identify a definitive list of Critical Success Factors (CSFs), the key things that project managers must get right in order to deliver a successful product. With the advent of Information Technology (IT) projects and, more recently, projects to deliver Enterprise Resource Planning (ERP) systems, attention has turned to identifying definitive lists of CSFs for these more specific project types. The purpose of this paper is to take stock of this research effort by examining how thinking about each type of project has evolved over time, before producing a consolidated list of CSFs for each as a basis for comparison. This process reveals a high degree of similarity, leading to the conclusion that the goal of identifying a generic list of CSFs for project management has been achieved. Therefore, rather than continuing to describe lists of CSFs, researchers could increase the value of their contribution by taking a step forward and focusing on why, despite this apparent knowledge of how to ensure their success, ERP projects continue to fai

Managing change – can HR software help?

With the pace of change in the HR and wider business environment seemingly becoming ever-faster, Human Resources teams have a real challenge on their hands to manage any resulting disruption. Employee engagement and morale is at stake, not to mention the reputation of HR, and there is significant pressure to justify the financial implications of any change projects undertaken. In this white paper, HR thought leaders therefore focus on the subject of best-practice change management, whilst providing 'real world' examples from the UK's 11th largest housing association, Together Housing. The white paper also analyses the value of technology to help streamline the potentially disruptive change management process, before sharing tips and advice for those embarking upon their own change journey

Towards Automated Performance Bug Identification in Python

Context: Software performance is a critical non-functional requirement, appearing in many fields such as mission critical applications, financial, and real time systems. In this work we focused on early detection of performance bugs; our software under study was a real time system used in the advertisement/marketing domain. Goal: Find a simple and easy to implement solution, predicting performance bugs. Method: We built several models using four machine learning methods, commonly used for defect prediction: C4.5 Decision Trees, Na\"{\i}ve Bayes, Bayesian Networks, and Logistic Regression. Results: Our empirical results show that a C4.5 model, using lines of code changed, file's age and size as explanatory variables, can be used to predict performance bugs (recall=0.73, accuracy=0.85, and precision=0.96). We show that reducing the number of changes delivered on a commit, can decrease the chance of performance bug injection. Conclusions: We believe that our approach can help practitioners to eliminate performance bugs early in the development cycle. Our results are also of interest to theoreticians, establishing a link between functional bugs and (non-functional) performance bugs, and explicitly showing that attributes used for prediction of functional bugs can be used for prediction of performance bugs

Factors Affecting the Development of Workforce Versatility

Among all strategies supporting the firms' flexibility and agility, the development of human resources versatility holds a promising place. This article presents an investigation of the factors affecting the development of this flexibility lever, related to the problem of planning and scheduling industrial activities, taking into account two dimensions of flexibility: the modulation of working time, which provides the company with fluctuating work capacities, and the versatility of operators: for all the multi-skilled workers, we adopt a dynamic vision of their competences. Therefore, this model takes into account the evolution of their skills over time, depending on how much they were put in practice in previous periods. The model was solved by using an approach relying on genetic algorithm that used an indirect encoding to build the chromosome genotype, and then a serial scheduling scheme is adopted to build the solution