  Requirements are key artefacts to describe the intended purpose of a software
system. The quality of requirements is crucial for deciding what to do next,
impacting the development process's effectiveness and efficiency. However, we
know very little about the connection between practitioners' perceptions
regarding requirements quality and its impact on the process or the feelings of
the professionals involved in the development process.
  Objectives: This study investigates: i) How software development
practitioners define requirements quality, ii) how the perceived quality of
requirements impact process and stakeholders' well-being, and iii) what are the
causes and potential solutions for poor-quality requirements. Method: This
study was performed as a descriptive interview study at a sub-organization of a
Nordic bank that develops its own web and mobile apps. The data collection
comprises interviews with 20 practitioners, including requirements engineers,
developers, testers, and newly employed developers, with five interviewees from
each group.
  Results: The results show that different roles have different views on what
makes a requirement good quality. Participants highlighted that, in general,
they experience negative emotions, more work, and overhead communication when
they work with requirements they perceive to be of poor quality. The
practitioners also describe positive effects on their performance and positive
feelings when they work with requirements that they perceive to be good.
