Software debt exists in different ways. Technical debt is widely known, some other forms are competence debt and quality debt. Software debt can cause product maintenance costs to increase and can depress developers. Several solutions exist to manage software debt.
An exploration of recent advice from Henrik Knibert, Ward Cunningham and Hayim Makabee on technical debt, how to make the most of it and when to pay it off.
Simplicity, feedback, communication, respect and courage, these eXtreme Programming (XP) values still inspire the team of the XP Days Benelux 2013 conference. InfoQ did an interview with two of the conference hosts, Merlijn van Minderhout and Pascal Van Cauwenberghe, about new developments in agile, successful agile transformations and the needs of European organizations in agile adoption.
Swarming is a technique that helps agile teams to deliver working software fast and frequently. What is swarming, what are the benefits of swarming, and when and how to apply it?
The Wall Street Journal has begun to take notice of the growing number of technology companies that have been practicing Pair Programming and has published their take on the practice in an article titled Computer Programmers Learn Tough Lesson in Sharing.
Wikispeed founder Joe Justice gave a talk in Wellington, New Zealand, this week in which he spoke about the Wikispeed mission of "Rapidly Solving Problems for Social Good", starting by using agile techniques to build a 100MPG vehicle with the intent of creating a new approach to motor-vehicle manufacturing, using open-source and crowd-source approaches building on agile values and principles.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
A recent post by Paul Dolman-Darrall on the Value, Flow, Quality blog proposed a list of the 20 most influential people in the Agile community.
The Agile community has a great tradition of making fun of itself and April Fools Day 2012 was no exception. Here is a wrap up of some of the best gags from this year that you may have missed.
Pair programming is an agile software development technique in which two programmers work together at one workstation. The benefits of pair programming are well known and the technique is widely practiced. However, what is the best way to sit while pairing?
Agile coach Morgan Ahlström recently turned to the Agile Coach Support mailing list to ask how to deal with an organization that said they wanted the benefits of becoming more agile, but was behaving in ways contrary to that goal.
Several members of the Agile community emphasize the importance of feedback loops in the effectiveness of Agile development processes.
Building software is closely associated with managing a lot of constraints. These constraints might be in terms of time, money, technology, decisions, compatibility, regulatory, people, process or all of the above. Jim Bird discussed the constraints imposed by Scrum, XP and how they help in fostering creativity and building the right software.
The Agile 2010 conference was held in Orlando from 9-14 August. A number of commentators felt there were not enough sessions focused on the technical practices and programming techniques, including Bob Martin who twittered about the lack of technical sessions. This resulted in a number of responses and the announcement of plans to launch an XP Universe conference in 2011 targeting programmers.
Stuart Wray wrote a paper analysing how pair programming actually works in team environments and identifies four mechanisms that can be applied to improve the effectiveness of pair programming, and why it results in better quality products.