Career Forums

Modern Analyst Forums Business and Sy... General Traceability through Project Lifecycle

11/9/2010 6:32 AM

	brouilt1
1 posts

Traceability through Project Lifecycle

Within our organization it is part of our process to complete requirements traceability via a traceability matrix (manual). Completion rate is high as it relates to tracing requirements to testing artifacts (ID's), but we have this gap in between the two process areas that continues to exist. We haven't received support from a leadership perspective to include traceability for design and build artifacts. The expectation of our process is to identify the section or sub-section of the deliverable for design, and the program, screen, report name, etc. for the build. We have provided value add looking using the perspective of various roles, but the case for change apparently hasn't been strong enough. Is anyone willing to share data, information and/or success stories from organization or that you've come across in the past. Any assistance would be much appreciated!

11/29/2010 3:01 AM

	Craig Brown
560 posts
www.betterprojects.net

Re: Traceability through Project Lifecycle

What are you trying to achieve?

I think that what you should be doing here is reviewing solution designs, (or iteration plans) and recording what is being delivered by the (planned) solution. As the BA it's your job to reconcile the solution design, (and in my view also the delivered solution) back to the requirements.

The developers/designer should enable this by mapping planned features and components back to your requirements in their design docs