basysKom Toolbox

20 – Agile – The story

A story describes what needs to be done


Structured way to describe what needs to be done.


A story is the most important artifact in an agile workflow.

As a USER I want to do SOMETHING to achieve this GOAL

A good story is independent, negotiable, valuable, estimable, short, precise, testable and fits on a small piece of paper.

Just something very important to note: A story does not substitute a meeting between the Product Owner and the team, but document the result of such meetings.

The writer of a story is the product owner. The product owner needs to ensure that the story fulfill the definition of ready. In order to achieve this it became a useful tool to implement a regular meeting every week to review the backlog together with the team and to refine stories together. Such a meeting can also be used to ensure that the definition of ready is fulfilled and that new stories can get estimated.


All Projects



Implementation effort

The general effort of writing good stories depend heavily on the experience of the product owner and the complexity of the project. The product owner should plan to invest at least 10-20 hours a week into the stories.


All Projects.


In suboptimal situations it happens that the product owner can not fully decide upon the projects features and has to consult and wait for customer feedback. In such situations you usually see that it is very complicated to fullfil a definition of ready and stories become more vague and meta. This is why it is so important that a product owner can decide upon the product features.

See also

About the Toolbox

The basysKom Toolbox is a state-of-the-art collection of best practices in agile management and software development and a valuable tool for every kickoff meeting.

These cards can be used during a project kickoff in order to select best fitting good practices from the very start of your project, but also as a reminder during the course of a project implementation. Every card holds a QR code with additional information related to the specific tool, the tools’ applicability, known constraints and additional tips on how to implement it in a project setup.

You can provide us feedback on GitHub.


basysKom Newsletter

We collect only the data you enter in this form (no IP address or information that can be derived from it). The collected data is only used in order to send you our regular newsletters, from which you can unsubscribe at any point using the link at the bottom of each newsletter. We will retain this information until you ask us to delete it permanently. For more information about our privacy policy, read Privacy Policy