18
votes
Accepted
What is the difference between acceptance criteria and the definition of done?
The acceptance criteria you have listed are really a mixture of stories and tasks.
Given your example story:
As a user I want to register and log in so that I can register on the application and ...
- 19.1k
7
votes
How do I define acceptance criteria for subjective outcomes?
Why Your "Story" Isn't Testable
As a small business owner
I want simple and easy instructions to follow for any recommendations to my website
so that I understand what it is I need to do and ...
- 49.5k
6
votes
Accepted
Is "Replicate X visual feature from Y app" a valid acceptance criterion
The concept is valid, which is to seek a result based on a reference. But of course it needs to be broken down into measurable points.
For example: the acceptance test will be like:
Achieve the ...
- 817
5
votes
How to track Incomplete acceptance criteria in JIRA
As you are referring to sprints and user stories, I will assume you are using the Scrum framework.
Within Scrum, there is no such thing as a partially complete user story. A user story can either be ...
- 2,730
5
votes
Which tense is correct when describing acceptance criteria in scrum stories?
Interesting question.
While it really does not matter I believe that linguistically it needs to be present tense.
It can never be past tense as it is describing something that has not been done ...
5
votes
What is the difference between acceptance criteria and the definition of done?
The acceptance criteria are to verify the new feature is working as expected by the stakeholders. They are better called Business Facing Tests.
A business-facing test is a test that's intended to ...
- 5,533
5
votes
In Scrum, who is responsible for not-meeting UNexpressed acceptance criteria?
Scrum is based on an empirical process control system. It assumes that not everything is known and that knowledge will emerge over time. Trying to specify every acceptance criteria in exact detail may ...
- 1,250
4
votes
Should developers be talking to users during Story planning / refinement?
In certain situations I think they should, but there are a lot of caveats and gotchas to it. Let me list out reasons I have done it, and also times when I would not do it and maybe that will help as ...
- 395
4
votes
Should I specify user story acceptance criteria in Given/When/Then format or checklists?
It depends, does it help the team in better using them as requirements and does it improve communication with stakeholders? Then yes. Just discuss with the team which they think gives the most value ...
- 5,533
4
votes
Accepted
Should developers be talking to users during Story planning / refinement?
Yes, ofcourse, why should the development team settle for second hand information. Self-organizing teams should get the information from the source!
I really like this item from the Cargo Cult Agile ...
- 5,533
4
votes
Who should write Acceptance Criteria in a project delivered using Scrum Methodology
It should first be said that there are no hard and fast rules on this. That said, the most successful teams I see operate as you describe. Specifically, the PO creates a backlog item with initial ...
- 16.8k
4
votes
Issue found while testing but scenario not mentioned in acceptance criteria
Before We Dive Any Deeper...
You don't have a single problem, you have many. Aside from lacking a cross-functional team that fully collaborates, the two biggest process problems appear to be:
The ...
- 49.5k
4
votes
What's the point of having acceptance criteria when you have defined in a design document what you want done and how?
There's no one form for acceptance criteria. If your document describes what needs to be done in sufficient detail to write tests against, then that document is your acceptance criteria.
Keep in mind ...
- 18.8k
3
votes
Accepted
How to track Incomplete acceptance criteria in JIRA
Usually, we clone the user story and move it to the next sprint for tracking.
Don't do that.
The story isn't done. If you put it to Done and clone it, your velocity will be messed up. It will look ...
- 14.8k
3
votes
Is this good acceptance criteria, in a JIRA?
Good Acceptance Criteria cannot stand alone. It has to be derived from the requirement description - e.g. User Story. Therefore, a good requirement description is the starting point.
However, ...
- 238
3
votes
Who should write Acceptance Criteria in a project delivered using Scrum Methodology
The Acceptance Criteria is about usability. When a feature meets the acceptance criteria, then for sure it can be used. The acceptance criteria is as clear as black/white.
See this video, please: ...
- 121
3
votes
How do I get client to participate in acceptance testing?
A viable strategy could be the following.
First, make him truly aware of the delay he's causing: you might produce a Cumulative Flow Diagram to point out the slowdown (quite easy given that you work ...
- 165
3
votes
Accepted
Acceptance Testing fails on owners machines only
Actually I think you see this more with web applications vs 'normal' apps. Clients can have a whole host of browsers/plugins/firewalls etc which you dont have in your test enviroment.
In regards to ...
- 926
3
votes
Who else can test in absence of QA?
The user story is closed when the acceptance criteria is met. So if any team member can check if the story acceptance criteria passed or not, then yes they can close the tickets.
If any technical ...
- 817
3
votes
In SAFe (Scaled Agile Framework); are there any guidelines around what feature acceptance criteria should look like (eg SMART)?
I can't really answer this from a SAFe perspective since I'm not very familiar with the framework, but I'll add a general answer nonetheless because I sense some confusion in the way the question was ...
- 14.5k
3
votes
What's the point of having acceptance criteria when you have defined in a design document what you want done and how?
You can of course use a design or requirement document as the basis of your acceptance criteria. No need to record that information again on a story if you already have it. However, change control can ...
- 6,081
3
votes
What to do with a branch and card when a task meets the acceptance criteria BUT user testing reveals it's not acceptable?
I also believe that the most concerning part is:
the PM has decided that whilst the AC has been met, the code should not reach production as it does not deliver a suitable enough value to our user.
...
- 14.8k
3
votes
Is given-when-then a standard for how acceptance criteria should be worded?
Requiring a specific structure for acceptance criteria is often wasteful, so I encourage teams to understand different structures for capturing their units of work, their acceptance criteria, and ...
- 18.8k
2
votes
Accepted
How do I define acceptance criteria for subjective outcomes?
I think subjective user stories are a recipe for scope creep. If you want to focus on business owners requirements & make something that is measurable then I would fall back on a framework like ...
- 1,383
2
votes
How to organize effective iteration demo in outsource project?
On our project, we hold virtual demos for clients at the end of releases all the time. We have a pretty standardized format for this, that usually works pretty well.
First of all, you want to make ...
- 221
2
votes
How do I get client to participate in acceptance testing?
I think the question is why he's not reviewing the stories. I'd use the lean approach that Toyota developed: help the client eliminate his own bottleneck.
Possible reasons:
he doesn't have dedicated ...
- 315
2
votes
JIRA query to find all issues where acceptance criteria is less than 20 characters
Jira does not offer any native character count function. A few alternatives:
Export to CSV and filter the data in Excel
Use Jira API
Use ScriptRunner, as you can see here: issueFunction in ...
- 8,549
2
votes
Best practice for Service Acceptance criteria in User Story format?
A user-story is a description of a Requirement.
I think what you are concerned with is about describing a Specification.
Specifications are not rendered as user-stories; they can (and should) be ...
- 61
2
votes
In Scrum, who is responsible for not-meeting UNexpressed acceptance criteria?
The product owner is responsible for defining all the items in the backlog with enough detail for the team to be able to work on them. Acceptance criteria is part of those details. The product owner ...
- 14.5k
2
votes
In Scrum, who is responsible for not-meeting UNexpressed acceptance criteria?
If the quality of the product isn't good, is the Scrum Team fault
It is never the stakeholder fault!
According to the Scrum Guide (2019), the Scrum Reviews are
"informal meetings" in which the ...
- 141
Only top scored, non community-wiki answers of a minimum length are eligible