  Non-functional requirements (NFRs) are determinant for the success of
software projects. However,they are characterized as hard to define, and in
agile software development(ASD), are often given less priority and usually not
documented. In this paper, we present the findings of the documentation
practices and challenges of NFRs in companies utilizing ASD and propose
guidelines for enhancing NFRs documentation in ASD. We interviewed
practitioners from four companies and identified that epics, features, user
stories, acceptance criteria,Definition of Done(DoD), product and sprint
backlogs are used for documenting NFRS. Please refer to the manuscript for the
full abstract.
