Join the Technical Debt bloggers in discussions about their personal experiences in agile development best practices and adopting agile ideas in complex business systems. If you are interested in blogging for us, let us know!
By Frances Lash | March 25, 2015
This post beings with an interesting statement: that in a start up environment technical debt often feels inevitable. Technical debt can be seen as a function of moving fast, minimum variable products (MVP), prototypes, agile practices, and of releasing the product to market as soon as possible.
The idea of using a minimum variable product to ... read more
By Frances Lash | February 23, 2015
In this post, technical debt management is looked at from a DevOps approach. Technical debt is defined here, as the price organizations pay when releasing poorly designed code. Companies that collect a large amount of technical debt are in risk of running into a situation where any innovation takes a backseat to putting out fires. ... read more
By Frances Lash | February 2, 2015
Is technical debt still a valid metaphor in the present global software development world? The answer is yes, and this post goes on to present the benefits of such a metaphor while explaining just what technical debt is exactly. There is a growing concern on tech debt not simply because of the costs associated with ... read more
By Frances Lash | January 5, 2015
This post discusses the three categories of code that can be found within a certain project and that confusion about them plus a misunderstanding about their actual cost can lead to trouble. The three categories of code follow:
Temporary Code: or code written to throw away within a day or week – if it breaks it’s ... read more
By Frances Lash | December 30, 2014
The on going management of technical debt has become viewed as critical for the development of high quality and maintainable software, even by those who promote agile development processes. This consideration for tech debt management has contradicted the notion that development decisions should almost exclusively be driven by business value because of the difficulty of ... read more
By Frances Lash | November 12, 2014
Technical debt, as a term, serves to incentivize change within app and portfolio management. However, it fails to translate with business leaders, therefore failing to push through with the change it seeks to promote. In this post, Phil Murphy expands on his love/hate relationship with the term; lauding the “sentiment for change” it inspires, but ... read more
By Frances Lash | October 14, 2014
Managing technical debt is easiest when there is an outline to help your development team discuss how classify and prevent technical debt. This post does just that. Technical debt is classified in several ways according to Martin Fowler’s tech debt quadrant (prudent and deliberate debt; reckless and deliberate debt; reckless and inadvertent debt; prudent and ... read more
By Frances Lash | September 19, 2014
Acknowledging that some form of technical debt exists in every codebase is paramount to managing debt and staying in “the black”. Asides from the fact that technical debt kills productivity thus leading to economic downsides, there exists a psychological downside to technical debt. If a developer dreads dealing with code that is brittle and filled ... read more
By Frances Lash | September 2, 2014
This is a kind of ‘wiki-how’ on how to manage technical debt in an agile environment – the right way. Not that there is one right way, but there are a few basics that this article points out. Technical debt, like any other debt should be budgeted in the release and iteration planning. Ultimately, the ... read more
By Frances Lash | July 11, 2014
One of the mantras of Agile development teams is to do “just good enough” to get the job done. This is what drives the creation of architecture that meets the bare minimum requirements to function. But the “just good enough” mindset is an easy way to incur technical debt.
This is what the post, Architecture Technical ... read more