• Aucun résultat trouvé

Managing Requirements Interdependencies in Agile Software Development: A Preliminary Result

N/A
N/A
Protected

Academic year: 2022

Partager "Managing Requirements Interdependencies in Agile Software Development: A Preliminary Result"

Copied!
2
0
0

Texte intégral

(1)

Managing Requirements Interdependencies in Agile Software Development: A Preliminary

Result

Indira Nurdiani

Blekinge Institute of Technology SE-37179 Karlskrona, Sweden

indira.nurdiani@bth.se

Abstract. Currently managing requirement interdependencies using Ag- ile practices is relatively unexplored. This study explores the state of practice of managing requirements interdependencies in Agile software development through a survey. A total of 52 complete responses were obtained, with 50% of the respondents suggesting that they consider requirements interdependencies. The preliminary result indicates that requirements interdependencies become a greater concern as the project and product complexity increases.

Keywords: Agile Methods, Survey, Requirements Interdependencies

1 Introduction

Software is a fast paced industry with frequent requirement changes from the customers. To maintain competitive advantage software companies need to react quickly to requirement changes. Agile methods, such as Scrum and eXtreme Programming (XP) [1], emerged to provide a solution to software companies to react rapidly to requirement changes.

With Agile methods, requirements are implemented incrementally in a series of releases [1]. In incremental development, such as in Agile methods, managing interdependencies between requirements is critical [2]. However, the management of requirement dependencies using Agile practices is a relatively unexplored re- search topic [3,4].

This paper presents the preliminary results of a survey to explore the state of practice of managing requirements interdependencies in Agile development teams. In this study, requirement interdependency is defined as relationships between backlog items, e.g., epics, metaphors, or stories. The following aspects are particularly explored in this study (1) whether requirements interdependen- cies are considered in the industry and (2) which tools or practices are used to manage requirements interdependencies.

(2)

2 Indira Nurdiani

2 Methodology and Preliminary Results

A web-based survey1was used as a data collection strategy. A total of 52 respon- dents completed the survey. The respondents were recruited primarily from the author’s personal contacts as well as relevant conferences and discussion forums.

The majority of the respondents were software developers with 27 respon- dents, followed by Scrum masters with six respondents. To name a few the re- spondents also include business analyst, system architect, etc. The preliminary analysis of the survey shows that 26 respondents suggested that they considered requirement interdependencies in their projects. Thirteen respondents suggested that they did not consider requirements interdependencies, and the remaining 13 respondents suggested that they did not know. One of the popular reasons provided by the respondents for not considering requirements interdependencies was the simplicity of the projects. Other reasons include lack of awareness or simply because their roles did not require them to consider requirements inter- dependencies.

A number of tools and practices were also identified from the survey. The tools that were mentioned include JIRA, Team Foundation Server (TFS), and, Git. The use of informative workspace, like white boards, Scrum or Kanban board was also reported by the respondents. Known Agile practices, such as retrospective and planning meeting, were rarely mentioned as an approach to manage requirements interdependencies. The preliminary analysis also shows that the tools and practices are used in combination with each other.

The preliminary results of the survey show that requirements interdependen- cies is an important concern in Agile development teams. The results further indicate that requirements interdependencies become a greater concern as the project and product complexity increases. The next step in this study to com- plete the analysis of the remaining sections of the survey.

References

1. Beck, K.: Embracing Change with eXtreme Programming. Computer 32(10), 70–77 (Oct 1999)

2. Carlshamre, P., Sandahl, K., Lindvall, M., Regnell, B., Natt och Dag, J.: An indus- trial survey of requirements interdependencies in software product release planning.

In: the proceedings of the 5th IEEE International Symposium on Requirements Engineering. pp. 84–91 (2001)

3. Martakis, A., Daneva, M.: Handling requirements dependencies in agile projects:

A focus group with agile software development practitioners. In: the proceedings of the 7th IEEE International Conference on Research Challenges in Information Science (RCIS 2013). pp. 1–11 (May 2013)

4. Schalliol, G.: Challenges for analysts on a large xp project. Marchesi, et al.,(eds.) Extreme Programming Perspectives, Pearson Education, Indianapolis, IN (2003)

1 http://www.bth.se/com/inu.nsf/pages/requirements-interdependencies-in-agile- survey

Références

Documents relatifs

presents a semi-formal approach for eliciting and documenting efficiency requirements (a type of NFRs) with use cases and a high-level architecture. This approach uses

On the other hand, both applications received high scores in perceived audio- visual adequacy, perceived feedback's adequacy, and perceived usability.. These results provided a

i) First Study: Survey with privacy experts to validate the concepts found in our SLR. This study results in a conceptual model of privacy related concepts. ii) Second Study:

With the course of time, innovative products tend to become functional products and thus tend to move from an agile strategy to a lean strategy. Although

 All the interviewees assert that the traceability presents one of the proofs to determine the responsibility in case of incident.  The traceability has an

spatial school facilitates knowledge sharing by us- ing office space but in distributed agile projects this strategy is not explicitly in practice to share knowl- edge among remote

Lean management (hereafter referred to as Lean) is a holistic approach aiming at providing the right product in the correct amount of time at the right place

We evaluated politeness, sentiment and emotions of comments posted by agile developers and studied the communication flow to understand how they interacted in the presence of