This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Click to edit Master title style
nFocus Software Testing
e-Innovation Centre
Shifnal Road
Telford
TF2 9FT
Tel: 0870 242 6235
www.nfocus.co.ukNotes MAY accompany this presentation, please select notes page view
So why are we testing? To add value by reducing the risk of bugs in production, increase confidence of a successful deployment and deliver objective information
on the state of the system and the process by which it was developed
• Participate– We are all equal in the workshop room– During scene setting no discussion except for clarification
• Time keeping– Try not to digress– Any one can call ‘digression’ timeout after 5 minutes– Anyone can call a break (within reason)
• Meeting Behaviour– Mobile phones and pagers off if possible (no calls in the workshop room)– Discuss one topic at a time– No side meetings– One speaker at a time– Be clear and concise– Have a positive can do attitude
• Workshop Recording– Flip charts are the record of the workshop proceedings – Silence is seen as consent– Issues risks and dependencies will be recorded and deferred– Important items but irrelevant to this workshop will be recorded and deferred
• Define the problem statement– What are we brainstorming?
• List ideas– Any thing goes even bizarre ideas (often
triggers new ideas)– Be positive ‘can do’ – No evaluation, judgement or criticisms– Try to expand on other ideas– Unlikely that there is a single solution– Revisit earlier ideas