English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Requirements engineering (RE) is considerably different in agile developmentthan in more traditional development processes. Yet, there is little empiricalknowledge on the state of the practice and contemporary problems in agile RE.As part of a bigger survey initiative (Naming the Pain in RequirementsEngineering), we build an empirical basis on such aspects of agile RE. Based onthe responses of representatives from 92 different organisations, we found thatagile RE concentrates on free-text documentation of requirements elicited witha variety of techniques. Often, traces between requirements and code areexplicitly managed and also software testing and RE are aligned. Furthermore,continuous improvement of RE is performed due to intrinsic motivation.Important experienced problems include unclear requirements and communicationflaws. Overall, we found that most organisations conduct RE in a way we wouldexpect and that agile RE is in several aspects not so different from RE inother development processes.

Requirements Engineering Practice and Problems in Agile Projects: Results from an International Survey