its an important interview question. i want everyone to share their view on it. we all know that RTM is most commonly used in waterfall. But in agile what do we use ?
The most common way to trace requirements in Agile is to use a tool such as JIRA or Rally where Epics/Initiatives are traced or decomposed in to Features, Features are decomposed into Stories, and Stories can be traced to individual tasks.
In organizations where documentation is critical (such as large platforms or in a regulated environments), in addition to the Agile artifacts (which tend to become work-orders) the team may, in parallel, maintain system and platform documentation.
Hi JAGDEEPMANAK,
I think Adrian's answer pretty much hit the nail on the head. In JIRA you also have the option of completing fields such as who the business owner is for that Epic/Feature and who from a BA perspective is responsible for writing the respective User Stories. Typically for the companies that I have worked at, the Product Owner (i.e. the Business) writes the Epic or Feature(s) and the BA will write the User Stories (these act as the requirements to fulfill that Feature that they belong to). This way in a years time when someone asks "Why did we do this?" I can tell who in the Business raised the initial work request (The Feature) and who worked the requirements (The User Stories). I can also tell which Developer worked on the associated Tasks in the same manner.
This acts as your full tracability. I personally find it much easier to handle and ensure it is accurate than the traditional RACI method for Waterfall.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: