First Paragraph
As a consultant, I had the distinct pleasure of helping several
companies, big and small, to integrate Test Driven Development and Unit Testing
as part of their organizational culture. Some have failed. Those who have
succeeded had several things in common. This chapter combines many of the stories
from both camps.
As with any type of change in an organization, changing people’s
habits is more psychological than it is technical. People don’t like change,
and change is usually accompanied with plenty of FUD (Fear, Uncertainty,
Doubt) to go around. If you plan to introduce this kind of change into your
organization, there are some things you need to consider no matter where you
work.
This chapter is made of four main parts:
§Becoming the agent of
change – Initial steps before you start mixing things up
§Ways to succeed –
from my experience, things contributed to success in making changes to a
process
§Ways to fail – also
from my experience, things which can destroy what you are trying to do
§Tough questions and
answers – most frequently asked questions when introducing unit testing to
a team.
The first thing you need to realize is that this won’t be a walk
in the park for most people, as you’ll see in the next section.
