Close popover
Lithosh Thomas (LithoshT4530)
Senior Consultant
LithoshT4530 Member since 2016 5 posts
Posted: January 8, 2019
Last activity: January 24, 2019

Maintenance/Change Management of User Stories in Agile Work Bench


I was going through the Agile work bench in 7.4 to capture the requirements as user stories and features. I understand that we can design the feature in a way that it mimics our case life cycle and have the user stories mapped to the case.
The question I have is related to the maintenance/change management of the user story. For example, I have a feature F1 and a User Story US1. In sprint 1 we have implemented the US1 and later it was found out that we need to make significant changes in the implemented user story. Now we cant go back to the implemented user story since it is already marked as Implemented. In this case I have to create a new User story US2 under F1 to change few functionalities done in US1

Down the line when application is huge and when these user stories are imported the user is presented with US1 and US 2 but its hard for the user to understand which one is implemented and which among the user stories functionalities are implemented. Here is where I dont understand how we manage the user stories. This is not an issue with use case model because the BSA always overrides the use case with the changes and end user is provided with the upto date information instead of having multiple duplicate use cases.

To All Pega BSAs, How can we have proper change management using user stories and features?

Project Delivery
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.