Zurück

The Case for Technical Excellence

One of the (most overlooked) principles of the Manifesto for Agile Software Development is that “Continuous attention to technical excellence and good design enhances agility”.

All too often, work that focuses on addressing technical issues is deprioritised in the name of focusing on business value. Is there a case for technical excellence – in code, in architecture, in people – beyond its appearance on a might-as-well-be-hidden page on a manifesto that's over two decades old? Is technical excellence only the concern of technical roles? Is a good architecture in conflict with business value or a vehicle for it?

This session looks to go beyond buzzwords to build a case for technical excellence that appeals to all roles in a development organisation, noting that “The best architectures, requirements, and designs emerge from self-organizing teams”.

Speaker

 

Kevlin Henney
Kevlin Henney is an independent consultant, trainer, speaker and writer. His development interests and work with companies covers programming, practice and people. He has contributed to open- and closed-source codebases, been a columnist for a number of magazines and sites and has been on far too many committees (it has been said that "a committee is a cul-de-sac down which ideas are lured and then quietly strangled”). He is co-author of two volumes in the Pattern-Oriented Software Architecture series, editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.

 

Jetzt Tickets sichern

inside-agile-Newsletter

Du möchtest über die Agile Softwareentwicklung im Unternehmen
und weitere Angebote von inside agile auf dem Laufenden gehalten werden?

 

Anmelden