Software Testers – Do we think a step ahead?

Posted on

As Software Testers we have a fairly important role to play as representatives of the Customers in ensuring we deliver a Quality Product within the expected framework of Customer’s Expectations. However, that said, we also bask in a seat where we are used (need) to Wait on Requirements, Wait on Implementation Details, Wait on Design Overviews and Wait on Information to be shared and provided by other stakeholders before being able to do testing

In such a kind of situation what is the value addition that we present as Testers in the Software Development Life Cycle. I would like to seek ideas and suggestions on how QA can help in presenting value addition in being more effective and efficient in its engagement.

My question is how can we truly be a Step Ahead of the rest and make sure that we are true partners in pre-empting any issues that were not thought about in the right time and ensure that the right questions were asked at the appropriate time.

Are there a few secrets or traits that can help facilitate Software Testing teams to be more effective and efficient in this journey across the SDLC

Advertisements

2 thoughts on “Software Testers – Do we think a step ahead?

    Pankaj said:
    December 30, 2013 at 5:42 pm

    This is precisely the situation we faced a year back where we were not sure if we were providing any value add to the team (apart from testing of course). However, we tried an approach to get involved in all the phases right from requirements gathering to design and implementation, rather than just waiting to test when our turn comes.
    The results of this exercise has been amazing where now we know what is to be tested in the future release also and have the test strategy ready for it. This is after we have asked more questions during requirements gathering, provided our inputs on design and did a round of alpha test before the actual testing started. Moreover, we have been very effective by the way of implementing some tools/utilities for the team which makes the work for all easy.
    Also, this is only possible by active participation be dev team and client as well.

    mandyamsrinivas responded:
    December 31, 2013 at 7:15 am

    Hi Pankaj, Thank you for the crisp and simple terms you have indicated for testers to be effective. I fully agree with your comments, the means might seem simple but drives effective outcomes.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s