SeekUX follows an approach related to personas, the user stories, to properly understand and illustrate in one or more sentences in the everyday or business language about the end user or user of the system, as part of his/her job function. In short we not only respect our client’s view but also take into account the perspective of the end user

Before designing or understanding any layout of a system, SeekUX experts follow the concept of user stories. User story is an agile methodology to identify a description of a website/mobile application from an end user’s perspective. SeekUX now only keeps in view the aspect of our client, but the end user as well because that’s whom the website or mobile application is basically made into existance for.

At SeekUX we make sure, the user story is written in the language of the customer, so that is is clear for the business and the development team, that what the customer wants and why he wants it? User stories are meant to be short, clear and concise, usually fitting on a sticky note or a note card. once a user story is made, we make sure it pases through the acceptance test. These acceptance tests are created to verify if the user story has been correctly implemented.

User Stories are also used instead of heavy specification documents, telling you what your customer wants from the system & how he wants it? They follow a very simple format:

As a <type of user>, I want <some goal> so that <some reason>

for example, if we take an example of some educational institute and it wants to offer some xyz facility for their students.

  1. A user story card is made at first. like “As a student I want to purchase a parking pass, so i can drive to school.”
  2. The system designer will further detail the user story on the back side of the card to make it more favourable for the developers to understand. i.e. parking passes be made monthly, annually etc. the experts brainstorm it with the product owner.
  3. At the third step, the function can be integrated in the system most suitable for the end user and the product owner. i.e. the students can purchase monthly parking passes online.

User stories help us in maintaining a strong communication bond between us and the product owner, because while the sticky note or note card being on the table or the noticeboard, it helps us properly discuss on what should be done and what is going on? These discussions are much more important and effective, than any requirement document. User stories is an agile requirement management tool.

User stories is a quick way of handling customer requirements without having the need to establish formalized requirement documents. user stories achieve this by:

  • Every user story has its own business value, which are easy to account and handle
  • Strong communication throughout the project lifetime, increases its overall business value
  • minor maintenance needed
  • considered at the time of use
  • allowing even complex projects to manageable small increments
  • specially suitable for projects with volatile of poor requirement understanding
  • easy to estimate development efforts
  • maintain a close customer/ stakeholder contact