gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Text added (#32163)

Browse Source 
* Text added

* Update index.md
This commit is contained in:
Tosson
2019-05-17 03:32:56 +02:00
committed by Paul Gamble
parent 93214303d4
commit a0d2c5ccc2
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
guide/english/agile/acceptance-criteria/index.md
View File

@ -34,7 +34,8 @@ Acceptance criteria can be viewed as an instrument to protect the Delivery Team.
Consider the following situation: when accepting the user story, the Product Owner suggests adding something that was not in the scope of the User story. In this case the Delivery team is in the position to reject this request (however small it might be) and ask the Product owner to create a new User story that can be taken care of in another Sprint.
#### More Information
In the agile approach, the aim is to focus more on people and communication rather than process and tools.
Nomad8 provides a [FAQ on Acceptance Criteria](https://nomad8.com/acceptance_criteria/)
@ -43,3 +44,5 @@ Leading Agile on [Acceptance Criteria](https://www.leadingagile.com/2014/09/acce
Ruby Garage on [Writing Acceptance Criteria with Gherkin Syntax](https://rubygarage.org/blog/clear-acceptance-criteria-and-why-its-important)
Elijah Valenciano [The Acceptance Criteria for Writing Acceptance Criteria](https://medium.freecodecamp.org/the-acceptance-criteria-for-writing-acceptance-criteria-6eae9d497814)
[Agile Manifesto](http://agilemanifesto.org/)