Over the past decades we have seen several methodologies for software development and approaches to perform requirements engineering. However, requirements engineering continues to be one of the challenging aspects of software engineering because it involves understanding the requirements of business users and ensuring that they are specified correctly to build applications and products that will satisfy business users. This is also true for projects that follow agile methodologies. Moreover, delivering working software in short iterations requires intense communication and coordination among agile teams in order to refine requirements and identify dependencies and conflicts. In my experience with agile teams in both collocated and distributed environments, an interesting aspect I have observed is that successful agile teams learn from unusual sources. In this article, I have shared some simple lessons from five unusual source
