Topics
How to fine-tune user story writing
1. Default settings
Initially, you can ask StoriesOnBoard AI to write you the standard user story format by hitting the SPACE button in a new line.
In this case, you'll get the well-know user story format as a preview, so you can instruct StoriesOnBoard AI to refine the result before inserting it into the description.
Most common refinement instructions:
make it simpler
make it longer
change user persona to X
2. Custom templates
If you want to stick to another structure or wording, you can teach it to the AI assistant by opening the AI menu (green spark button in the top right corner) and selecting the "Update AI templates" menu.
As you can see, you can select three predefined and commonly used user story formats.
As a user...
In the role of...
Given...when...
On top of it, you can enter custom content in the input field. This input can be a template (without content), but you can also enter an example, plus you can add instructions as well, like writing a regular prompt in a chat window.
Goal-oriented format
I want [feature/action] because [reason/benefit].
Job-to-be-done format
When [situation], I want to [motivation], so I can [desired outcome].
Problem-focused format
As [role], I'm facing [problem], so I need [solution].
Scenario-focused format
In [scenario/context], as [user], I expect [action/feature], in order to [purpose/outcome].
Capability-focused format
As [user type], I should be able to [action], enabling me to [achieve specific outcome].
Hypothesis-driven format
We believe that [action/feature] for [user] will result in [outcome]. We will know we're right when [measurable result].
Direct statement format
[User] can [do action] to [achieve benefit or solve a problem].
Persona-driven format
[Persona name/type] needs [feature] to successfully [achieve objective] because [reason/context].
Acceptance-focused format
For [user type], [feature/action] must [criteria] to ensure [specific benefit/outcome].
Context-action-result format
In context of [situation], when the user [action], then [result/outcome] should happen.
How to take the most out of acceptance criteria writing
1. Default settings
Writing acceptance criteria is the second most used AI feature in StoriesOnBoard, which is why we dedicated a standalone function for that. By default, it comes up with the most common acceptance criteria groups and adds a few criteria to each group.
Similarly to user stories, as step 2, you can extend the result in the preview mode by instructing the AI to
collect more criteria into a selected group
collect more criteria into all groups
add new groups and criteria
add a group that came into your mind and would be important
2. Custom templates
If you have already made up your own acceptance criteria structure, you can add your template or select one of the proven pre-made templates.
Here are some ideas how to customize the template:
add your instructions, like "consider adding detailed criteria for input fields"
highlight numbering in the example like "AC1, AC2..."
add fix groups like "technical requirements" and "non-technical requirements"
ask the AI to brainstorm groups based on the content by mentioning just "acceptance criteria group."
In the preview mode, you can still ask the AI to write more content as described above by extending the criteria or the groups
3. Writing acceptance criteria in two steps
If you have a specific need around acceptance criteria that can't be managed with the above-listed methods, try to use the two-step method.
For example, if you need a very specific and detailed list of acceptance criteria, then you'd set up the groups and ask only the first AC, but in a strict way, and ask the AI to write the other criteria in step two in the preview mode.
Provide AC only for the first group, other groups should be just listed.
# Acceptance criteria
## group1:
AC1 - Manage favorite product categories
- There is a section on the customer account page for favorite categories management
- The customer can:
- Add new product categories to their favorites list
- Remove existing product categories from their favorites list
- View their current list of favorite categories
- Once a category is added to favorites, products from that category appear in the “Recommended for you” section
## group2
## group3
How to write specifications with less effort
If you want to speed up the specification process, especially for simple, common user stories, then you can use the story template function.
To get this feature, you should go to the story map settings in the top right corner, then select the Story templates and AI templates section and enter your content you want to add to each user story (story, AC, DOD etc.)
After switching it on, the template content will be added to all newly created cards. As we mentioned previously, the AI reads the user story card's content so it can follow this template. The only thing you need to do is hit the SPACE button and ask the AI to write the whole specification with something like this:
Write the specification based on the given template
...and the AI will write content into all sections you added to the template.
Example in the screenshot
User Story Title:
[Brief, descriptive title of the user story]
Story:
As a [type of user], I want [an action or feature], so that [benefit or value gained].
Acceptance Criteria
[Criterion 1]
[Criterion 2]
[Criterion 3]
Detailed Description
[Provide additional context, details, and business rules that clarify the purpose and functionality of the user story.]
Technical Notes/Dependencies
[Any technical details or dependencies on other stories or systems.] [List related user stories or tasks that must be completed first.]
Priority and Estimation Priority:
[High/Medium/Low] Estimated Effort: [Story points or estimated hours/days]
Questions/Clarifications [Open questions or items that require clarification from stakeholders.]
Of course, in the preview state, you can ask the AI to extend this or that section. Moreover you can do it in multiple steps, because there's no limit for refining the AI results.