This question is locked. New answers and comments are not allowed.
Hello,
we work like that:
Keyusers are responsible for defining requirements and testing them after they have been implemented by the developers. During the process of user requirement definition the key user's name is in the "assigned to" field. If a key user finished the definition of a user story and its is assigned to an iteration we change the user story state "to in development". Furthermore we assign the developer lead to the user story. (so he gets an email notification) If the user story have been implemented by the developers the "assigned to" should be changed back to the keyuser who defined the requirement and has the overall responsibility for the user story. Unfortunately the information who created the requirement is nowhere in the system anymore.
That's why I think it would be good to have 2 name/person fields at the user story.
we work like that:
Keyusers are responsible for defining requirements and testing them after they have been implemented by the developers. During the process of user requirement definition the key user's name is in the "assigned to" field. If a key user finished the definition of a user story and its is assigned to an iteration we change the user story state "to in development". Furthermore we assign the developer lead to the user story. (so he gets an email notification) If the user story have been implemented by the developers the "assigned to" should be changed back to the keyuser who defined the requirement and has the overall responsibility for the user story. Unfortunately the information who created the requirement is nowhere in the system anymore.
That's why I think it would be good to have 2 name/person fields at the user story.
- the person who has the overall responsibility for the use case (this person should have the possibility to the define in the setup if he/she would like to be informed always if the user story changes)
- the person who is assigned to the use case (and its current state, like development, testing) at the moment. In certain project stages (e.g. requirement definition) the responsible person and the assigned to person could be the same, during other stages they could be different (e.g. key user and developer).
Please let me know what you think about it.
Kind regards
Daniel