title: What is a 'type of user' in a User story?
body: <p>I work as a UX-designer and have some experience with user stories from agile development projects where they were used to document functional requirements on the form:</p>
  
  <blockquote>
    <p>As a [type of user] I want to [goal] so that [reason]</p>
  </blockquote>
  
  <p>After a discussion with some colleagues we identified three different interpretations of what a [type of user] is supposed to be.</p>
  
  <ol>
  <li>For me as a UX-designer the [type of user] would represent a <strong>persona</strong>, an
  archetypical end user or customer built from user research on real
  people.</li>
  <li>One of the developers said the [type of user] was a <strong>role in the
  software</strong>, for example a medic or a sniper in a war game.</li>
  <li>A project leader said the [type of user] represented <strong>team roles</strong>
  in the development project, for example a tester or a developer.</li>
  </ol>
  
  <p>Who is right? If all of us are right, wouldn't this be a common source of confusion?</p>