Time to Breathe
In software development there is a tendency to add, add, add, change, change, change—even when the additions or changes are not of any value.
Inspired by the ideas of Minimal Viable Products and iterative software development, but forgetting the most important parts of those, we end up rapidly iterating but not really waiting or accounting for feedback.
A team usually works on a single project, pushing the development with all the velocity they can muster—and when they realize they have been pushing in the wrong direction they turn around and push in the opposite direction, once again with full force.[anecdotal]
This is wasteful. But it is also endemic of a larger problem.
Anders Enghøj and I recently launched Mærkelex, an encyclopaedia for scout badges in Denmark.
We spent a total of 5-6 man days developing before launch, including the time we spent inputting the data on badges
Continue reading →