Can we get better? 1% at a time!
Ajay Balamurugadas
Creative Problem Solver, Passionate to learn, love to motivate people to achieve their goals
We are lucky that there are no standards in testing. There is so much diversity and variety in contexts that there are unlimited learning opportunities.
Different Experience Levels
============================
# No professional experience or only theoretical experience of software testing
# New job with prior experience of hands-on software testing
# Coming back to software testing after a break
# Starting software testing after working in a different profession
# Veteran of software testing
Different Domains
=================
Insurance | Education | Gaming | Finance | Ecommerce | Retail |
Emerging Tech and much more
Different Quality Criteria
===========================
Functionality | Usability | Security | Automation | Performance |
Scalability | Accessibility | Compatibility and more
Different Models of working
===========================
Agile / Scrum / Lean / Kanban / Waterfall / Customized Agile /
Strictly by process
Different Platforms/Layers
==========================
Desktop/Web/Mobile/API only | Multiple platforms/layers(UI, DB, API)
Even with so much diversity, most of us want to improve. The goals are big, sometimes vague and most of the time only on paper. My point is - as we all want to improve, can we improve 1% at a time, consistently across all areas so that when it adds up, leads to a bigger and significant gain.
Let me walk you through an example:
No one likes when the customers report bugs after production release.
So what would be some kneejerk reactions?
Instead, we could focus on the critical factors that contribute to this problem and target to solve them. What if we don't have any problems as of now but want to improve, can we focus on all the areas and improve by 1% in each of them?
Questioning and Documentation
For any release, there might be discussions with different stakeholders. What if we improved our questions? What if we made more useful notes in each meeting? If we never had the minutes of the meeting sent, can we start sending the minutes? If we are already sending the minutes, can we save time by removing the redundancy or improve the format of the minutes? If we are already following a specific format, can we target to finish on time and stick to the agenda? If we are not wasting any time in meetings, can we target to shift the meeting to emails/chat and save the meeting time?
领英推荐
Understanding the Design
Can we record the meeting so that we save time explaining the same design to multiple people? What if we shared the recording well before the meeting or shared it in a common pre-defined location so that everyone knows where to find it? How about contrasting and comparing multiple designs at this stage than just going through one design? What if we include all the stakeholders and share the impact of each design on them?
Dev Tests
What if we discussed the code at this stage itself? What if testers and developers discussed ideas on how to test a particular design? What if the testers shared the probable bugs even before the code is developed? What if testability is incorporated from the first line of code?
Test Ideas
Think about the scenario when the priority of ideas and scope is clearly discussed with the stakeholders. The focus is on finding the more critical bugs? What if the bug reports are 1% better - maybe the right attachments, logs? If they are already present, the follow-up test results are also included?
Tools
The right tools are used from the start. The tools that can save us time. The tools that help us discover the right kind of information. The tools that prevent us from making blunders.
There are many more such areas where we spend a lot of time while testing. What if we improve in each of those by just 1% to start with?
Happy to discuss more. I am still thinking more about this idea.
Maybe, I will improve this thought by 1% in the coming days.
What do you think about this idea - 1% improvement at a time?
Senior Software Engineer - IBM Security - MaaS360
3 年"There are no standards in testing." Because I believe primary objective of testing is 'exploring' and it's never ending process, And having standards will not make much sense and also the expectations keeps changing from time to time..!?
True believer of incremental change, not just in testing!