I’ve been meaning to write this post for a while. Recently, I saw a couple of blog posts on this topic (here and here) from bloggers I respect a lot. This spurred me to finally get around to writing this post.
This post is about using “personas” as a part of software requirements process. It’s not about marketing, sales or other activities.
At most companies, personnel with the job title of “product managers” or “business analysts” write Requirements Documents. These documents are then used by engineering teams to build and test the software.
There’s a school of thought that says that Personas are a very useful concept as a part of gathering and documenting requirements.
Having been a part of a few teams that tried to use personas in their requirements process – I consider personas mostly a waste of time. Here’s why…