Ticket Acceptance Criteria
As an engineering manager I want well written acceptance criteria so that completion for a task is well understood, being met, and providing desirable output. This will save time and money in additional effort being required for additional tasks or fixing undesired behavior. It will lead to happy stakeholders that are having their needs fulfilled.
- The stakeholders have read and agreed to acceptance criteria to meet the desired outcome.
- The acceptance criteria is finite (constrain the story to be specific and measurable) and not open ended
- The acceptance criteria will be reconciled with requirements
- Any combination of acceptance criteria does not contradict any other combination
- The output will match or otherwise denote difference between mock-ups and screen flows that were included at the creation of the task
- Demonstration of the acceptance criteria being met will be done as part of completion
- The acceptance criteria should define every desired outcome explicitly and eliminate undefined implicit behavior
- The acceptance criteria must be able to be used for test plan and creation of acceptance tests (a combination of automated and manual tests) independent of development
- The meeting of acceptance criteria does not eliminate the need for code reviews, automate build and test, and other similar processes
- The acceptance criteria is quantifiable and measurable. It should be able to be looked at it and verified without doubt of it is actually done.