First time use - Quickstart


  • We use the term User stories and Functional User Stories and Functional User Requirements interchangeably.  ScopeMaster is ideal for user story and backlog analysis.
  • ScopeMaster analyses every word of every requirement and sets of requirements.
  • The body of the user story should only describe the functional purpose of the story
  • Navigation is not considered functional and should be omitted from the body of the user story.
  • At this time ScopeMaster is less suited to Systems Engineering Requirements.

It's your first time with ScopeMaster, so here's what you need to do:

  1. Register - Once your application has been approved, you'll be sent the registration url.
  2. Register your organisation and email, then wait for the "activation" email to arrive
  3. Click on the link in the activation email to confirm your email address.
  4. Login
  5. review the tips on the home screen:

ScopeMaster Home screen

Click continue

Then follow the link to add the example set of user stories

Once added, you then need to Analyse the stories, so click on the analyse button:

Sit back and watch ScopeMaster do the hard work!

We recommend that you spend at least 20 minutes exploring and modifying the example user stories, try making changes and then view them in the various different analysis views available:

They have been carefully created to help you understand the different types of user story that you might encounter.

You are now ready to create your own set of user stories:

Start Refining and Follow this Sequence

  1. Resolve Ambiguities, user stories with no clear functional intent

  2. Resolve inconsistent user names

  3. Resolve inconsistent object names

  4. Resolve individual requirements completeness, use suggested elicitation questions.

  5. Resolve missing requirements, use the CRUD table

  6. Resolve missing requirements, use the Use Case Model diagram

  7. Ensure Each requirement is complete, use the elicitation suggestions and use case diagram.

  8. Ensure design validity use the Suggested Class Diagram

  9. Optional - organise user stories using labels.

  10. Organise user stories into Epics/capabilities.

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