Connecting User Stories to Process Models Copy

Whether you are agile or not, connecting user stories to process models is a great analysis exercise to find requirements gaps and frame up requirements from a user point of view. You can also think of user stories as high level stakeholder requirements.

As a <who>, I need to <what>, so that I can <why>

Let’s look at what the user stories are from our cart process model:

As a shopper, I want to place an item in a cart, so that I can make a purchase

As a shopper, I want to view my cart, so that I can see what I am spending

As a shopper, I want to edit my cart contents, so I don’t buy something I don’t not want

As a shopper, I want to confirm my cart content, so that I can checkout

As a shopper, I want to check out, so I can get my items delivered soon!

Now, these can also be broken down, or split even further. As you identify them all, the details start pouring into your mind. Where you thinking about these sub-stories, or story slices?

• As a shopper, I want to edit my cart contents, so that I can see what I am spending
  • Edit the quantity of each item
  • Remove an item

• As a shopper, I want to confirm my cart content, so that I can checkout
  • Confirm my items
  • Confirm my shipping address
  • Confirm my shipping choice

It’s funny how the act of writing them out helps us analyze and find the missing sub stories!

Now, these are requirements statements that we can have some serious conversations about with the team and stakeholders.

User focused!

Plain language!

What it takes to make sure we build the user what they need!