Writing user stories

Focus on Functionality

ScopeMaster analyses the functional part of the user story, the who and what.

ScopeMaster is an intelligent analyser that interprets the functional intent of each requirement.  You are not required to use the "As a....I want....so that... structure".  Write your user stories ensuring that the functional meaning is clear, concise and complete.

The  body of the user story should only contain the user and the functional phrases.

You will need to experiment with phraseology a little at the beginning.  You will soon be writing good quality, clear, concise, measurable, testable user stories much faster than before.


Use appropriate/ unambiguous verbs

There are a limited number of verbs in English that are clear and unambiguous when it comes to describing moving data. We encourage you to use these verbs.  User verbs with meaning regarding data movement such as update, insert, view, lookup.  Avoid verbs such as consider, see, wait, align, distribute.

Avoid too much detail

Focus on the the Subject, Verb, Object structure. Don't include too much detail about navigation or object attributes.  A good example might be.  "As a visitor, I want to search for products"

Square Brackets:  [exclude from analysis]

If some phrases confuse the analyser, you may include them by surrounding them with square brackets.  Use square brackets to exclude useful information from the analysis. e.g.  I am a supervisor and I need to update profiles [on behalf of users over the phone]

Custom Object Names

To instruct ScopeMaster to interpret a phrase as an object of interest (data being maintained by the software) just add the phrase the data dictionary  (Users and Objects), then reanalyse each user story that contains that word (or analyse all). 

Custom User Names

As with custom objects, define them in the data dictionary, then reanalyse the user story.

Curly Braces:  

The use of curly braces {object} and {{user}} to nominate objects and users will be deprecated in Q2 2023

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us