Product Vision & User Stories

It's important to create a product Vision, which will act as a guide for the team. This is created by the product owner at the very beginning of the project.

Included in this is the Minimum Viable Product / MVP - This involves developing the product enough for it to be released and receive feedback.

benefits of this are:

allows quick delivery and feedback reduces scope creep

Must also create themes which could be for example:

Profile delivery Payment

then after the themes are identified, they are the broken into features

Once the features have been defined, the product manager can select those which are needed for MVP. The others aren't required to complete the initial release

The product manager usually creates the user stories as it's his responsibility to add value to the product.

Each interaction the user has with the product is called a use case this provides the basis of the user story - this tells the team how they're going to use the product.

a user story provides detailed information to let the team know exactly what to deliver.

this is the format thats usually conformed to:

, I want , so that

This is an example of a functional user story. however, each story must have acceptance criteria.

Acceptance Criteria

the AC is usually created or generated by the team as a collaborative effort. Each user story has a unique AC.For example, the AC could be that the customers name is captured and saved, alongside their email address and telephone number