Best Practice to link user story from TFS into Pega
Hi All, I'm working with a client, who is operating the Agile project management using Microsoft Team Foundation Server (TFS) and using Pega for application development. There is a need to have good linkage between the user stories from TFS with the Pega specification and application rules, so we can achieve better traceability. I'm seeking some advice on best practice, if you have come across similar situation and how you've handled it. Thanks in advance for the help!
Tata Consultancy Services
IN
Hi Arnab, We also have a similar challenge. Please let me know if you were able to get a solution for the problem you have posted?
Deloitte Consulting
US
Hi Arnab ,
I am also looking for an advise on similar grounds , please let us know if you were able to find some solution. I'll check with my resources too.
Thanks
Saumya!
Achmea
NL
Hi Arnab and other posters,
We have no direct links to TFS, but a practice is to make an requirement rule for each TFS Story and use the field 'External req. ID' to store the identifier of the TFS Story.
After this you can link your specifications to the requirements. It is not ideal, but at least you have tracability.