O'Reilly logo
  • Melissa Thornton thinks this is interesting:

Role Modeling

Next, the team considers each role and adds detail to the role cards. The details will vary based on the domain and the type of software but good, general factors to consider include:

  • The frequency with which the user will use the software.
  • The user’s level of expertise with the domain.
  • The user’s general level of proficiency with computers and software.
  • The user’s level of proficiency with the software being developed.
  • The user’s general goal for using the software. Some users are after convenience, others favor a rich experience, and so on.


Cover of User Stories Applied: For Agile Software Development


Role modeling