You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project does not force the specification of acceptance criteria. Many (most?) user stories won’t have acceptance criteria specified in detail at the early stages. That detail will be added later when the story is being discussed with the team, and sized. But the project does still print the header. It’s just clutter to even bother to print “Acceptance Criteria: \n None Specified” so suppress it when there is no acceptance criteria specified.
Maybe these issues should be written as user stories ;-)
The text was updated successfully, but these errors were encountered:
The project does not force the specification of acceptance criteria. Many (most?) user stories won’t have acceptance criteria specified in detail at the early stages. That detail will be added later when the story is being discussed with the team, and sized. But the project does still print the header. It’s just clutter to even bother to print “Acceptance Criteria: \n None Specified” so suppress it when there is no acceptance criteria specified.
Maybe these issues should be written as user stories ;-)
The text was updated successfully, but these errors were encountered: