Development of User Stories

After defining usable personas for the project, it's important to understand whether their needs as stakeholders would align with what the product can offer for them; the top priority in this section is to prioritize product features and align the product result with what a user would require.

We can use one of our existing personas to exemplify this:

"I am a Market Research Analyst, I want to access live population information quickly so that I can predict market trends easily to stand above any competing parties on the market."

For this specific example, the data provided could be insufficient to meet all of the user's requirements as market research would require a supporting data structure for spending habits / economic needs in the specified regions; though it is also important to recognise that we cannot provide everything that stakeholder could need for their job, it's a necessity to try and meet all their needs as effectively as possible and to our best efforts.

Defining Tasks as User Stories

Since the user is the focus of the project and its success, we can apply user stories to the issues used in project management interfaces like Kanban / Sprint boards.

This ensures that our work stays focused on the user's needs while being plausible with the resources and requirements for the project.

Functional Requirements & User Stories

We further expand on this by transforming our functional requirements into user stories which are also posted as issues: