Walk me through how you create and maintain a requirements traceability matrix for a mid-sized project; what fields do you include and how do you use it to manage scope and verify coverage?

Question

VirtualInterview.AI · Accepted Answer

For a 10-sprint billing integration I built an RTM in Excel/Confluence starting from 240 user stories. Columns included requirement ID, description, source stakeholder, priority, functional/non-functional, acceptance criteria, linked user story/ticket, design doc reference, test case ID, status, and release/sprint. I kept it live by syncing weekly to JIRA using a simple ID convention and a script that flagged orphan requirements and gaps in test coverage. That process caught four missing security tests and prevented scope creep that would have added ~2 weeks. The RTM became our single source of truth for traceability during UAT and for the compliance audit, where it cut evidence-prep time by ~60%.

Sample Answer

Keywords