Peter Gfader's brain noise
Taiichi Ohno (Toyota Prod System) on fooling westerners.

Taiichi Ohno on fooling westerners:

“I’m proud to be Japanese and I wanted my country to succeed. I believed my system was a way that could help us become a modern industrial nation. That is why I had no problem with sharing it with other Japanese companies, even my biggest competitors. But I was very, very concerned that you Americans and Europeans would understand what we are doing, copy it, and defeat us in the marketplace.”

He went on to say that when Americans and Europeans came to visit Toyota that he did his best *to confuse them* as to why Toyota was so successful.
He said,

“I explained it by talking about techniques, like quicker machine setups, reduction of the seven wastes (*muda*) and other techniques with Japanese names like *kanban* and *kaizen*. 

I did my best to *prevent the visitors from fully grasping* our overall approach. Today, I am ready to be open and explain fully what we did. We are now strong enough to deal with any competition.”

I am still amazed by the greatness of this man!



The problem with TDD! #noTDD #TDDisDead

The problem with TDD I think is: 

"TDD is harder to practice and TDD is harder to get ‘right’ than other tools." 

Not saying that your favourite tool is an easy tool to use ;-)


  1. TDD is a combination of: Thinking, Coding, Testing, Refactoring.
    Let alone “Testing”, lots of people (including myself) get already the “Thinking” wrong.
    Here an example of 2010 when I got the Thinking wrong 
  2. Additionally to those 4 there are lots of other skills needed: Mocking, CleanCode, Emergent Architecture, ATDD, …
  3. BTW: Did I say that Refactoring is very hard?

My video interview about: Clean Code, Testing and Continuous Improvement

Is TDD dead? No, its just a tool. #noTDD #TDDisDead

If you havent been on a internet-less island you probably heard about this blog and the google hangout conversation.

Here are my thoughts to that

# Unrelated 

Completely unrelated to TDD/UnitTesting I really enjoyed 2 sentences from the hangout:

"In order to understand/define something, I like to understand how it came about"
Martin Fowler


"If an idea is obviously bad, find a cheap way to try it."
"If an idea is good, someone else has tried it before"
Kent Beck


Read More

Interesting success story of Large Scale Scrum (LeSS) @ J.P. Morgan

What are the experiences of a large group in a tier-one financial services firm adopting Large-Scale Scrum (LeSS)?

Things I wanted to highlight:

Read More

Do you know the effect of releasing less often??

When a release is hard and expensive, we don’t do it often.
When we don’t do it often, we add more stuff to 1 release.
When we add more stuff to 1 release, it gets harder.
Do you see where this is going?

Focus on

Are you saving more than 20% by doing Offshore Development?

If yes, well done. Not many can save 20%!

As just one example, United Technologies, an acknowledged leader in developing offshore best practices, is saving just over 20 percent by outsourcing to India. (For more, read “Inside Outsourcing in India,”

That’s still substantial savings, to be sure. But it takes years of effort and a huge up-front investment. For many companies, it simply may not be worth it.

via “The Hidden Costs of Outsourcing”. Great article worth reading!

5 great reasons for a long 4 week Sprint: #shitScrumMasterSay

Reasons for 4 week Sprints:

- You don’t know how to split PBIs (which is hard for your team)
- You have people work on different projects and only assign 20% to your project
- You don’t have to do that boring retrospective every week
- You can delay the hectic time before the Sprint Review
- You don’t need to remove impediments, since they don’t affect you that much in a long Sprint

Are your 3week ScrumSprints just Mini-Waterfalls?

Why is a 3 week sprint length not so effective in Scrum?

In my experience 3 week Sprints are:
- harder to plan, since we don’t know what we could do in 13 days from now
- harder to establish a rhythm, which is very important for a team to have

Sprints help to reduce complexity, and having Sprints longer than 2 weeks is not helpful in reducing complexity.

Do you know 5 great reasons for a long 4 week Sprint

Are your 3week ScrumSprints just Mini-Waterfalls?

Are your Scrum Sprints just Mini-Waterfalls?

I see “MiniWaterfalls” especially with teams that work in 3 or 4 week Sprints (don’t tell me you do 6week sprints ;-).

The tendency of longer sprints is to fall back in usual behavior and don’t change anything.
If you are in such a team, ask in the next Retro:

What do we need to change in order to half our Sprint time?

If you don’t have any established velocity yet, just adapt the Sprint length now. Make sure to do this with your team.

Solve the root cause, and don’t just expand the Sprint length to fit the work!


A few years ago I wrote

The longer I teach and coach scrum, the more I become convinced that the physical workflow board is the heart of scrum. Without the workflow board, a team has no center, no focus, no hub.

More recent experience has shown me that this heart has no beat. Here’s the problem:…

Do you know the 6 hidden costs of Offshore Outsourcing?

Great article on

The hidden mentioned costs:

  1. The Cost of Selecting a Vendor
  2. The Cost of Transition
  3. The Cost of Layoffs
  4. The Cultural Cost
  5. The Cost of Ramping Up
  6. The Cost of Managing an Offshore Contract

via “The Hidden costs of Offshore Oursourcing”

What is the ideal Sprint length in Scrum?

Or, what is the ideal iteration length in XP?

I would say zero, because that would mean we deliver value immediately.
Isn’t that a nice goal to have ;-)

Some tools that worked well in 1 of our Web Development Teams

Additional to the tools that I use and that are not on Scott Hanselman’s list of tools found here

TFS - Chained Builds

ab.exe - Apache HTTP server benchmarking tool - not a fan of jMeter

Superbenchmarker - ab.exe on steriod

Written in JavaScript that use that uses

Firebug on the Server ;-)

ELMAH (Error Logging Modules and Handlers)

Asset bundling for .NET web apps 

Getting started:

Tools TODO

  1. GremlinJS
  2. PhantomCSS

What do we use in the next project?

  • OneNote as Team Wiki
  • Test & Deployment Setup
  • ASP.NET App Framework via custom ControllerFactory and Custom ViewEngine


Did you know that 1/3rd of all large government IT projects in The Netherlands ends in project termination? via @jessehouwing
Did you know that the cost of worldwide project software failure is about $200 billion?

From the Standish Group

Interesting bits 

However, we have seen many projects that have met the Triple Constraints or successful projects did not return value to the organization or the users and executive sponsor were unsatisfied.

The Triple Constraints are: On Time, On Scope, On Budget.

We think the better approach is to consider return on value than the Triple constraints.

Now… What is “Value”?
And… What is “Success” for you?