The paper presents the results of a survey performed in 23 Agile companies. The survey focuses on the identification of the non-agile practices used in the organization of their development process. Even if the companies considered in the study are using Agile approaches to develop their products, the organization and the planning of the work is deeply affected by the approaches used in Plan-Based companies. Understanding which are the most used non-agile techniques and why managers are still so linked to them can identify potential weaknesses in the actual implementation of the Agile Methods. 1.

Notwithstanding the pervasiveness of enterprise systems, their selection and implementation is still being perceived as problematic if not risky. Research in the tradition of requirements engineering argues that its insights will ameliorate this condition. Yet, the context of enterprise systems has outmoded requirements engineering methodically and practically. Theoretically, analysis of the presuppositions of requirements engineering has identified a methodological turn that proffers a cogent explanation of empirical findings about today's practices. The conclusions are of immediate relevance for organisations, since they present an updated view of current practices of selection and implementation of enterprise systems.

Due to the enormous pressure towards deploying software as fast as possible, functional requirements have been the main focus of software development process at the expense of implementing non-functional requirements (NFRs) such as performance and security. Thus, in practice, NFRs have been observed to be frequently neglected or forgotten in the software development process. However, NFRs is an important concept in requirements engineering which plays an essential role in the success or the failure of systems. NFRs introduce quality characteristics, but they also represent constraints under which the system must operate. So, the chances of success for the software system are maximized when NFRs are modeled since the initial phases of the development process. This article reviews the NFR concepts, relates them to the overall software development process and identifies new areas of further work. Keywords. Requirements engineering, Non-functional requirements, Software development process.

How can an organization facilitate customer engagement in an agile software development project, emphasizing on the project's needs and constraints? The objective of this thesis is to answer this questions based on literature and an empirical study of a software development company.

This paper investigates commonalities and differences between Agile and Documentation-driven approaches in managing uncertainty in requirement gathering. The research method is a survey collected interviewing sixteen project managers of Italian software companies, 8 using Agile Methods, and 8 using Documentation-driven methods. The results show that Agile and Document-driven companies consider in a different way the problem of changing requirements and the related uncertainty; thus, they manage differently requirements gathering and the relationship with the customer. 1.

The paper presents the results of a survey performed in 23 Agile companies. The survey focuses on the identification of the non-agile practices used in the organization of their development process. Even if the companies considered in the study are using Agile approaches to develop their products, the organization and the planning of the work is deeply affected by the approaches used in Plan-Based companies. Understanding which are the most used non-agile techniques and why managers are still so linked to them can identify potential weaknesses in the actual implementation of the Agile Methods. 1.

Abstract – Nowadays, in time of rapid software development and continuous change, the software development organizations have increasingly been adapting the Agile practices within their software development methodologies. This paper discusses experiences and observations of applying a set of selected Agile practices within globally distributed organization responsible for development of large scale software systems for evolving telecommunication products. The paper provides valuable material for practitioners who plan to adopt agile principles in similar environment conditions. Also we give possible direction for future research. I.

Nowadays, many of the Agile based project development teams are distributed geographically across the globe. The teams are divided into onshore and offshore that work together to achieve on a common target. The teams in turn work in small iterations to minimize the effect of change in software requirements and at the same time developing regular communication between them. However different factors such as physical distance and lack of proper communication between the onshore and offshore teams become a hurdle between them leading to misunderstandings about software requirements. Though there are many advanced way of communication like video conferencing, voice chatting is available, it certainly has several disadvantages in getting the task completed. This paper gives an insight about these challenges faced in many of the software industries and it would allow different stakeholders within agile based onshore /offshore setting to better understand these challenges in eliciting their requirements. General Terms This article can be classified under the problems faced and the solutions achieved in the software life cycle management.

Version: 1.0

"A case study on analyzing socio-technical congruence within a distributed software development project on the project level"