Requirements engineering (RE) has a long and successful tradition. While different approaches always existed, RE became optimized for an artefact driven setup where the individuals hand-over documents. Now agile practices spread. They are geared for a team setup where individuals form one “super-brain” based on intensive interaction. The proven approaches from RE suddendly create a lot of friction and bad smells. So, should we forget about requirements?