Skip to main content

Validation user stories

Last post 02:51 pm November 19, 2013 by Ian Mitchell
3 replies
12:28 pm November 19, 2013

Hi

I'm having some trouble figuring out how to handle validation using user stories. I've come up with the following approach but I'm not sure if it is correct.

Is the following a valid user story?

As a Comptroller
I want to prevent a customer from being disabled when it has unpaid invoices
So I can ensure that the customer pays their invoices

If not, how would I ensure that this is properly tracked?

Thanks


01:06 pm November 19, 2013

As an administrator who disables customer accounts,
I would like to be prevented from disabling a customer account if the account has unpaid invoices
so that customers have a chance to pay their invoices.

Acceptance Criteria: display a message to the administrator with information about why the account cannot be disabled.


01:07 pm November 19, 2013

Thanks


02:51 pm November 19, 2013

Perhaps this can be written as a specific acceptance criterion for a more general user story, e.g.

Given a customer account
Where at least one invoice is unpaid
Then the account will be enabled


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.