New book: Being the project manager

This week Sju G. Thorup‘s book “Being the project manager” was published. ZeaLake supported Sju’s work, and I am very happy with the result.

“Being the project manager” is written for new project managers and people who aspire to lead a project. It is not a traditional textbook, and it is suited for Agile and . . . → Read More: New book: Being the project manager

Why verify features before marking them “Done”?

On our backlog, we have the usual columns: Planned, In Progress and Done. But before the Done column we have an extra column called Verify. Our backlog looks like this:

When a feature has been fully developed and tested, we move it to Verify where the owner of that feature . . . → Read More: Why verify features before marking them “Done”?

It’s not a bug, it’s a feature request

I previously advised that you shouldn’t track bugs but rather fix them immediately. But not every issue reported as a bug should be treated as a bug in this sense. So how do we distinguish between a bug and a feature request?

Issues are reported when the software is not behaving as expected. That expectation . . . → Read More: It’s not a bug, it’s a feature request

Lightweight code reviews using TortoiseSVN

I believe that it is often a good idea to have another set of eyes looking at the code I write. The questions and comments resulting from such a code review indicate its value:

“It seems like you are missing a test case for this scenario, and I think the code will break on it” . . . → Read More: Lightweight code reviews using TortoiseSVN

High Performance Engineering Teams

You want to shorten the time from idea to live. You want your team to develop faster. You want higher quality. In short: you want a high performance engineering team.

This presentation is based on my experiences building high performance engineering teams, and focuses on the technical practices required. These practices centers around automation (build, . . . → Read More: High Performance Engineering Teams

Should technical debt be avoided?

We often use the term technical debt when referring to code that development have currently postponed but will eventually have to complete at some point in the future. Examples can be a polished installer, a refactoring of the data access layer, an optimization of important queries, improved modularization, and known bugs.

When doing agile development . . . → Read More: Should technical debt be avoided?


As a human being you get value out of every heartbeat. Nutrients are transported out to every hungry cell in your body and at the same time waste products are returned providing feedback to regulation mechanisms. To increase the value provided by the heartbeat, the body can increase the frequency: with a more rapid pulse, . . . → Read More: Decompose!

Don’t track bugs; fix them!

We got a question the other day about which bug tracking system we would recommend? After some discussion, I concluded that I wouldn’t recommend any at all. Because I believe bugs shouldn’t be tracked.

Track systems are seductive A bug tracking system feels so nice. When you discover an error or get a new idea, . . . → Read More: Don’t track bugs; fix them!