I test software.
I learn how the software behaves and report on it.
I do not break software.
I exercise software and look to address the questions of stakeholders around how the software works.
I consider formal "Requirements Documents" to be information points for my investigation, nothing more.
When the software is being developed or modified, I look to the reason why it is being developed or modified, not merely how.
I look for the need the software is intended to fill and the wish the software is intended to address.
I look for the value people wish and hope the software to bring.
When the value and business purpose, as stated by the stakeholders and sponsors of the effort, is not being achieved I stand up and say so.
When the "Documented Requirements" are not in alignment with the value and business purpose, as stated by the stakeholders and sponsors of the effort, I stand up and say so.
I say these things openly, in public, not in a closed room.
I look to see how I can contribute to the effort beyond exercising software.
I look to see how I can support the BAs in representing the wishes and desires of the stakeholders and sponsors of the effort,the customers on whose behalf we are working.
I evaluate and exercise stated requirements and search out those that are presumed.
I look to see how I can support the designers and developers in clarifying what is meant when documents are unclear.
I evaluate and exercise designs.
I try hard to smooth the effort and move work without sudden jerks, fits and starts.
I try to build consensus in the team over the behavior of the software and how it relates to the stated intention and purpose.
I try to speak for the customer when no one else does so.
I do not assure anything.
I challenge assurances.
I challenge assumptions.
I challenge presumptions.
I challenge the status quo.
I challenge my role on the project.
If I can not add value on a project in any way, I say so and withdraw when that is the best thing from the project, the group and the larger organization.
I help raise people up.
I help colleagues see what is possible, not merely what is now.
I help them be better at their craft when they express a desire to be better.
I strive to become better at my own craft and work to learn more.
I am not a master; I am an apprentice constantly learning my trade.
If people look to me for assistance, I will give it if it is in my power to assist them.
If people do not want assistance, I do not impose my assistance on them.
I try to make things better.
I try to make software better.
I try to make communication better.
I try to make myself better.
I am a software tester.