This tutorial covers the Elective area of the Test Management Body of Knowledge (TMBOK) required for the Certified Test Manager (CTM) certification. This tutorial also covers the Elective area of the Certified Software Test Professional requirements.

The TPI® Model of Test Process Improvement described by Tim Koomen and Martin Pol provides what many consider to be a more appropriate test-process-specific alternative to traditional level-based capability maturity models. In contrast to one-size-fits-all models, TPI® describes two to four levels of maturity within each of its 20 key areas and offers organizations the ability to define their own priorities profile or to follow the suggested controlled, efficient, optimizing overall maturity sequence. The model is a structure to be applied by skilled test professionals and does not define the specifics for judging how well a particular test process fits the model. This interactive workshop addresses the specifics of how to apply the TPI® Model's structure to assess and guide improvement of one's own actual test process. Techniques also are suggested for overcoming resistance when getting started. Exercises enhance learning by allowing participants to practice applying practical techniques to realistic examples.

WHO SHOULD ATTEND: This course has been designed for test, project, and system managers, as well as for testers, analysts, designers, programmers, auditors, and users who are concerned about the efficiency and effectiveness of testing within the overall development process.

• TPI® Model structure key areas, levels, checkpoints, dependencies, and maturity matrix.
• Selecting an individual priority profile vs. pursuing predefined maturity levels.
• Developing more specific criteria for assessing whether one's test process satisfies model checkpoints.
• Suggesting and implementing specific test process improvements.
• Limitations and issues with the model and process improvement efforts.

• PROCESS VIEW OF TPI® MODEL
  • What a process is, and is not, why it matters
  • Distinguishing “real” from “presumed”
  • Defined and documented processes
  • General maturity model concepts
  • Why individual test process models are needed
  • Level-based vs. continuous models
  • Model vs. methodology
  • Key area mapping to methodology
  • TPI ® Model structure key areas, levels
  • Priority profile vs. predefined maturity levels
  • Presumed key area priorities for addressing
  • Dependencies among key areas
  • Using the model to assess current test process
  • Internal vs. external assessments
  • Suggesting improvements
  • TPI® Model usage survey results
  • Limiting issues with all maturity models
  • Compliance with activities vs. how well
  • Relating test process to software quality results
• ASSESSING KEY AREAS
  • Adding structure to checkpoints judgments
  • Level-1 presumed priority key areas
  • Test strategy [ IEEE Standards]
  • Life-cycle model [ Proactive Testing™]
  • Test specification techniques
  • Commitment and motivation
  • Reporting
  • Defect management
  • Test process management
  • Level-2 presumed priority key areas
  • Moment of involvement
  • Communication
  • Testware management
  • Level-3 presumed priority key areas
  • Estimating and planning
  • Test automation
  • Test environment
  • Office environment
  • Test functions and training
  • Level-4-6 presumed priority key areas
  • Static test techniques
  • Scope of methodology
  • Low-level testing
  • Metrics
  • Evaluation
• IMPLEMENTING IMPROVEMENTS
  • Issues with presumed priority sequence
  • Need for measures and baselines up-front
  • Defining and carrying out improvement projects
  • Evaluating effectiveness of testing, improvements
  • Ongoing monitoring and adjustment
  • Reporting, using measures to improve
  • Gaining management, development buy-in