Jul
09

XP Day Benelux Call for Sessions closing

Don’t forget to send in your session proposal for the XP Days Benelux 2005 conference on 17-18 November 2005 in Rotterdam, The Netherlands.

The Call for Sessions closes on July 11th.

I’m just about ready to send in my session proposal. Are you?

Jul
07

Step 6 of the 5 Focusing Steps

You’ve been applying the Theory of Constraint’s 5 Focusing Steps and you’ve been able to increase throughput of your system/organisation. But you’re running out of ideas to get more throughput. What now?

Try the 6th Focusing Step: Change The System

Changing a system is hard. You’re up against years worth of accumulated rules, regulation, processes, tacit knowledge about “the way we do things ’round here”. Like Laurent says many of these rules have accumulated over the years. Maybe they were effective at the time, but they failed to adapt to a changing world and are now holding back the organisation.

And people don’t like change.

As that eminent business consultant Machiavelli noted: “He who wants to change the organisation will only get lukewarm support from those who stand to gain from the change. He will get fierce opposition from those who gain from the current situation“.

How can you make changes easier? Here are some tips that sometimes work for me:

  • Involve those who will be affected by the change in shaping the change. Nothing worse than having a change foisted upon you.
  • One thing at a time. If you change several things at once, the change becomes very complicated and it’s hard to tell what worked and what didn’t. If you perform regular, incremental changes, people get used to the rythm of change.
  • Let people “taste before they swallow”. This is an expression by Virginia Satir (via Jerry Weinberg and Nynke Fokma). If you encounter a new idea, have a taste of it. If you don’t like it you can always spit it out. Only swallow it when you like the taste. Propose that people try the change for a set period, after which there will be an evaluation. The change is instituted if the evaluation is positive. Make sure that the evaluation is genuine and not a rubber-stamp process.
  • Trust me, I know what I’m doing. This is a tricky one… When people are afraid of a change, a little show of confidence can pull them over the line. And now you’ve put yourself on the line…
Jul
06

The 5 Focusing Steps. Or is it 6? 7?

I’m still (slowly) adding stuff to the Theory of Constraints series on my site.

There are 5 focusing steps:

Okay, that’s really 6 steps.

Is that the end of it? At the XP2005 session on the Theory of Constraints we discussed a further step when the “5 Focusing Steps” run out of steam.

More about Step 6 tomorrow.

And then I’ll write up the results of the Toyota Way session at XP2005

Jul
05

Documenting Wiki2Go

No time to write in the blog or continue on the Theory of Constraints series today.

I’ve been updating the documentation for the Wiki2Go wiki that is used to host, amongst others, this site. It’s quite easy and fast to set up if you know what you’re doing. And I do. But others are now setting up Wiki2Go sites and are asking how to do it.

As Fred Brooks says “A programming product costs roughly 3x as much as a program.” As others start using and developing Wiki2Go I have to invest in (user and developer) documentation, installation tools, administration user interfaces, deployment…

Brooks describes another type of product, a “Programming System Product” like the operating system he worked on before writing the book. This one costs 9x as much as the program itself.

This should serve as a warning to framework writers: how much more costly is your framework than writing the code? 3x? 9x? Are you sure you will recuperate that investment? Will programmers write their applications 3x faster? 9x?


If you’re interested in developing Wiki2Go, the project is now hosted on Rubyforge


TheMythicalManMonth And read this book!

Jul
04

Theory of Constraints

I’m writing a series of notes on the “Theory of Constraints”, based on the “I’m not a bottleneck! I’m a free man!” sessions at XP2005 and SPA2005.

Why did I get interested in the Theory of Constraints?

  • It gives me a different perspective to look at systems and organisations
  • The Theory of Constraints is very simple. But the conclusions one can draw from it are often wonderfully counter-intuitive, yet very effective
  • It is a complementary tool to “Lean Thinking”: ToC tells you what to optimize, Lean tells you how to optimize. ToC focuses the system optimization effort where it has the most effect.
  • ToC is a whole-system method. Local optimisations often have detrimental global effects. ToC helps me look at the whole system and then take action at the local level (the bottleneck).

Read more about it:

TheGoal ItsNotLuck ThinkingForAChange