How to User Story

User stories have become indispensable in agile practice. But why? While previously stacks of specifications were created before implementation, today a short sentence with "As..., I want..., so that..." is supposed to make everything better? The answer lies in the understanding of what a user story is and what it should enable us to do.

When used correctly, user stories help us focus on the users of the system. Adopting this perspective allows us to develop software that delivers value to those users. A shared understanding – from stakeholders to the product owner to the entire team – is incredibly important in this process. A user story helps us create this shared understanding.

What sounds very simple in theory often presents us with many challenges and questions in practice:

• Why does it have to be user stories specifically?
• Who actually writes the user stories?
• Who is my user?
• Why does it take so long for my user stories to be finished?
• How can I create user stories that are suitable for iteration?
• Why do they actually have to fit into one iteration?
• What details should be included, and how many?
• How should I handle purely technical tasks?
• When will the story be fully implemented? I can always improve something (90% syndrome).

Requirements

Basic knowledge of agile methods

‍

Program & Content

In this training, we will search for answers to these questions. At the end of the course, participants will leave brimming with new techniques, inspiration, ideas, "aha!" moments, and experiences, and will be eager to try them out and put them into practice.

What topics will we cover:

• Understanding (Agile Manifesto, CCC, delivering value)
• Discover (Story Mapping, Use Case+)
• Writing (template, user roles, adding details, acceptance criteria, functional manifesto, INVEST)
• Cutting (Epics, Story Writing Workshop, Discovery Team, SPIDR, Unsplittable User Stories)
• Estimation (Relative Estimation, T-Shirt Sizes, Velocity)
• Prioritize (MVP, Potentially Shippable Product Increment)
• Implementation & Acceptance (Open or Done, Value on Credit, Documentation)
• Questions that are important to you

In addition to theoretical input, participants can directly benefit from practical exercises. Furthermore, the exchange within the group allows for different perspectives to be adopted and experiences to be shared.

After this course, participants will understand the principle of user stories and be able to use them in such a way that added value can be created regularly.

Learning objectives

• Understanding the importance and benefits of user stories
• Create and use user stories clearly and effectively
• Define and apply roles and collaboration
• Overcoming typical challenges

Target audience

• Everyone involved in agile projects

Included services

• Course materials
• Certificate of participation