We have gotten into the habit of thinking deeper about one topic on a weekly basis. We pick topics based on anything interesting we read - so the topics can range from 'how to express the value of testing' to 'Dieter Rams' design principles' to 'effective remote work habits'. Employees are guided to spend no more than one hour researching the topic online. The emphasis is on coming up with their own ideas and interpretations. We then meet as a group to exchange ideas. I love this habit and consider it one of the more unique benefits you will enjoy at Qxf2.
Painters produce paintings we can see. Writers produce stories we can read. Actors make movies we can watch. Cooks have dishes we can eat. We produce artifacts like test cases, automated checks, tools - but they are like the paint brush, type writer and utensils. What is our output?
Information about risks. High probability low magnitude. We can explore manually, flagging risks. key information. when things go wrong, users perceive product. Output is how do u describe. Mind map, acc model. Key is to communicate with others. Things which u have to look at. What we produce we should show. Risks
Tough to judge our output. Its like we Testers play a team game. In cricket we bat or bowl well still loose match all will complain. We can field well but miss one run out chance all will complain. So its hard to guage our contribution. So whole team performance with ours in important. Output is context dependent. Feedback about the product to the stakeholders and build confidence about their products is one of main output
Product which meets end users requirement Developer is like builder we tester find the flows so that building doesnt collapse. We find flaws in a system. Meet the customer satisfaction
Tester can find bugs. Testing output depends on stakeholder. Some people expect risk impact analysis. Developer gives value in case we show them defects. Testing output varies.
Testers are like police officers. Get Judged on what u missed. U miss bug u r questioned on ur testing. How we test at qxf2 for new client. We come up with a minimal viable product. We build on it. Also spoke about bike-shedding
© Qxf2 Services 2013 -
