• Home|
  • Blogs|
  • 3 Keys how Developers and Testers can display best productivity and help Best Software Delivery!

3 Keys how Developers and Testers can display best productivity and help Best Software Delivery!

I request readers to put your comments on this article as I am trying to put my software delivery floor experience in words. Most of us who been in software deliveries can give better inputs.

Since years I have been working for Software Development Life Cycle (SDLC) for many international giant businesses. Most of the times I worked closely with two important tribes ;-) of Software Industry one is "Developers" and another is "Testers".

Many times I have seen that they work parallel both has different approach to show their productivity or quality of work. Once requirement is clear, development team starts with approach "How to make it best final delivered product!" and testing team start thinking "What are different reasons where code can be broken!"

If we look at their thinking, it clearly shows that each one of them want best software delivery as part of team. Most of the times for 3 developers there is only one tester assigned for delivery as standards.

According to me below are three keys which needs to be taken in account to get best software delivery from each one of them.

1. High involvement of development team and testing team during requirement understanding phase is needed. In my experience most of the time, brainstorming on requirement understanding helped lot to identify defects in product before development phase starts.

2. Generally in software delivery productivity of team mate is calculated based on below parameters.

For Developer - how many bugs opened for his/her code by testing team.

For Tester - how many bugs identified by him/her during testing phases.

First thing is we need to change these parameters to judge their productivity, instead putting below parameters as common for both developers and testers.

How many inputs given during requirement analysis by each of them to fine tune requirement gaps.

How closely developer and testers are working during development phase itself, so as code will have hardly any bug during testing phases.

3. Both developers and testers should understand that even though their job profile makes them to think differently, but final outcome is high quality of delivery which will come as outcome of their contribution as best one team instead of sub teams!

GrassDew has four main business streams – Consulting Services, Software Solutions, Security Services and Knowledge Services. Our primary focus is on various software development and maintenance services.

To know more about our services, email us at shekhar.pawar@grassdew.com