user_story

Capturing User Stories

By admin, October 18, 2013

Making IT part of your story.

As stakeholders of an endevour, we all have different perspectives, points of views and goals to achieves which are not 100% align with each other. As Business Analysts we want to achieve a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.

user_stories_roles

User Story technique allows us to capture the requirements and business needs for an IT system using everyday language. User stories are used in agile methodologies as the baseline for defining the business functions that system must provide. To facilitate requirements elicitation and management. It captures the ‘who’, ‘what’ and ‘why’ of a requirement in a simple way, often limited in detail by what can be hand-written on a small paper notecard. User stories are written by or for the business user as that user’s primary way to influence the functionality of the system being developed. User stories may also be written  to express non-functional requirements (security, performance, quality, etc.).

Communicating the needs with phrase as simple as

“As a <role>, I want <goal> so that <benefit>”

allows the stakeholders to understand their perspectives and bring consensus of the future solution.

Tell us your story, we will provide you with recommendation for a solution.