190 likes | 352 Views
The Dandelion Model – so far, so good TM Summit London, January 29 2008 Anne Mette Jonassen Hass, DELTA, amj@delta.dk. DELTA. ”We help ideas meet the real world”. We are not all alike. Different things make different people thrive. Our vision.
E N D
The Dandelion Model – so far, so good TM SummitLondon, January 29 2008Anne Mette Jonassen Hass, DELTA, amj@delta.dk
DELTA ”We help ideas meet the real world”
We are not all alike Different things make different people thrive
Our vision We would like your help in creating a model that helps you match your personality to a job where you’ll thrive and add value to the company and yourself We do not have the final answer yet!
Tester skills - overview Testing skills Soft skills IT skills Domain knowledge
Workshop at EuroSTAR 2007 • Identify ‘negative’ personality characteristics • Identify activities to be performed by testers, divided on 4 testing roles • Match the ‘negative’ characteristics to roles (if possible) • Translate the ‘negative’ characteristics to ‘positive’ characteristics (if possible)
‘Negative’ characteristics , version 1 • Introvert • Irritating • Jump to conclusions • Lazy • Mistrusting • Naive • Opinionative • Overcritical • Overoptimistic • Paranoid • Pedantic • Pessimist • Rigid • Selfish • Skeptical • Stubborn • Tempered • Uncooperative • Undiplomatic • Unhelpful • Unsatisfied • Unstructured • Unsupportive • Whimsy • Wishy-washy • Anarchistic • Anxious • Argumentative • Arrogant • Competitive • Confused • Demanding • Dictatorial • Dishonest • Disorganized • Dogmatic • Inconsiderate
Test manager tasks • Delegation • Leading • Follow-up • Improvement • Teaching • HR • Self-learning • RE (? – the authors’ question mark) • Estimation • Budget • Planning • Strategy • Resources • Reporting • Coordinating • Motivation • Information • Communication • Coaching • Delegation
Test analyst / designer tasks • Risk identification • Risk analysis • Mentor to junior testers • Identify test conditions • Inspection • Identify test data • Selecting test technique(s) • Clarify ambiguity (requirements) • Design test cases • Exploratory testing (charter) • Communicate with development / customer / shareholder • Identify test environment • Review the test basis • Reporting – test coverage
Test environment responsible tasks • Evaluate tools • Smoke test (readiness) • Extract data • Populate data • Masking data • Set up and maintain hardware / interfaces • Build and deploy software • Run environment (mainframe / batch / online) • Release management • Version handling • Baseline • Reset environment to original state
Test executer tasks • Bug report • Log test results • Execute tests • Improve tests • Be surprised • Analysis of observations • Investigate • Review requirements and give feed-back • Read design to understand • Analysis of quality • Explore the system • Communicate • Hands on
Further work • Getting a ‘complete’ list of ‘negative’ characteristics • Provide a definition of each of the characteristics • Provide a ’positive translation’ of the characteristics • Provide ‘complete’ list of testing activities • Provide detailed mapping between characteristics and activities • Maybe add ‘positive’ characteristics as well
First feeble attempt Let’s get going…
Remember • Test is difficult • Test requires overview • Test requires creativity • Test requires systematic work • Test requires imagination • Test requires courage • Test is fun