Monday, 28 November 2016


A persona describes one category of the target users of your system as a fictitious but realistic person with goals and needs.

It is useful because it summarises the user, their role, their skills and aptitudes, their preferences, and their goals. Personas give rise to user stories, and keep the user stories focused on the goals of real users.

The persona needs to include a name and a picture, so that developers, business analysts, and testers can relate to it as if it was a real person. 

It should include the following details:
  • their demographic characteristics (e.g. age, disability) that might affect their interaction with the product, and their requirements in using it
  • their role in using the software (e.g.  admin, editor, contributor, supervisor)
  • what their job title is
  • activities they do in their spare time which might affect their performance (either beneficially or adversely)
  • their goals in using the software
  • common tasks they will want to carry out using the software
What problems does the persona have that the software will solve? What benefits can they achieve using the software? Why do they want to use the software?

Further reading