Quality versus Agility: a conflict of interest?

Quality versus Agility: a conflict of interest?
An agile way of working is often marketed to achieve shorter cycle times or lower time-to-market. In short: “more speed”. In contrast, a general complaint from software teams is that “we don’t have time for quality”. Doing so, they express their feeling that there is always a trade-off between quality and speed. There is never time to do it right, but there is always time to do it over... This can lead to a long time before a product is viable for large business volumes!

This meetup consists of a talk, writing quality stories hands-on, and a Q&A
We’ll start with a talk and discuss subjects like:

• What is quality, and how to make it explicit?
• Agility is not the same as speed, and agility is a quality on its own.
• How to make your stakeholders perceive qualities as value.
• How quality is achieved by architectural tactical measures.
• How some architectural tactical measures help speed and agility.
• How to apply just-in-time architecture methodology to ensure quality.
• Why architecture skills are more important than the architecture role.

After this, it’s time to do hands-on work in groups! We’ll instruct you how you can write quality stories and then it’s your turn to gain some experience writing them. We’ll conclude the evening with discussing the results and a Q&A.

What you will take home
It’s our goal to show you that quality and agility are not mutually exclusive and to showcase how quality stories help you to achieve quality in an agile environment.

Agenda
17:30 Dinner
18:30 Talk starts
20:30 End of meetup