Technical User Stories

Why is this important?

We can break your Business Requirement Doc, Design Spec Doc & Prototype into digestible pieces for your Development Team to handle. We can write User Stories with pre-conditions, acceptance criteria, and of course, what problem you're solving with context.

As a User, I want to...

This is a vital part of a proper Story to explain the goal that the developer is writing. It must express the problem you're solving for the developer to understand the WHY behind the Story.


A great User Story is going to contain this section to help QA write their acceptance tests and for the Dev to know what needs to happen before this feature can work.

Acceptance Criteria

How does your Dev or QA know if the code fails or passes? The User Story should explain what success looks like to make quick work for checking what they've built.


Thanks for submitting!