In response to increasing market demand for high performance applications, many organizations implement performance testing projects, often at great expense. Sadly, these solutions alone are often insufficient to keep pace with emerging expectations and competitive pressures. With specific examples from recent client implementations, Scott Barber shares the fundamentals of implementing T4APM™, a simple and universal approach that is valuable independently or as an extension of existing performance testing programs. The T4APM™ approach hinges on applying a simple and unobtrusive Target, Test, Trend, Tune cycle to tasks in your application lifecycle—from a single unit test through entire system production monitoring. Leveraging T4APM™ on a particular task may require knowledge specific to the task, but learning how to leverage the approach does not. Scott provides everything you need to become the T4APM™ coach and champion, and to help your team keep up with increasing demand for better performance, regardless of your current title or role.
Scott Barber
Chief performance evangelist, Scott Barber is a respected leader in the advancement of software testing practices, an industry activist, and load testing celebrity of sorts. Scott authored several books―Performance Testing Guidance for Web Applications, Beautiful Testing, How to Reduce the Cost of Testing, and Web Load Testing for Dummies―and more than 100 articles and blog posts. Founder/president of PerfTestPlus, Scott co-founded the WOPR, served as director of the AST and CMG, and is a founding member of ISST. His industry writing, speaking, and activism focus on improving the effectiveness and business alignment of software development practices. Learn more about Scott Barber.
Testers frequently feel that they and their contributions to delivering software are undervalued. These feelings may stem from patterns of important defects being de-prioritized, receiving lower salaries than their peers who code, being assigned seemingly pointless tasks, or being expected to “test comprehensively” with insufficient time and resources (that tend to shrink as the target release date approaches). If you’ve experienced these feelings, you’ve probably wondered “What does senior management value if not the information testers provide?!?” If so, here are some answers. After fifteen years of working primarily in and around testers and testing, Scott Barber had the opportunity to serve as a product owner for a family of products. Join Scott as he shares lessons he learned, responsibilities he was given, ways his own thinking about software testing and testers evolved, and the somewhat surprising expectations he came to have of testers and testing for his products—after he became “senior management.”