Month: February 2016

Establishing a Zero Defect Culture

Zero Defect Culture is a term I came up with just over a year ago to describe an approach that focuses on keeping your in-development defects at or around zero.

It can be applied to any team developing a software application in phased iterations to help minimise disruption created during feedback cycles between releases.

Continue reading “Establishing a Zero Defect Culture”


Process By Default

Have you given your development processes the thought they deserve? Do you consider the benefits of different approaches in different contexts? Do you question whether established practices are right for you and your team?

It seems obvious to say that we need to separate our tools from how we choose to use them. Or that ‘best practice’ varies depending on your particular situation. Yet it is common to see teams fall into process by default.

Continue reading “Process By Default”