How To: Working with user stories

Note: Some of the functionality in this article was introduced with the release of Hansoft 9.1

User stories are a very powerful tool when working with requirements in product development. This article describes how to work with them and assumes you have a basic understanding of what they are.

Step 1: Create a template for user stories

Note: Only main managers can control the column settings and do this.

Now for every new user story this information will be pre-filled for the user adding the user story.

Step 2: Add user stories

Note: Any user with a section delegated to them or that are members of sprints can create user stories in Hansoft.

Step 3: Defining how you work with user stories

The common pattern for user stories is As a <user> I want to <action> so that <purpose> and the true beauty of it is the simplicity and that it captures three key attributes: for who (persona), what (feature) and why (value).

Acceptance Criteria

An acceptance criteria is often needed to define what must be fulfilled for the user story to be considered completed. These are typically testable bullet points that are captured in a dedicated field in Hansoft and controlled by the Product Owner.

Note: Only main managers can setup new columns.

Quality of user stories

A user story should follow the principles of INVEST (independent, negotiable, valuable, estimable, small enough and testable). You might want to consider having a check box to mark that it fulfils these criteria:

Definition of Done

In addition all user stories share a Definition of Done - the steps needed for the user story to be considered done-done (both from a product development perspective as well as the customer perspective).

This can be represented as a pipeline in Hansoft that main managers can configure.