Posts Tagged ‘Requirements capture’

Persona’s help to focus on who the product is aimed at.
Ask questions like:

  • What does this type of user need?
  • What do they want?
  • What do they like?

The answers can help to keep the team focused on who they are building a site for, ensuring that the user is at the forefront of the peoples mind when making design and build decisions. (more…)

Read Full Post »

‘Stories’ are a great way to describe requirements. In defining these stories you also define tasks that need to be completed by the development team and give the tester an idea of what they need to test. The writing of Stories should help keep the understanding of what a task is simple and accessible to all. Written in non-technical language they follow a simple format:


As a…

I want…

So that…


For example:

Add ‘Artist’ filter to search.

As a user

I want to filter my search results by ‘Artist’

so that I find the CD I want more easily.


Expressed like this anyone in the team or wider business can discuss the task without specific technical knowledge.


Read Full Post »

When capturing requirements from clients or stakeholders a good way to start  is to hold a brainstorming session.  Asking people to contribute to a brainstorming session for a new product or feature is a great way to gather information and get people involved and emotionally invested in the project. Invite all stakeholders and key representatives from each area of the company that the product will effect. Try to ensure that everyone invited gets the opportunity to contribute. The greatest insight can come from the most unlikely of participants and gathering input from every department will help to get a more all encompassing view of what is required.


Read Full Post »