The Applications Handbook.pdf - Nexus Technologies Inc.
The Applications Handbook.pdf - Nexus Technologies Inc.
The Applications Handbook.pdf - Nexus Technologies Inc.
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
70 ■ <strong>The</strong> <strong>Applications</strong> <strong>Handbook</strong><br />
When we look at the complete lifecycle, it’s obvious that launch<br />
may signal the conclusion of the application team’s major<br />
effort, but for the production teams who must work with their<br />
pre-production peers to ensure that the application is responsive<br />
to the business, it’s only the start.<br />
To qualify as “responsive,” the application has to perform well<br />
technically, with good response times for all users. It also has to<br />
serve the business by changing as needed easily, efficiently, and<br />
with minimal risk.<br />
In this context, application performance management and<br />
application change management are critical disciplines in running<br />
an effective live application.<br />
• Application performance management assures that<br />
applications are of consistently high quality.<br />
• Application change management is the key to running<br />
applications that are change-ready.<br />
Application Performance<br />
Management<br />
For a vivid example of why so many want to dissolve traditional<br />
IT silos, consider the usual approach to confirming<br />
application performance.<br />
• Preproduction teams work to develop complex, comprehensive<br />
test scripts that will realistically mirror end-user<br />
behavior.<br />
• When the apps go live, these scripts go into a drawer,<br />
saved for future releases and regression tests.<br />
• Production teams create performance scripts to verify<br />
application response times in the live environment.<br />
But this lack of sharing works both ways. Real user behavior<br />
has the uncanny ability to reveal critical application weaknesses<br />
and faulty assumptions that the development teams