Has anyone created a Requirements Traceability Matrix? Even though I have seen and used a couple of formats, but wasn’t quite impressed with those. Trying to have a discussion here to see how this format can be improved by sharing inputs from all of us.
goakhter wrote Has anyone created a Requirements Traceability Matrix? Even though I have seen and used a couple of formats, but wasn’t quite impressed with those. Trying to have a discussion here to see how this format can be improved by sharing inputs from all of us.
Like any other endeavor a business analyst undertakes, (s)he must first ask "Why?" Don't use a traceability matrix because everybody else is or because you think you should. Ask yourself, what problem did I encounter and which I'm trying to solve. If the traceability matrix solves your problem then go ahead and use it. Otherwise, you will not be impressed at all.
For example, I've heard so many people who are not happy with use cases because "Use cases don't work!" only to find out they are trying to utilize the use cases to show data flow in their application. Of course - use cases won't work. Use the right tool for the right task.
But I digress...
Back to the traceability matrix...
There are indeed many formats, styles, and ways to use a traceability matrix and the format which you might end up using depends on the task at hand:
Do you have a specific problem you are trying to solve or a goal you need to achieve?
- Adrian
Thanks Adrian for the tip. To answer your question about the specific problem - yes, the requirements I am capturing are subjected to changes frequently and this is going on for quite sometime. Understood this is one of those time when a BA needs to draw a line on the sand and propose implementing CM process. But before start this conversation, I was planning to have a document that would capture the functional requirements, map it to the data requirements and planned Test Case to clearly show the problem this fluidity is causing to the overall project and how a simple/single change triggers a cascading effect and impact multiple areas..
I am sure RequisitePro is a great product for complex traceability, but it is not always easy to justify the cost.
Now you brought a interesting perspective. I created Gap Analysis document in the manner you described (col/row arrangement), but never did this with Traceability Matrix. Will try to create a Template and see how it looks. Also can share this format with a couple of other stakeholders and get their feedback. It is looks and works better, then I may keep using that format going forward.
-golam
"the requirements I am capturing are subjected to changes frequently and this is going on for quite sometime."
If I may.... this sounds like the major issue impacting you. There is no value in doing change management or traceability if the Requirements to be managed/traced are not stable. Trying change management in this case will just annoy everyone involved.
So, what is happening that is causing unstable requirements? Is there a target date for requirements, and for the project overall?
www.iag.biz
Traceability matrix can created in many formats (Graphical, tabular, tree). We have used CASE Spec software in our projects for generating traceability, gap and impact analysis reports. It is cost effective. You may find more information at http://www.casespec.net
brought to you by enabling practitioners & organizations to achieve their goals using: