Before the Agile Manifesto's promulgation, one of the main challenges in software development was the production of requirement specifications, often accompanied by numerous inefficiencies. Among the four core values of the Agile Manifesto, one emphasized “working software over comprehensive documentation”. However, this value was frequently misinterpreted, leading to minimal documentation practices that prioritized “doing agility” over building quality software. Consequently, user stories replaced use cases. Over time, it became apparent that one problem was merely substituted for another: a significant decline in the quality of requirements. This work seeks to underscore two key points: 1) The issue does not stem from favoring one technique over the other but rather from the need to properly define and specify requirements; 2) These techniques are not interchangeable; they address distinct aspects of requirements. To achieve the best results, they are most effective when used in combination.