Skip to content

Details

! This is an Online event !

The link to this online event will be added later.

There are two reasons for all bugs, delays and frustrations - missing requirements and poor communication.

The user story is a conversation starter. It's not a requirement.

The problem is that this conversation never happens for many software development teams. We don't know the "language", and we often treat user stories like requirements.

User Story Analysis is a neat, structured, quality-driven, human-driven, engaging, collaborative approach to analysing user stories and building team routines to turn the user story into well-thought-out requirements.

It's a way to bring everything that is known for the story to the table and save actual calendar days wasted in clarifications scattered across multiple channels.

The practice is supported by a Miro board that will help teams quickly get a hold of it and make the best out of their refinement meetings.

We can now get ready for development by deeply empathising with our users, uncovering the actual context, goals, needs and intentions behind the user story, brainstorming on what could go wrong and how to test for all known risks, and revealing dependencies early in the process.

Our speaker of this night is Hristina Koleva, process geek, tester, product owner and mentor.

For 17+ years in the industry, she has learnt that software quality needs a full-picture approach with efficient practices.

Her mission is to help teams start on the right foot with quality through early risk management and collaboration and guide them not to get lost in translation about quality and processes.

Related topics

Agile Coaching
Agile Leadership
Agile Project Management
Scrum
Women in Technology

You may also like