144 research outputs found

    Some Findings Concerning Requirements in Agile Methodologies

    Get PDF
    gile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies

    Changing situational contexts present a constant challenge to software developers.

    Get PDF
    A software process can take many forms and its optimality demands that it should be harmonised with the needs of the given software development situational context. This theoretical proposition is reasonably clear. However, the finer details of the interaction between the software process and the factors of the situational context are much less obvious. In previously published research, the authors have elaborated a reference framework that identifies the factors of a situational context that affect the software process [1]. In this paper, we report on the application of our reference framework in an examination of the changing nature of software development situational contexts. Our corresponding study of fifteen software development companies indicates that certain factors appear more subject to change than others. This finding is a potentially important insight that can help us with the recurring challenge of adapting the software process to changing circumstances

    Agile software development practices in Egypt SMEs : a grounded theory investigation

    Get PDF
    Agile information system development methods have been adopted by most software development organizations due to their proven benefits in terms of flexibility, reliability, and responsiveness. However, companies face significant challenges in adopting these approaches. Specifically, this research investigates challenges faced by software development companies in Egypt while transitioning to Agile. As little previous research is available targeting their concerns, we have conducted a grounded theory investigation. Key problem areas were found including lack of cadence in sprints planning, inadequate use of effort estimation and product quality issues. The developed grounded theory reflects on the key problem areas found with SMEs adopting agile practices and can be used by software development practitioners adopting agile methods in Egypt or similar developing countries as an outline for the common problem areas they are expected to find

    Information flows at inter-team boundaries in agile information systems development

    Get PDF
    Agile software development methods are being used on larger projects thus the study of inter-team communication are becoming an important topic of interest for researchers. This research addresses inter-team communication by exploring the tools and three different boundaries, inter-team, team and customers, and geographically separated teams. In this research, we gathered data from semi-structured face-to-face interviews which were analyzed following the grounded theory approach. Our study reveals consensus from different teams on the importance of virtual Kanban boards. Also, some teams members tend to adapt to other teams’ preferred communication tool. We observed challenges around interdependent user stories among the different teams and highlighted the problems that rise at the different boundaries. Keywords: agile information system development • inter-team communication • agile team boundary • communication • agile methods • cooperating agile team

    Commissioning of the vacuum system of the KATRIN Main Spectrometer

    Get PDF
    The KATRIN experiment will probe the neutrino mass by measuring the beta-electron energy spectrum near the endpoint of tritium beta-decay. An integral energy analysis will be performed by an electro-static spectrometer (Main Spectrometer), an ultra-high vacuum vessel with a length of 23.2 m, a volume of 1240 m^3, and a complex inner electrode system with about 120000 individual parts. The strong magnetic field that guides the beta-electrons is provided by super-conducting solenoids at both ends of the spectrometer. Its influence on turbo-molecular pumps and vacuum gauges had to be considered. A system consisting of 6 turbo-molecular pumps and 3 km of non-evaporable getter strips has been deployed and was tested during the commissioning of the spectrometer. In this paper the configuration, the commissioning with bake-out at 300{\deg}C, and the performance of this system are presented in detail. The vacuum system has to maintain a pressure in the 10^{-11} mbar range. It is demonstrated that the performance of the system is already close to these stringent functional requirements for the KATRIN experiment, which will start at the end of 2016.Comment: submitted for publication in JINST, 39 pages, 15 figure
    corecore