Best practices in software development - quality vs velocity

Poor quality of a software solution is a common reason why development velocity drops. That translates into less features delivered on time and increased necessity to scale up the team to keep up the pace.

In a worst case scenario, this leads to serious investments, major redesign or even complete rewrite.

On the other hand, maximizing quality comes with immediate costs, that are not always acceptable.

As a Solutions Architect and Head of Technology of a software house – virtual roundtable speaker – Krzysztof’s observed hundreds of projects and seen how specific practices and business models influence solution quality and development velocity.

What’s proved and brings the real value?

What’s generally overhyped?

Where’s the sweet spot between quality and velocity?