According to Jeff Sutherland, one of the co-founders of SCRUM, backlog refinement forms the backbone of a functioning Scrum Team. However, the Scrum Guide is largely silent on how this important event can be successfully established in the development process. The document only devotes a short and concise paragraph to the event.

 Sutherland's statements on backlog refinement were confirmed during the development of automated scheduling software for ground handling services at a large airport in northern Germany. The event became one of the key success factors in realizing the agile project. And that despite or precisely because the prerequisites for the project were very challenging:
- a brief vision and no formulated requirements for the product
- a large number of the software critical stakeholders
- No possibility to involve business analysts
- a managing director as product owner who was only available to the team part-time
- Expert knowledge that was only available in the respective silos
- a complex product portfolio with many dependencies between the different solutions
- the risk of chain reactions at the airport in the event of delays, endangering the transport of passengers on the same day or losing important slot times for the airspace

In his lecture, Nils Hyoma shows how his team successfully solved complex challenges with good backlog refinement. The team was gradually able to integrate critical stakeholders in a targeted manner. The software developers have taken on the responsibility for determining the requirements, resolved dependencies through collaboration with other teams and coordinated the releases.

 In addition to the actual task of developing software, the planned and structured backlog refinement event gradually became the engine of change management and the agile and digital transformation of the airport.

The practical talk takes up real project situations and problems. Nils Hyoma summarizes the experience gained in the agile project in a highly complex environment. He explains how and why a well-carried out backlog refinement can become a key success factor in agile projects.

According to Jeff Sutherland, one of the co-founders of SCRUM, backlog refinement forms the backbone of a functioning Scrum Team. However, the Scrum Guide is largely silent on how this important event can be successfully established in the development process. The document only devotes a short and concise paragraph to the event.

 Sutherland's statements on backlog refinement were confirmed during the development of automated scheduling software for ground handling services at a large airport in northern Germany. The event became one of the key success factors in realizing the agile project. And that despite or precisely because the prerequisites for the project were very challenging:
- a brief vision and no formulated requirements for the product
- a large number of the software critical stakeholders
- No possibility to involve business analysts
- a managing director as product owner who was only available to the team part-time
- Expert knowledge that was only available in the respective silos
- a complex product portfolio with many dependencies between the different solutions
- the risk of chain reactions at the airport in the event of delays, endangering the transport of passengers on the same day or losing important slot times for the airspace

In his lecture, Nils Hyoma shows how his team successfully solved complex challenges with good backlog refinement. The team was gradually able to integrate critical stakeholders in a targeted manner. The software developers have taken on the responsibility for determining the requirements, resolved dependencies through collaboration with other teams and coordinated the releases.

 In addition to the actual task of developing software, the planned and structured backlog refinement event gradually became the engine of change management and the agile and digital transformation of the airport.

 The practical talk takes up real project situations and problems. Nils Hyoma summarizes the experience gained in the agile project in a highly complex environment. He explains how and why a well-carried out backlog refinement can become a key success factor in agile projects.

According to Jeff Sutherland, one of the co-founders of SCRUM, backlog refinement forms the backbone of a functioning Scrum Team. However, the Scrum Guide is largely silent on how this important event can be successfully established in the development process. The document only devotes a short and concise paragraph to the event.

 Sutherland's statements on backlog refinement were confirmed during the development of automated scheduling software for ground handling services at a large airport in northern Germany. The event became one of the key success factors in realizing the agile project. And that despite or precisely because the prerequisites for the project were very challenging:
- a brief vision and no formulated requirements for the product
- a large number of the software critical stakeholders
- No possibility to involve business analysts
- a managing director as product owner who was only available to the team part-time
- Expert knowledge that was only available in the respective silos
- a complex product portfolio with many dependencies between the different solutions
- the risk of chain reactions at the airport in the event of delays, endangering the transport of passengers on the same day or losing important slot times for the airspace

In his lecture, Nils Hyoma shows how his team successfully solved complex challenges with good backlog refinement. The team was gradually able to integrate critical stakeholders in a targeted manner. The software developers have taken on the responsibility for determining the requirements, resolved dependencies through collaboration with other teams and coordinated the releases.

 In addition to the actual task of developing software, the planned and structured backlog refinement event gradually became the engine of change management and the agile and digital transformation of the airport.

 The practical talk takes up real project situations and problems. Nils Hyoma summarizes the experience gained in the agile project in a highly complex environment. He explains how and why a well-carried out backlog refinement can become a key success factor in agile projects.

Nils Hyoma and Shobhit Pradhan facilitate this hands-on workshop!

If you are an agile coach or a Product Owner then collaboration is one of many key factors when looking for solutions to complex problems! You want to foster direct communication between developers, experts and users, and establish a common understanding of the product and its vision? Then a Design Studio workshop is one method that can meet your expectations in a short time-frame. You will find common solutions with your team in less than 60 min.

Ever heard about it before? No problem! Shobhit Pradhan and Nils Hyoma will perform interactive Design Studio Sessions with you! All you will need is a few sheets of paper and assorted color pens. Together, we will create iterative and collaborative outstanding mockups for challenging problems with you and you will instantly learn a new method.

After the workshop, you’ll know how to facilitate a workshop for people with various backgrounds. The participants will share their work experiences and you’ll be able to solve problems that could not be solved alone. The methods fit perfectly into agile environments or lean workflows. You’ll have an increase in the buy-in of your project.

We will use miro.com as a whiteboard and Zoom breakout rooms. Please bring color pens and white paper and a way to upload your offline drafts through the camera.

Nils Hyoma and Shobhit Pradhan facilitate this hands-on workshop!

If you are an agile coach or a Product Owner then collaboration is one of many key factors when looking for solutions to complex problems! You want to foster direct communication between developers, experts and users, and establish a common understanding of the product and its vision? Then a Design Studio workshop is one method that can meet your expectations in a short time-frame. You will find common solutions with your team in less than 60 min.

Ever heard about it before? No problem! Shobhit Pradhan and Nils Hyoma will perform interactive Design Studio Sessions with you! All you will need is a few sheets of paper and assorted color pens. Together, we will create iterative and collaborative outstanding mockups for challenging problems with you and you will instantly learn a new method.

After the workshop, you’ll know how to facilitate a workshop for people with various backgrounds. The participants will share their work experiences and you’ll be able to solve problems that could not be solved alone. The methods fit perfectly into agile environments or lean workflows. You’ll have an increase in the buy-in of your project.

We will use miro.com as a whiteboard and Zoom breakout rooms. Please bring color pens and white paper and a way to upload your offline drafts through the camera.

Nils Hyoma and Shobhit Pradhan facilitate this hands-on workshop!

If you are an agile coach or a Product Owner then collaboration is one of many key factors when looking for solutions to complex problems! You want to foster direct communication between developers, experts and users, and establish a common understanding of the product and its vision? Then a Design Studio workshop is one method that can meet your expectations in a short time-frame. You will find common solutions with your team in less than 60 min.

Ever heard about it before? No problem! Shobhit Pradhan and Nils Hyoma will perform interactive Design Studio Sessions with you! All you will need is a few sheets of paper and assorted color pens. Together, we will create iterative and collaborative outstanding mockups for challenging problems with you and you will instantly learn a new method.

After the workshop, you’ll know how to facilitate a workshop for people with various backgrounds. The participants will share their work experiences and you’ll be able to solve problems that could not be solved alone. The methods fit perfectly into agile environments or lean workflows. You’ll have an increase in the buy-in of your project.

We will use miro.com as a whiteboard and Zoom breakout rooms. Please bring color pens and white paper and a way to upload your offline drafts through the camera.