The ideas put forward in this document are my own and they were neither borrowed nor copied from any other sources. These were born out of the theme of the Software Testing Conference - 2010, India.

2. Create an industry standard model to follow that allow organizations to grow within as well as from a global perspective.

3. This model is applicable to software services organisations who provide development and testing services to customers.

4. Software Product organisations can follow this model to build robust, quality, reliable, and early time-to-market software products.

5. This model is applicable to every role within the software development/testing lifecycle, i.e, the manager, lead and the engineer.

7. Agility of the organisation: Means to manage the ever-changing/agile Business Processes in the future.

8. Anticipate at-the-moment new business requirements from the customer.

9. Agility of the team: Means to build an “agile” not a “fragile” test team.

10. Flexibility of the testing techniques used.

11. There a lot of trainings made available in the organizations on development i.e, JAVA, C, C++, , .NET etc. But are there enough for testing as well ??? Define a training/project readiness plan specifically based on test activities and techniques for the test team members before directly assigning them to any projects.

12. Gather the team prior to the beginning of the project and strategize the execution per tester.

13. Agility of the individual: Means to provide tester independence.

14. Testers trained to apply different techniques to the system during execution.

16. Frequent communication with the customers. Understand their business and anticipate new requirements based on their time-to-market needs.

17. Selecting the appropriate development lifecycle . Agile and V - model have their own advantages and disadvantages.

18. Train your team to adapt to new test techniques. Strategize !

19. Encourage maximum exploratory testing along with automation during regression.

20. Well-trained team can be capable of switching gears during execution in time-based projects.

21. Have a separate automation team. Allow them to work independent of the other testers.

23. Maximum customer satisfaction.

24. Granting the tester his/her independence during execution. Instill confidence in the tester. It would definitely motivate him to do more. Makes feel he/she has achieved a milestone.

25. Different techniques applied during execution to the system as a whole. Ensures almost complete coverage of the requirements.

26. Providing complete metrics to the management as a result of different techniques used and ensuring optimum coverage.

28. Provide the management with the visibility of the test activities.

29. Involve OR Communicate to the team of the regular updates about the project from the stakeholders. Neither isolate the team from the management discussions and decisions unless they are really necessary nor involve them too much and vice versa.

30. Rotate the testers to work on different techniques on every project. At the end of the day, tester skills count in his/her resume.

32. Agile vs V – Which model to use? Both yield better results in their own way. Depends on the type of project and the necessity of the customer. Agile for smaller projects with less time-to-market. V-model for projects which have high expectations and therefore need utmost importance on development and testing activities to be carried out. Decide the best option. Be flexible!

33. Maximum usage of exploratory testing and heuristics during the final regression testing before the final product goes to the customer. At the end of the project, the customer is the layman. He will be interested in the end result/business objective and not in the “statement coverage of a module”.

34. Apply different test techniques i.e., Static testing (Test basis review, Documentation review), Black-box (BVC, EP, Decision-based, state-transition etc), White-box (Statement coverage, Decision coverage etc), Risk-based, Defect-based testing during system test execution.

35. Break the software in as much ways as possible within the scope of the requirements.

36. Provide tester independence to apply his best skills during execution, the ones he is good at.

37. Create a balanced ecological system with the development team.

38. Encourage feedback to the management from the team members on the way the activities are to be carried out and schedule to be met and vice versa.

39. Heed to the testers! They are the smaller shining carbon crystals of the diamond.

40. Rotate the test team to adapt to change. It would improve their skills and help gather rich experience.

41. Have a separate independent automation team. Manual and Automation testing need to exist in harmony. Negligence of one over other reduces the quality and coverage.

43. This can be achieved only by having a separate autonomous testing unit within the organization.

44. Also, create an elite panel of experienced testers who can train new recruits on the different testing techniques and strategies to be used on the job.

45. Why should always the testing team be at the receiving end from the stakeholders and the customers??? Encourage feedback from the test team. Listen and Oblige!

47. The A-A-A model should be implemented in a way that the customer is assured of quality as well as the time-to-market delivery.

48. Demonstrate and exhibit the robustness of the team.

49. Reveal the strengths of the team gained by the implementing the model.

50. Go for the Agile model or the V-model. Display that we have the experience on working on either of these powerful development lifecycles.

51. Demonstrate the agility.

52. Show the easy and efficient adaptation to their sudden needs and requirements.

53. Create valuable confidence in them.

54. Look forward to achieve and Win!