Agile Business Analysis: From Story to Code

How to ensure that business and IT truly understand each other and deliver what makes sense in an agile world? The training focuses on the practical side of business analysis, applied primarily during the agile (generally iterative) way of delivering changes. First, it will introduce you to what is today considered basic knowledge of the agile approach, and then show techniques that are successfully used for the effective work of a business analyst.

During the course, participants will become familiar with the following techniques:

• Domain storytelling, which serves to understand the context, find concepts and their relationships. It will help them analyze the current state and needs, as well as start initial discussions about the desired solution.
• User Story Mapping, which will subsequently determine the main axis of the solution and allow them to effectively prioritize delivery (so that features that no one needs are not developed).
• Use Cases and User Stories, which will then allow you to develop the requirements in detail suitable for their inclusion in one of the subsequent iterations (sprints).

Participants will practically try out all the techniques and, above all, will recognize the power in their mutual connection.

The training places great emphasis on practical understanding between business and IT. For this reason, the training is suitable for both business analysts and IT analysts and developers. Analysts will learn what information they should find out and why, and developers will then understand why analysts want it in the way they ultimately convey it to them.

The training is built on practical experience, not on dogmas or an idealized image of agility. It does not follow the path of strict dogmatic definitions and theorizing agile authorities. The goal of the training is to show participants that with a relatively simple approach they can be significantly useful members of an agile team.

The vast majority of techniques presented during the training can also be successfully used in the traditional (waterfall) development method. So you don't necessarily have to be 100% agile to be able to come to the training and take the maximum out of it into your daily practice.