review and redefine user histories

Last post 06:19 am July 10, 2014 by Ian Mitchell

2 replies

01:20 am July 10, 2014

Hi.

What happen if a user history is done and next sprint the PO, realize that it has to be enhanced with some adds, more functionality that impacts in the DB too. We have to create another US?... brings the US back to board and add the new activities? We have to do anything else?

thanks in advance.

Ilia Pavlichenko

03:36 am July 10, 2014

Story consists of 3C - Card, Conversation, Confirmation and US "dies" is the Sprint when it's Done and Converstation is over. Thus formally a new story should be created even if it's similar (iterative devolopment).

Ian Mitchell

06:19 am July 10, 2014

NB this is true even when work associated with an old story is found to have defects. New ticketed work can be raised *against* the old story (i.e. referencing it), or you can duplicate the story and give it better acceptance criteria. A story can be cloned and improved but never brought back from the grave. Once its conversation is over, a story is finished.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.