User Stories

Format

Once we had identified the rent journeys and epics for MVP, we set about breaking them down further into user stories in this format:

As a [User], I want to [Action] so that [Expected Outcome].

For example: As an agent, I want to send a Payment Methods link to a caller so that they can learn how to pay their rent.

We considered wants and needs from both agent and caller perspectives but wrote stories from one perspective or the other to avoid duplication. For example, and using the story above, we did not want a parallel description outlining that a caller wants to receive a payment methods link so that they can learn how to pay their rent.

True to Agile methodology, we kept each story lean so that we could break down and prioritise later on.

Backlog

Each story was entered into the backlog of our Jira software, which we are going to use to manage the sprint planning and design and build of the service.