Professional Documents
Culture Documents
Peter Gfader
View profile
Unless you try to catch the attention as I do in this blog post ;-)
Boom! After that class, he was on a mission to convince everyone that TDD
is the only way to do things.
The 1st day back at work he talked about improving the team and trying
TDD and got the following statement from his colleague:
Henri (made up name): "I don't write any tests since I am not a tester".
I know he handled the situation quite well, but he asked me for advice.
One thing to consider is the underlying question to this, which might be:
"How do we get people to change their behavior?"
● Why is the practice or tool that you are suggesting any better than
the current way of doing things?
● Can you explain the value in the proposed change?
● Can you lead by example?
● Do you have enough patience and skills to teach others?
Roles?
I see this a lot, that people are focused on their role, forgetting the bigger
picture of the team and purpose of the work they are doing.
We learned too often that documentation gets out of sync too easily. I
blogged about the "Why are *automated tests* so important?" on my
personal blog.
Quality
Quality is everyone's responsibility in a Scrum Team. There is no QA Team
in a Scrum context, which means the whole Scrum team is responsible for
delivering high-quality software that works and is fully tested.