Today I had a conversation with our ‘scrum of scrum’ masters (we have 7 different scrum teams on our product team of 60+) and he asked me why someone would provide ‘developer tests’ as a task for the backlog?
Before I go any further, this is NOT a bait type of email, simply my opinion. If you do not buy into the testing (either TDD or test after) then you can disregard this post. But if you do buy into the testing concepts keep reading.
In order to gain a better understanding of the context I asked my SoS master for more background on this project and what they were doing. After a brief conversation I became very clear to me that this developer did not think of testing as part of his requirement of building out a feature, but rather as a stand alone deliverable that he needed to deliver at the end of the sprint.
I explained that all developers on our team need to stop thinking in this way and to start looking at tests as ‘first class citizens’ when creating code. I believe the exact statement I gave him was:
When developers are creating a feature, the unit tests which prove the feature as being valid is just as critical as the code which implements the feature.
Quite simply, IN MY OPINION if you buy into the testing concepts stop thinking about tests as a second class citizen and start thinking about them as part of your deliverable.
Till next time,
07-27-2009 7:57 PM