Building up technical debt?

Retrospectives are the ideal time to remind the team about specific practices.

In our last retrospective, I tried to find out if we were building up technical debt.

By holding a poll, the results would show us if we took enough time to refactor.

Every team member graded the code health on a scale from 0 to 5. Zero being dramatic, five being perfect code.

This was the result:


The team responded that five is impossible to achieve, but we that it should always be our ambition.

We concluded that 4 was a great score and that we took enough time to refactor.

Keep up the good work, guys! We’ll do the poll again in a couple of weeks.

About Nick Oostvogels

Hi, I'm an independent management consultant. My biggest strengths are located in the fields of teamwork, motivation, leadership and continuous improvement. In the IT industry you find a lot of these values in the agile movement, in which I often act as a project leader, product owner or coach. My interests go a lot further, into other industries where we find these values in lean production. Besides that, I try to broaden my horizon as much as possible, always looking for better ways of doing business.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: