Download as PDF, PPTX
Uploaded byKevlin Henney
The Case for Technical Excellence
The document discusses the importance of technical excellence within agile practices, highlighting how neglecting quality can incur technical debt, which parallels financial debt. It emphasizes that while prioritizing business value is essential, continuous attention to technical quality and design enhances agility and prevents complications from accumulating technical debt. Additionally, it explores the implications of metaphors in understanding software development and the dangers of misapplying the concept of technical debt.
More Related Content
Similar to The Case for Technical Excellence
![Technical debt in cyber ark [agile practitioners-2015]](https://cdn.slidesharecdn.com/ss_thumbnails/technicaldebtincyberarkagile-practitioners-2015-150201082255-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
The Case for Technical Excellence
- 1.
- 2.
- 4. agile, adjective ▪ ableto move quickly and easily Concise Oxford English Dictionary
- 5. agile, noun ▪ quickmovement The goal pursued by many organisations ‘doing’ agile
- 6. agile, noun ▪ busyness Theresult of many organisations ‘doing’ agile
- 7. agile, noun ▪ prioritisingbusiness goals over technical excellence The practice of many organisations ‘doing’ agile
- 8. agile, noun ▪ underminingbusiness goals by ignoring technical excellence The result of many organisations ‘doing’ agile
- 10. Continuous attention to technicalexcellence and good design enhances agility.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 20. Architecture represents the significantdesign decisions that shape a system, where significant is measured by cost of change. Grady Booch
- 21. What effect doesignoring quality have on feature development? a. It has no effect b. It reduces the cost c. It increases the cost
- 22. What effect doesignoring quality have in the short-term? a. It has no effect b. It reduces the cost c. It increases the cost
- 23. What effect doesignoring quality have in the long-term? a. It has no effect b. It reduces the cost c. It increases the cost
- 24.
- 25.
- 27. As an evolvingprogram is continually changed, its complexity, reflecting deteriorating structure, increases unless work is done to maintain or reduce it. Meir M Lehman “Programs, Life Cycles, and Laws of Software Evolution”
- 28.
- 30. metaphor The figure ofspeech in which a name or descriptive term is transferred to some object different from, but analogous to, that to which it is properly applicable.
- 31. µεταϕορα The figure ofspeech in which a name or descriptive term is transfer
- 33. Metaphor is pervasivein everyday life, not just in language but in thought and action.
- 34. The essence ofmetaphor is understanding and experiencing one kind of thing in terms of another.
- 35. TIME IS MONEY ARGUMENTIS WAR ARGUMENTS ARE BUILDINGS HAPPY IS UP; SAD IS DOWN LOVE IS A JOURNEY
- 37. The aphysical and invisibledomain of software is more about metaphor than matter.
- 38. To be consideredgood, a metaphor has to offer a number of points of useful correspondence with what is being described. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 39. Another quality ofa good metaphor is that it should not have too many obvious points of conflict. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 40. The third qualityof a metaphor that makes it effective is familiarity to its audience. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 41. Technical Debt isa wonderful metaphor developed by Ward Cunningham. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt. Martin Fowler martinfowler.com/bliki/TechnicalDebt.html (2003)
- 42. Martin Fowler martinfowler.com/bliki/TechnicalDebt.html (2003) TechnicalDebt is a wonderful metaphor developed by Ward Cunningham. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt.
- 43. Shipping first timecode is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite. Ward Cunningham c2.com/doc/oopsla92.html
- 44. Ward Cunningham c2.com/doc/oopsla92.html The dangeroccurs when the debt is not repaid. Every minute spent on not-quite- right code counts as interest on that debt.
- 45. Although we knowthat by definition no metaphor is perfect, there are two common ways in which the metaphor is misapplied: assuming technical debt is necessarily something bad; equating technical debt with a financial debt value. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 46.
- 47.
- 48. Technical debt isnot the cost of repaying the debt: it is the cost of owning the debt. These are not the same. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 49. That is themessage of the technical debt metaphor: it is not simply a measure of the specific work needed to repay the debt; it is the additional time and effort added to all past, present, and future work that comes from having the debt in the first place. Kevlin Henney “On Exactitude in Technical Debt” oreilly.com/radar/on-exactitude-in-technical-debt
- 50.
- 51.
- 52.
- 53.
- 54. neglect Want of attentionto what ought to be done; the fact of leaving something undone or unattended to; negligence.
- 55. John Seddon Freedom fromCommand & Control — A better way to make work work Value demand represents the demands customers make for the things they want, things that are of value to them. Failure demand is created by the organisation not working properly. Failure demand is demand caused by a failure to do something or do something right.
- 56. The best architectures, requirements,and designs emerge from self-organizing teams.