Why and how to start a #ZeroBugs policy - part 2
This is the second post of a series about the #ZeroBugs policy. In the previous post, I detailed what a #ZeroBugs policy is and how we tried to apply it. I e...
Recent posts
Why and how to start a #ZeroBugs policy - part 1
Some teams spend 95% of their development time fixing bugs … An entrepreneur I worked with reported an even scarier story. He went bankrupt because bugs were...
Sustainable productivity in eXtreme Programming
eXtreme programming will not improve your short term productivity. But it will drastically improve your long term productivity.
Are Software Developers Overworked or Undecided ?
During the last 15 years, I’ve worked in many different teams. Every team has its own way of working. I’ve been at places where everyone seemed busy all the ...
Mobbing around the world for 48h … who’s in ?
In Far From the mobbing crowd the Cucumber guys explain how they combined mob programming and remote work. Matt and Steve also explain that a mob is both res...
What Rails teaches us about building platforms and frameworks
More than ever, the cheapest way to build a framework is to refactor it out of a specific app.
How to run your first improvement kata
The improvement kata can solve problems that typical retrospectives fail to address. Although there is a halo of mystery around it, it’s actually not that di...
Lessons learned from running our first improvement kata
During the past few weeks, I blogged the story of our first improvement kata.