Why should you read this case study?
For the past 28 months, we were able to push out 26 new releases, with just two gaps in December, when we celebrate Christmas. As a matter of fact, the versions were there, however, we decided against releasing them because it might have meant very few people would make use of the changes during the holidays.
With an average of six new features per month, we have released 150+ new features to production. The living proof appears in our Kanbanize Blog (make sure to subscribe for updates).
As of this moment, at Kanbanize we have a total of one (1) open customer issues. Yes, this is not a joke, we have almost no open customer issues for a code base exceeding a million lines. Of course, there are issues that we are just not aware of, but out of the reported ones, we’ve fixed them all.
We have around sixty open internal issues, most of which are low priority. We are depleting these quite quickly, so in around four months we expect to have zero open internal issues as well.
We managed to create an eight-digit company in three years and effectively multiply the initial funding by more than 30 times.
The numbers show that we must be doing something right and this book talks about the engineering part of this modest success.
Okay, let’s do this!