This month’s meeting is about creating and generating Personas to help gather and make sense of complex software requirements. Personas provide a named profile for a user type. This profile is useful for describing a user in detail, and generating and understanding user stories and the overall requirements.
Presentation: WHO ARE THE USERS IN YOUR USER STORIES ??
“As a [user], I want to…”
If you’ve written requirements as stories, you are probably very familiar with this phrase, but who exactly is the user we are talking about?
Very often we resort to generic role titles.
You’ve likely found that many conversations still revolve around, “I think we should” rather than about what your target users would need.
In the absence of having real users give feedback on a regular basis, we often resort to abstractions such as market segments, but it is very difficult to make detailed design decisions based on broad segments.
Personas solve this problem by creating a realistic profile that represents a segment.
In this presentation, I’ll outline what personas are, why they are useful, and how to create them.
By the end, you will have techniques you can use immediately to create assumptive personas and start focusing your team.
About The Presenter:
Jeremy Kriegel has been designing great user experiences (UX) for 15 years. Just as we need to understand the needs and context of users to craft a design solution, Jeremy believes that success also requires us to look at the business context to craft an appropriate design process.
From start-ups to Fortune 100 companies, as a consultant or on an internal team, he has seen a lot of different scenarios that each required their own approach. He brings this diversity of experience to bear in adapting UX to agile methodologies, finding the balance appropriate for each business.
Currently, Jeremy leads the UX team at Cambridge Interactive Development Corp, the company behind Everest Poker and the Everest Gaming suite.
There is no related post.