Some Findings Concerning Requirements in Agile Methodologies

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

Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program

Software development projects have undergone remarkable changes with the arrival of agile development methods. While intended for small, self-managing teams, these methods are increasingly used also for large development programs. A major challenge in programs is to coordinate the work of many teams, due to high uncertainty in tasks, a high degree of interdependence between tasks and because of the large number of people involved. This revelatory case study focuses on how knowledge work is coordinated in large-scale agile development programs by providing a rich description of the coordination practices used and how these practices change over time in a four year development program with 12 development teams. The main findings highlight the role of coordination modes based on feedback, the use of a number of mechanisms far beyond what is described in practitioner advice, and finally how coordination practices change over time. The findings are important to improve the outcome of large knowledge-based development programs by tailoring coordination practices to needs and ensuring adjustment over time.Comment: To appear in Project Management Journa

Requirements Engineering for Globally Distributed Teams using Scaled Agile Framework

As large organizations are striving to deliver software at a faster pace and to keep up with the latest trends, they are in a transformation stage of adopting to Scaled Agile Framework (SAFe). SAFe is a framework for implementing agile practices at enterprise level and it provides a roadmap for portfolios, programs and teams. Large organizations adopting to SAFe are facing challenges in coordinating, planning and managing requirements, as they work with globally distributed teams. The goal of this thesis was to improve the Requirements Engineering (RE) process using Scaled Agile Framework in globally distributed teams. The main research method used in this thesis was action research, an iterative approach which combines theory and practice. The empirical study was conducted in a large project that used SAFe and had eight globally distributed teams. In order to investigate the challenges faced by globally distributed teams, analysis of the existing literature and RE process flow in SAFe was important. It served as a good input to understand which good RE practices can be applied in the empirical study. The results of the study show that visually representing requirements as models and sharing domain and system knowledge through Community of Practice (CoP) reduced ambiguity in requirements. The good RE practice applied in SAFe, of working and improving collaboratively with the globally distributed teams helped in better coordination and managing of requirements. In addition to this, it was also essential to have SAFe training to develop clear and shared understanding of the framework and RE process. The lessons learned from the empirical study indicate that a well-organized PI planning is the key RE practice of SAFe in providing the big picture of requirements to all members in distributed teams. In addition, Community of Practice (CoP) can be a key RE practice of SAFe in sharing knowledge such as business domain, system knowledge, skills and techniques, and experiences

Principles in Patterns (PiP) : Piloting of C-CAP - Evaluation of Impact and Implications for System and Process Development

The Principles in Patterns (PiP) project is leading a programme of innovation and development work intended to explore and develop new technology-supported approaches to curriculum design, approval and review. It is anticipated that such technology-supported approaches can improve the efficacy of curriculum approval processes at higher education (HE) institutions, thereby improving curriculum responsiveness and enabling improved and rapid review mechanisms which may produce enhancements to pedagogy. Curriculum design in HE is a key "teachable moment" and often remains one of the few occasions when academics will plan and structure their intended teaching. Technology-supported curriculum design therefore presents an opportunity for improving academic quality, pedagogy and learning impact. Approaches that are innovative in their use of technology offer the promise of an interactive curriculum design process within which the designer is offered system assistance to better adhere to pedagogical best practice, is exposed to novel and high impact learning designs from which to draw inspiration, and benefits from system support to detect common design issues, many of which can delay curriculum approval and distract academic quality teams from monitoring substantive academic issues. This strand of the PiP evaluation (WP7:38) attempts to understand the impact of the PiP Class and Course Approval Pilot (C-CAP) system within specific stakeholder groups and seeks to understand the extent to which C-CAP is considered to support process improvements. As process improvements and changes were studied in a largely quantitative capacity during a previous but related evaluative strand, this strand includes the gathering of additional qualitative data to better understand and verify the business process improvements and change effected by C-CAP. This report therefore summarises the outcome of C-CAP piloting within a University faculty, presents the methodology used for evaluation, and the associated analysis and discussion. More generally this report constitutes an additional evaluative contribution towards a wider understanding of technology-supported approaches to curriculum design and approval in HE institutions and their potential in improving process transparency, efficiency and effectiveness

Agile Processes in Software Engineering and Extreme Programming

This open access book constitutes the proceedings of the 22nd International Conference on Agile Software Development, XP 2021, which was held virtually during June 14-18, 2021. XP is the premier agile software development conference combining research and practice. It is a unique forum where agile researchers, practitioners, thought leaders, coaches, and trainers get together to present and discuss their most recent innovations, research results, experiences, concerns, challenges, and trends.  XP conferences provide an informal environment to learn and trigger discussions and welcome both people new to agile and seasoned agile practitioners. This year’s conference was held with the theme “Agile Turns Twenty While the World Goes Online”. The 11 full and 2 short papers presented in this volume were carefully reviewed and selected from 38 submissions. They were organized in topical sections named: agile practices; process assessment; large-scale agile; and short contributions

Semantic Bridging between Conceptual Modeling Standards and Agile Software Projects Conceptualizations

Software engineering benefitted from modeling standards (e.g. UML, BPMN), but Agile Software Project Management tends to marginalize most forms of documentation including diagrammatic modeling, focusing instead on the tracking of a project\u27s backlog and related issues. Limited means are available for annotating Jira items with diagrams, however not on a granular and semantically traceable level. Business processes tend to get lost on the way between process analysis (if any) and backlog items; UML design decisions are often disconnected from the issue tracking environment. This paper proposes domain-specific conceptual modeling to obtain a diagrammatic view on a Jira project, motivated by past conceptualizations of the agile paradigm while also offering basic interoperability with Jira to switch between environments and views. The underlying conceptualization extends conceptual modeling languages (BPMN, UML) with an agile project management perspective to enrich contextual traceability of a project\u27s elements while ensuring that data structures handled by Jira can be captured and exposed to Jira if needed. Therefore, concepts underlying the typical software development project management are integrated with established modeling concepts and tailored (with metamodeling means) for the domain-specificity of agile project management. A Design Science approach was pursued to develop a modeling method artifact, resulting in a domain-specific modeling tool for software project managers that want to augment agile practices and enrich issue annotation

Assisting product line thinking and information sharing using a real-time visual tracking model for agile epics

The aim of this thesis is to understand and reduce repeated development of software artefacts, mainly in terms of the software components that are produced in the organization of Natural Resources Institute Finland. The thesis consists of a literature review around code reuse and the software product line method of building software. In the case study of the thesis, a visual model is added to the Jira environment of the organization of Natural Resources Institute Finland DIGI unit. The project workers associated with each project are interviewed both before and after the visual model was added. Through the results of the interviews, the study identifies improvements to understandability and presentability of projects. Suggesting that the addition of a graphical model for epics on a high abstraction level helps project workers increase information sharing within an organization, but more research is needed to understand and enable the technical impact of the model