Lean + Six Sigma = Love or War?

Too often you see Lean/Six Sigma as if it is one and the same. Is it a good love match, or is it a disaster in the making?

Both claim to improve processes through eliminating waste. However, Lean and Six Sigma define and reduce waste in a very different way.

Below a very short but accurate description between the core differences and the consequences for applicability.

KANBAN in s/w development (2)

KANBAN in s/w development is quite different from Kanban in production. Although both are visual planning systems using cards, there are significant differences as well.

Cynefin ...putting the bits and pieces in relation

Dave Snowden has a wonderful framework called Cynefin.
Dave is still in the process of developing it. The good thing is he put everything on his blog, the bad thing is, you need to find the bits and pieces.

Below you'll find a presentation that links all the different Domains and the title brings you to the latest blog on it.

(N)PCA an addition to LEAN thinking?

Those applying LEAN are familiar with AVA and NAVA; (Non) Added Value Activities. Of course Added Value is seen from the customers' perspective. It is very beneficial to look at a process based on AVA and NAVA. But is it sufficient?

When an activity is of Added Value, does it mean that the customer is willing to pay the cost for it?

Some of my achievements

The achievements are the result of a team. I do know that in all the cases below, without me, it would not have been easy or possible at all.

Sometimes I had to teach myself new things. Sometimes I had to completely develop new things).

Busy with BPR-Toolbox

Past couple of weeks I've been busy helping to further develop the BPR-Toolbox from Eforis.

From a personal perspective a very nice and interesting job. Lots of stuff going on, working with really smart people that like to push things and be reasonable as well. One of the first requirements was: we want a sexy application. Given the feedback we get, we managed this nicely.

MIN=MAX-rule

What is needed minimally to achieve the objective, is the maximum we're going to do. This is the  MIN=MAX-rule.

Projects tend to have some unnecessary and missing 'luggage'. The MIN = MAX-rule is ideal in determining the scope of projects. A good remedy for scope screep. And, it is also a good way to decide to included things while this was not obvious within the scope.