No abstract available.
Proceeding Downloads
Ninth International Workshop on Managing Technical Debt: report on the MTD 2017 workshop
Welcome to the Ninth International Workshop on Managing Technical Debt, collocated with the 18th International Conference on Agile Software Development (XP 2017) in Cologne. The technical debt research community continues to expand through ...
Changes and challenges of technical debt and its management during ongoing digital transformation
In this paper, we look how changes and challenges in technical debt and its management that could emerge from the ongoing digital transformation. The digital transformation ensues from companies' opportunities to join various digital ecosystems and use ...
Revisiting context-based code smells prioritization: on supporting referred context
Because numerous code smells are revealed by code smell detectors, many attempts have been undertaken to mitigate related problems by prioritizing and filtering code smells. We earlier proposed a technique to prioritize code smells by leveraging the ...
Who is producing more technical debt?: a personalized assessment of TD principal
Technical debt (TD) impedes software projects by reducing the velocity of development teams during software evolution. Although TD is usually assessed on either the entire system or on individual software artifacts, it is the actual craftsmanship of ...
Assessing code smell interest probability: a case study
An important parameter in deciding to eliminate technical debt (TD) is the probability of a module to generate interest along software evolution. In this study, we explore code smells, which according to practitioners are the most commonly occurring ...
An investigation of technical debt in automatic production systems
Technical Debt is a recent concept, borrowed from the financial domain. It has been recently used in software development to describe technical sub-optimal solutions that have short-term benefits but long-term extra-costs. However, no body of literature ...
The magnificent seven: towards a systematic estimation of technical debt interest
The interest of Technical Debt is difficult to assess. The negative effects (severity) of Technical Debt might depend on the context of the organization and the estimations might be subjective. There is a need for assessing Technical Debt interest in a ...
Towards triaging code-smell candidates via runtime scenarios and method-call dependencies
Managing technical debt includes the detection and assessment of debt at the code and design levels (such as bad smells). Existing approaches and tools for smell detection primarily use static program data for decision support. While a static analysis ...
Technical debt interest assessment: from issues to project
The interest of Technical Debt (TD) is difficult to calculate, especially on a project level. Current approaches are based on fine-grain issue assessment, but there is no evidence about how TD is assessed on a project level. A few tools use an ...
Generating innovations for the internet of things: agility and speed
The Internet of Things (IoT) bears great potential for innovation in modern companies. Agility and speed both matter when innovating in such a context. The first Inno4IoT workshop focuses on how to properly achieve and balance the two aspects while ...
Security challenges in IoT development: a software engineering perspective
The rapid growth of Internet-of-things (IoT) software applications has driven both practitioners and researchers' attention to methodological approaches for secure IoT development. Security issues for IoT is special in the way that they include not only ...
CitySense: blockchain-oriented smart cities
A smart city is a connected system in which things produce a huge quantity of data. We focused the attention on monitoring the environment quality in urban area by means of a distributed network of small mobile sensors that are devices on the Internet ...
An analysis of the bluetooth terminal development pivots from lean startup perspective: experience and lessons learnt
This paper presents an analysis, as a case study, of the development of the "Bluetooth terminal" application, a tool to monitor Bluetooth devices. The objective is to get further insight on how to use pivots to get a product closer to its users, and on ...
Emerging research themes and updated research agenda for large-scale agile development: a summary of the 5th international workshop at XP2017
Large software development projects and programs are increasingly adopting agile development practices. Frameworks for managing large agile development projects is gaining popularity, such as the Scaled Agile Framework and Large Scale Scrum. New ...
Assigned roles for inter-team coordination in large-scale agile development: a literature review
Inter-team coordination has been recognized as one of the most important challenges in large-scale agile development settings. Except specific practices, such as Scrum of Scrums meetings, certain roles are often reported to be responsible for areas of ...
Inter-team coordination mechanisms in large-scale agile
Coordination is an important but challenging success factor in large-scale software development. Large-scale is particularly demanding because it involves several teams, and therefore we chose to study coordination between teams. Our aim of this case ...
Coordination in the large: a research design
The public sector is facing a massive digitalization process in order to provide faster and more automated services to the public. Several new projects in this sector are developing software using agile methodologies. There is, however, a lack of ...
The SAFe way to the agile organization
How do you make the agile organization? This paper gives an answer in form of a case story from the financial software company SimCorp. In late 2015SimCorp decided to go agile on a big scale. To do so they applied the scalable agile framework SAFe. In ...
Agile transformation model for large software development organizations
Many organizations are going through large-scale agile transformations but they face challenges with measuring when the transformation has reached its goals or communicating what kinds of results they are expecting. Based on our experiences we developed ...
Trends in agile development of safety-critical software: a summary of the 3d international workshop on agile development of safety-critical software (ASCS 2017)
Agile development of safety-critical software has evolved from an early conceptual idea to, presently, an approach that is gaining uptake in the industry. As we now get more and more experience we also discover new challenges and related ideas that ...
The dynamics of agile practices for safety-critical software development
This short paper reports from a case study of the agile development of safety-critical software. It utilizes a framework of dynamic relationships between agile practices with the purpose of demonstrating the utility of the framework to understand a case ...
A study of safety documentation in a Scrum development process
Context: There has been an increasing use of agile techniques for safety-critical systems. Agile techniques embrace fast changing requirements, continuously delivered products and frequent communication with lightweight documentation. Motivation: ...
Microservices in agile software development: a workshop-based study into issues, advantages, and disadvantages
In the last years, cloud-native architectures have emerged as a target platform for the deployment of microservice architectures. The migration of existing monoliths into cloud-native applications is still in the early phase, and only few companies ...
Results of the 2nd International Workshop on the Impact of Agile Practices (ImpAct 2017)
At present, agile development is a dominating development process in software engineering. Yet, due to different contexts, also agile methods require adaptations (e.g. Scrum-but). Since adaptation means adding, modifying or dropping some agile elements, ...
- Proceedings of the XP2017 Scientific Workshops
Recommendations
Acceptance Rates
Year | Submitted | Accepted | Rate |
---|---|---|---|
XP '15 workshops | 15 | 11 | 73% |
Overall | 15 | 11 | 73% |