Does RTC support vesioning of User Stories?

Tatiana Khramkova (8●1●1) | asked Jul 07 '14, 1:45 p.m.

We document User Stories (USs) as work items (WIs). When a US is implemented and the WI is closed how change to the US (new version of that US) can be captured in RTC? Or what would be an appropriate way to maintain USs with version control?

Accepted answer

permanent link

Chris Newton (30●3●6) | answered Jul 07 '14, 4:16 p.m.

Once a user story has been implemented and accepted, I don't think you'd want to make changes to that user story. You could create an entirely new user story that captures the new functionality and link it to the original. If the user story hasn't been accepted/tested, then changes to the story are captured in the history tab of the work item.

Tatiana Khramkova selected this answer as the correct answer

Comments

Tatiana Khramkova commented Jul 07 '14, 5:22 p.m.

Chris, thank you for your answer. Unfortunately you confirmed my understanding. In this case if we cannot update a user story with an applicable change (create a new version) rather need to create a new user story, then how can we create a baseline at the end of the project (or a release)? Will that product baseline include all the user stories that were written / implemented? If yes then we’ll have potentially conflicting user stories which will be not very useful for maintenance. Should we consider using other tool for requirements management (especially if requirements is our deliverable)? If links in RTC points to the latest version of a user story, would tool help to pick those latest ones for the baseline? Or that will be a manual effort? Any thoughts?

It's all about the answers!

Related questions

Does RTC support vesioning of User Stories?

Accepted answer

Your answer