Defining a Requirements Traceability Strategy

Not every project needs the same depth of requirements traceability — a traceability strategy decides, up front, how rigorously each requirement will be linked back to its source and forward to its eventual delivery and test evidence. A regulated, high-risk initiative typically needs a detailed requirements traceability matrix (RTM) tracking every link; a small, low-risk initiative might only need a lighter-weight approach.

Setting this strategy early avoids two opposite failure modes: over-engineering traceability for simple work (which wastes effort nobody needed) or under-engineering it for complex, high-stakes work (which leaves gaps nobody can later prove were covered).

Study focus: expect a scenario describing a project's risk and regulatory profile, asking what level of traceability rigor is appropriate — the right answer scales the traceability effort to the actual stakes, not a one-size-fits-all RTM for every project.