Writing user stories

Focus on Functionality

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

You are not required to use the "As a....I want....so that... structure".  However you do need to write your user story to ensure that the meaning is clear. 

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.

Avoid too much detail

Focus on the the Subject, Verb, Object structure. Don't include too much detail about navigation or object attributes.

Square Brackets:  [exclude from analysis]

If some phrases are misleading ScopeMaster and yet feel they are important to retain.  Use square brackets to exclude them from the analysis. e.g.  I am a supervisor and I need to update profiles [on behalf of users over the phone]

Curly Braces:  {custom object}

To force ScopeMaster to interpret a phrase as an object of interest (data being maintained by the software) just put inside curly braces.

Double Curly Braces:  {{custom user}}

To force ScopeMaster to interpret a phrase as a user just put inside double curly braces.  

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