Be a problem-solver, not a solution-problemer. (Weinberg)
Each situation is different.
Each situation needs a different approach.
"eXtreme Programming by the book" (Kent Beck's)
is nothing but a theoretical model.
Don't get me wrong,
it's a great theoretical model,
it can be a great help to have such a model,
it's what you need to get a grip on the situation at hand.
But be aware:
Something that worked for you before
is not guaranteed to work again
in a different situation.
It can be dangerous
to view XP as a toolbox,
full of useful utils
you can pick at need.
Before you realize it,
you end up with a
completely
useless
incoherent
set of practices
that are unrelated
and unsupporting.
Build a great team,
They will build great software for you.
But...
if you have felt
only once,
the dynamics
of a good team
you know your goal.
You see which way to go.

We can guide you to the road,
but it's you who'll do the walking.

We join
new or existing project teams,
we merge with them.
We uncover
the worst problem areas,
propose changes,
and implement those changes
together with the team.
We build in frequent check points,
evaluate the results,
in dialogue with the team,
and feed those experiences
back into the process.

Working this way, we evolve towards a process that's fit for your team, in your company. Knowledge can be transferred in an easy, smooth and natural way.
Our goal is that the team can do without our advice as soon as possible.