Kashmir has been always embroiled in territorial dispute, is known as the world’s most militarized zone but it is also the source for cashmere wool or the saffron.
This is how I see the chaotic IT world, with different profiles disputing their roles and tools, but still responsible to deliver what clients expect: the finest products. Communication is at its lowest, inside the product and development team, every member is hallucinating its own reality. It is something we should explore together, and it comes from a developer that have experience to teach youngster how to start a career in programming, so also use this attitude towards testers in his team, challenging them to do more, to learn more, to stop acting as a support for developer. Would it be difficult if the tester stops a developer for a while and have a short chat? His/her approach could be more valuable before the latter starts building bricks. And instead of writing endless testing plans documents he or she could write some automated tests, where the developer might help if assistance is needed. I think tester’s job is not to act as one user one click to identify developer’s mistakes.
Let’s start a revolution – What if we implement two ground rules:
It’s time to start creating great products as a team, and for this we need to become one that is building software, not documentations, a team that is offering quality, that is responsible for its actions as a whole.
Sli.do – E175