A couple days ago I spoke at the Beyond Agile group meeting on the topic of “Recognizing Software Debt”. Early in the presentation we ran an exercise to get a feel for the effects of software debt that was original created by my friend, Masa Maeda. Here is a link to the exercise: http://www.agilistapm.com/understand-technical-debt-by-playing-a-game/ The [...]
Archives for TDD
Delving into Technical Debt – Cutter Article
The following is an except from the article authored by Israel Gat and myself named “Delving into Technical Debt”: Many of the findings and the recommendations we make in Cutter technical debt engagements are broadly applicable in concept, if not in detail. There is commonality in the nature of the hot spots we typically find, [...]
Treating Software as an Asset
William Caputo wrote a passionate blog entry on why “Software is not an asset” here: http://www.williamcaputo.com/archives/000310.html Although I entirely agree with ideas discussed about refactoring and removal of code, I do not think that the blog entry substantiates his claim that software is not an asset. An asset is: Anything tangible or intangible that is [...]
Towards a Push-Button Release
This presentation is being delivered as a 45-minute lecture and discussion for a company-wide tech talk today. It contains 2 case studies that revolve around moving to a push-button release that reduced the whole product company’s release cycles from 6 months to every week and the effects of a “No Defect” policy on a team’s [...]
Testing in an Agile Context
I presented the following in a webinar for Boeing this week on “Testing in an Agile Context”. The focus of the webinar was to discuss differences in approach for testing when moving to an Agile method. Hope that you enjoy. Please leave feedback in the comments section. Testing in an Agile Context 2011 View more [...]
Impediment Management and the Agile Triangle
The Agile Triangle, a concept that was discussed by Jim Highsmith in his book Agile Project Management: Creating Innovative Products, describes how teams and organizations can go beyond the traditional Iron Triangle in defining project success criteria. In the Agile Triangle, the traditional project constraints of schedule, cost, and scope are confined to one point [...]
