Another way to manage performance testing it to track it for specific changes that raise performance concerns. If a specific story creates a performance concern, require performance testing for that story. In the past, I've asked several times for performance test results as part of my acceptance criteria for certain stories.
Finally, if the team is doing enhancements to an existing system, and the performance concern is really focused on a concern around regression, then I'll often just have the testing team run comparisons to our baselines on major releases. For that, you'll need a set of scripts and baseline numbers you use from release to release. They only need to focus on the big things, and should be fairly easy to keep up to date, interpret and manage.
Dig Deeper on Topics Archive
Related Q&A from Mike Kelly
Creating user acceptance tests out of basic software requirements documents can be a daunting task. Expert Mike Kelly points out logical approaches ... Continue Reading
Expert selects preferred performance testing tools for data warehouse/BI software testing needs. Continue Reading
A software testing expert explains why performance testing scripts are frequently rewritten and when and whether that's a best practice. Continue Reading