INVEST in good User Stories poster. INVEST acronym provides a guidance on how to write user stories the way they are supposed to be written.
Read more



Stories should be independent in a way that allows the easy prioritization and not overlap each other, even though it is not always possible.


Story is viewed as an invitation for conversation capturing what is desired, not a contract for features. It may acquire notes, test ideas etc. in order to meet a customer needs.


Value of a story is based on customer needs, what is an important factor while prioritizing backlog. Value needs to be considered especially when splitting stories so each story brings a value to the customer.


A good story can be estimated, meaning that developers can understand it and be able to implement it. Based on that it is possible to rank and schedule implementation.


Stories tend to be small. Usually at most a few person-weeks of work or one iteration length. Smaller stories are easier to estimate and further details can be added later.


Common characteristic of good requirements is testability. This applies for stories as well. Testability is also an indication of understanding the goal of the story.

Resources Mike Cohn: User Stories Applied: For Agile Software Development

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.