We have completed a user story for a sprint. Near the end of the sprint there was a new functional addition requested for the same user story.
Here the user story will remain the same. ie
As a <user> i want to <> so that <> will remain the same. Only difference is that there is a new value add that is to be done.
So should this be taken as a new user story for the next sprint or should this be taken as a backlog?
We have met the done definition we had for the user story and this new feature is a new requirement which wont have any change in the user story definition.
I am adding an example to make it more clear.
Take a feature say create profile, in that user can update his name,address, phone no, photo etc and its done. now if the customer wants to have facebook link or add country code to phone number, is that change request a new user story?
Best Answer
Just make a new story for your new requirement.
The question in your title may not have a generic answer, but let's consider your example:
Suppose you had a definition of done for this story, including the ability to edit and save the home address, telephone number, and a few other things. The Product Owner agreed, the story was estimated and pulled into sprint. Later it was marked as done and the story points were earned.
If you change this story, this will induce a scope change of the original story. It also shows a drop in your burndown, even while you delivered high-quality work as was agreed upon before taking it up. See this related question. Make a new story, accept that it's tiny, and pull it in when you need to fill up your sprint with something small.
Learn from this, and adjust your definition of done each iteration so that it includes a once-over before the end, to prevent trivial additions before it's too late.