Don’t give us unexpected or surprising information”

Just got a curious instruction from a product manager: Bugs logged in sprint 3 should focus on functionality delivered in sprint 3 or previous sprints.”

I take issue with that; It’s a tester’s job to highlight holes in requirements, specifications, architectures, implementation choices, missing features — and, yes, in implemented functionality too. If we restrict ourselves to only the latter, we’re not doing our job as dispassionate investigators. A tester’s job is to highlight shortcomings and risks of any sort so that product managers and technical experts can make informed decisions.

The message I hear in that instruction is Don’t give us unexpected or surprising information”. You may not want to hear it, but I’m going to continue to do that.

September 20, 2010

Previous post
Testing luminaries This post has moved across two blogging platforms during its life. I preserve it here as a snapshot of my thinking about testing at the time I wrote
Next post
Building testable software We’ve all worked with software which wasn’t designed with testing in mind; as developers and as testers, many of us will have been stung by this.