Software testers often have great difficulty in quantifying and explaining the value of their work. One consequence is that many testing projects receive insufficient resources and, therefore, are unable to deliver the best value. Derk-Jan de Grood believes we can improve this situation although it requires changing our mindset to "result-driven testing." Result driven testing is based on specific principles: (1) understand, focus on, and support the goals of the organization; (2) do only those things that contribute to business goals; and (3) measure and report on testing's contribution to the organization. Keeping these principles at the forefront binds and guides the team. Join this session to find out how the test team at Collis has adopted these principles. They have developed a testing organization that generates trust and provides valuable insight into the quality of their organization's products.

Testers are professional critics. Our job is to evaluate and criticize other people's work. Although criticism can have a positive meaning, it is more often taken as negative. When we communicate our criticism to other people, we are sometimes misunderstood, and this can lead to serious problems, including losing confidence in ourselves. Dorothy Graham examines how our delivery of criticism and the ways we communicate can make us more effective-and not damage our interpersonal relationships. Dorothy presents a communications model that helps explain how and why personal interactions can go wrong. Both the "push" and "pull" styles of influencing can help us communicate better with our managers. Dorothy explains how your confidence level affects your ability to constructively criticize others' work and communicate test results. She concludes with valuable tips for increasing your confidence.

John Scarborough recounts the aftermath of a test project failure that stunned engineers and managers alike. The project was highly strategic yet very challenging. Team members were proud to be assigned to it. Early warning signs did not go unheeded. However, after the customer rejected a release of code, confidence plummeted, and the controls that the team had put in place were no longer sufficient to keep deliveries on track. The harder they worked, the more their deficiencies became apparent. Fortunately, all was not lost. Through a defined retrospective process with open and sometimes painful self-assessment, the team was able to deliver a positive study that led to overhauling and improving the company's processes for quality management. Take back an approach that can lead you from failure and disappointment to progress and success.

• How to establish an atmosphere of openness and candor

So you have been asked to start or improve a testing group within your organization. Where do you start? What services should you provide? Who are the right people for the job? Iris Trout presents a framework of best practices needed to implement or rapidly improve your testing organization. Hear how Bloomberg LP, a large financial reporting institution, tackled the issue of implementing a new testing organization. Iris describes how she built a strong testing process in minimal time and achieved exceptional results. She shares her interviewing techniques, automation how to's, and many other ways to implement quick successes. Learn to create Service Level Agreements. Discuss the value of peer reviews and how to evaluate their results. Iris shares handouts full of user-friendly ideas to help you get started.

• The essential components of a strong testing organization