Quality versus Agility: a conflict of interest?

An agile way-of-working is often marketed as a way to achieve shorter cycle times or lower time-to-market, in short, it sounds like “more speed”.

A general complaint heard from software teams is “we don’t have time for quality”. In so doing 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 actually leads to a longer time before a product is viable for large business volumes!

This talk will discuss subjects like:
- What is quality, how to make it explicit?
- Agility is not the same as speed, and agility is a quality in itself.
- 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.