Project User Stories

User Stories are the details of your Project's requirements and give Teams a basis on how much work is required to accomplish your project's goals. When you enter a new User Story, you will see a modal dialog like the following.

A best practice for naming User Stories can be US1, US2, etc. However, you can name the User Story as you wish.

The Story Description starts with a template in User Story syntax and users are encouraged to use this syntax as it makes your requirements as clear as possible to the Team members. You can use whatever text you are comfortable with for the story description.

Acceptance Criteria

Acceptance Criteria are a set of requirements that must be met before the User Story can be considered complete by the Team. To add criteria, click the Add New Criteria link.

A good practice for naming criteria is AC1, AC2, etc. Again, you can name these as you wish. The Scenario Description starts as a template for Gherkin syntax, but you can use whatever description you desire. Gherkin syntax is encouraged.

Be sure to save

Again, be sure to save your project as a draft by clicking the button when you are done editing.