Proactive Testing Management

Organizing and allocating resources for repeatable, effective, wanted testing
1 Day Intensive Seminar Workshop

The effectiveness of our testing is determined by the process we follow. This is true whether or not we are aware of the process that’s really being followed and regardless of whether it is the intended process. This interactive workshop shows how to structure the real process to accomplish more of the important testing in limited time while actually enabling earlier software delivery. Keys to success are (1) using Proactive Testing™ to save people time, effort, and aggravation; and (2) applying proven techniques for reliably estimating required time, effort, and resources for the test project. Exercises enhance learning by allowing participants to practice techniques with an actual case.

Participants will learn:

  * How to identify, improve, and manage the real testing process.
  * A structured Proactive Testing™ process that yields better software and also cuts development time.
  * Roles and responsibilities users, developers, and testers should and should not have.
  * Keys to gaining cooperation, support, and even advocacy for testing.
  * Systematic scalable risk-based planning of testing as a project that gets accomplished.
  * Methods to reliably identify, estimate, and control testing task effort, duration, and resources.

WHO SHOULD ATTEND: This course has been designed for systems and test managers, testers, analysts, developers, and others who plan, oversee, and/or carry out testing of software products.



  • Typical testing is unaware of its process
  • Why a process approach is necessary
  • Why most change efforts fail
  • Recognizing the REAL testing process
  • Reactive testing—out of time, but not tests
  • REAL process needs for value
  • One tester vs. two
  • Independent test group issues and strengths
  • Defect injection, detection economics
  • Conceptualizing testing levels, objectives
  • Relation of requirements and testing
  • Business vs. system/software requirements
  • Acceptance and technical testing distinction
  • Respective roles of developers, testers, users
  • Proactive Testing™ better, quicker, cheaper
  • How testing can save the developer’s time
  • Secrets for overcoming resistance to testing
  • Applying the process in the “real world”
  • Overcoming “We don’t have time” fallacy


  • Testing is primary means of risk reduction
  • Test planning structure and advantages
  • How test plans fit into the testing process
  • Prioritizing and focusing level by level
  • Giving testing equal project plan status
  • Reusing Test Designs and Test Cases
  • Responsibilities for Master, Detailed Plans
  • Determining the testing approach
  • Assuring resources will be ready
  • Agreeing when testing is “good enough”
  • Proactive and reactive risk analysis
  • Preventing showstoppers and excess rework
  • Stomachache metric that assures buy-in
  • Defining detailed tests to reduce the risks
  • Letting testing drive development


  • Top-down vs. bottom-up sizing techniques
  • Avoiding the major cause of estimate errors
  • Tasks needed to carry out the testing
  • Monitoring milestones and checkpoints
  • Tracking and categorizing defects
  • Gaining management attention to defects
  • Defect age measure of test effectiveness
  • Projecting ship date from defects
  • Defect detection efficiency, effectiveness
  • Testing WIIFMs for developers, managers

Upcoming Events
About Go Pro
Contact Us