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.
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]