Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

user story feedback

Last post 04:49 pm July 17, 2020 by Daniel Wilhite
1 reply
12:02 pm July 17, 2020

This user story sounds good, right? "As a participant, I want to get #21KK14 notification when submitting my option, so I am notified that my vote was sucessfully submitted." 

BUT: a participant would never know the code of a notification. It would be better to state: As a participant, I want to be notified (within a certain timeframe) that my vote was processed, so I know that my vote was succesful."


04:49 pm July 17, 2020

The goal of a User Story is not to explain something to the end user, it is to describe the problem that needs to be addressed in as detailed and exact language as needed in order to successfully do so. If the participant can receive multiple notifications associated to the option, stating specifically which notification is important helps to clarify the problem. 

If we want to get picky, your "within a certain timeframe" is too ambiguous unless you are going to clarify that in the Acceptance Criteria.  For example, the Development Team could satisfy that criteria by giving the participant notification 3 years after their vote has been processed.  Would you agree that solution is satisfactory?  

I will also add that the two story statements you provided are different problems.  The first is to notify that "my vote was sucessfully submitted" and the second is to notify that "my vote was processed".  From my knowledge of processing things, submitted and processed are two different operations.  In reality I would see your first story as part of the solution of the second.  Because as a participant, I'd like to know my submittal was received and that the vote has been processed.  Especially if there was a possible lag between the two. 


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.