InfoQ has an outstanding interview with Mary and Tom Poppendieck about Lean Software Development. One of the longer interviews on the topic, and full of great content. You can watch streaming video of the interview, jump around to the answers of specific questions, or read the full transcript – great format for presenting a long form interview like this.
Explaining Agile Development…
…to your Brother-in-Law. A great article by Joe Little, on his new blog. Thanks Mishkin for telling us about it. Joe’s article serves as an excellent precursor to our comparison of agile software development methodologies. It would also be extremely effective advice for getting mindshare prior to rolling out agile […]
Agile Development Methodology Comparison
Agile project management has entered the mainstream – incremental delivery is now common and (should be) expected for any new software development project. Which agile development methodology should you use on your project? There are at more than ten to choose from. What makes them different? The risks that they try to address.
Agile Development and Software Maintenance Costs
Over 90% of the cost of software development is software maintenance (cite). This alarming trend was predicted as early as 1972. McKinsey suggests that CIOs should spend no more than 40-60% on maintenance. Gartner’s IT Spending and Demand Survey (2002) reports that CIOs are spending 80% of their budgets on maintenance (p12 of presentation). Agile development can help reverse this trend.
Product Life Cycle and the ROI of Agile Development
The product life cycle is a description of the presence or behavior of a product in the marketplace over time. The framework for description is a function of the sales volume of the product versus time. Over time, products are created and introduced, and sales grow, peak and decline. The product life cycle uses phases to describe these different periods in the life of a product. Understanding the product life cycle is also key to calculating the ROI of agile development.
Code Debt: Neither A Borrower…
Code Debt is the debt we incur when we write sloppy code. We might do this to rush something out the door, with the plan to refactor later. Agile methodologies focus on delivering functionality quickly. They also invoke a mantra of refactoring – “make it better next release.” This can create pressure to “get it done” that overwhelms the objective of “get it done right.” Taking on code debt like this is about as smart as using one credit card to pay off another one.
Crossing The Desert With Bad Project Planning
Johanna Rothman recently wrote an article with a poignant introduction: “A project team focuses on an interim milestone, works like the devil to meet that milestone. They meet the milestone, look up, and realize they’re not at the end of the project–they still have to finish the darn thing. They’re living the Crossing the Desert syndrome.” Fixing it isn’t enough – how do we prevent it from happening?
Ten Common Mistakes of Going Agile
This concludes and summarizes our winter-holiday series on the 10 common mistakes of going agile. The ten mistakes that Levent Gurses identified in the Dec 2006 edition of Dr. Dobb’s journal. Here are links to the ten previous articles, and a summary of the mistakes.
Going Agile, 10 Mistakes: Make Agile the New Religion
Don’t over-hype the approach. Don’t be one-dimensional in your message. You will lose credibility. And if you over-promise, you risk making agile the scapegoat.