When migrating a product from a traditional approach to an agile one,
teams commonly bring along a large database of bugs. These are the
result of an inadequate focus on continuously high quality. Shortly into
their agile initiative, many teams (and their...
Jim Highsmith on Technical DebtA former coworker of mine, Jim Highsmith, has recently written an article on The Financial Implications of Technical Debt.
Jim states that recent studies indicate the cost of technical debt is
near $1 trillion in the U.S. I...
In a test implementing Back Door Manipulation, you bypass the System Under Test to reach the resource it manipulates directly, with the goal of veryfing its behavior or to perform some other handy operations. In fact, there's more than one reasons why you may...
Despite being part of numerous retrospectives over the past few years
I don't remember actually facilitating one until my current team's last
I've gradually come to appreciate the skill involved in facilitating
this type of meeting having originally...
I've been pondering the problem of how does an organization achieve
innovation and at the same time have some level of consistency in the
patterns and components that are in use across teams. Considering the
very nature of innovation is to solve existing...
A fairly common trend on nearly every project I've worked on is that
at some stage the client will ask for more people to be added to the
team in order to 'improve' the velocity.
Some of the most common arguments against doing so are that it will
The Shared Fixture pattern is the last of the Fixture organization patterns treated in this series. A Shared Fixture is the opposite and specular case of a Fresh Fixture: it is not recreated for each test, but all the test methods reuse the same object graph...
Based on feedback from participants in my Agile 2010 workshop “How We Do Things Around Here In Order To Succeed,” I am planning to offer the workshop as a one-day seminar. A tentative agenda for the seminar is as follows:
How do you welcome new employees? Normally,
it is a rite of passage that all new developers must search some
documentation and struggle with setting up their development
environment. Let me state for the record that I absolutely hate this
The Agile Triangles was introduced by Jim Highsmith
as an antidote to the Iron Triangle. Instead of balancing development
between cost, schedule and scope, the Agile Triangle strives to strike a
balance between value, quality and constraints:
Although we mostly split the work on my project so that there aren't
too many dependencies between the teams in Chicago and Pune, there have
still been some times when we've designed major parts of the code base
in Pune and have needed to communicate that...
I once heard a speaker saying that Lego bricks are one of the most abused metaphor in computer science. I like this quote very much, but I also like the Lego metaphor as it is very effective in explaining patterns like Dependency Injection even to higher...