Linking traditional detail requirements to user stories

[K Kaur]

Hi

I am working on a project where the analysis team has created full-fledged detailed requirements documents but the dev team is working in sprints. So we are tasked to convert those detailed requirements to user stories which is fine but the issue is traceability.

Programme wants to do traceability on detailed requirements whether they are fully met or partially met or not delivered.

I made the suggestion to create each detailed requirement as an EPIC and then divide that into user stories, when all the user stories in that EPIC are complete then we can say the requirement is completely met.

Problem is the way requirements are written, one requirement might not be contained enough and a user story may result in combing multiple detailed requirements. As there is only 1(EPIC) to multiple user stories linkage, this cant solve the problem we have. 

Sorry, whatever I have advised above cannot be changed as everything is already done and it's going to be very hard to change anything, the way programme is.

So just looking for any suggestions if there can be any fields which might help us with traceability. Currently, we are maintaining a sheet of all user stories and how much a user story is delivering for a detailed requirement and manually updating it.

Has anyone ever come across this?

Thanks a lot

KK

[Tony Pham]

Hi K,

Maybe you might think about using Feature as the top level of the requirements, then link each Feature to multiple Epics (if needed) and then each Epics can have multiple Stories.

Feature 1

    - Epic 1

           Story 1-1

           Story 1-2

    - Epic 2

           Story 2-1

[K Kaur]

Thanks for the response:)

It still does not cover the scenario where one story can be across two epics. That is the main problem.