Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

review and redefine user histories
Last Post 10 Jul 2014 05:19 AM by Ian Mitchell. 2 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
aldo daniel lavin
New Member
New Member
Posts:15
aldo daniel lavin

--
10 Jul 2014 12:20 AM
    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
    New Member
    New Member
    Posts:71
    Ilia Pavlichenko

    --
    10 Jul 2014 02:36 AM
    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
    Veteran Member
    Veteran Member
    Posts:1451
    Ian Mitchell

    --
    10 Jul 2014 05:19 AM
    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.
    You are not authorized to post a reply.


    Feedback