2. Improving speed of application developers
Kyle is being bombarded with requests and he turns to Andrew the app developer as he suspects the problem is with the code supporting the new service.
Andrew is now in reactive mode as he gets pulled off his current project to support a production problem.
This scenario plays out all too often; app developers fire-fighting, having to deal with changes that are often not related to coding. Too much time is often spent figuring out what changed in the environment rather than fixing the actual problem. Inevitably this leads to delayed innovation and directly impacts business agility and ultimately customer satisfaction.
Being able to rapidly understand changes in order to instantly know what triggered problems is high on the wish list for many developers.
Applying the Agile Ops approach in the development process can increase developer productivity. For example, based on internal studies a development team using CA Application Performance Management (APM) to test new code can help the business accelerate development cycles by up to 15 percent in the first year, and up to 10 percent in subsequent and following years. The savings over three years can total more than $4.6 million.
In essence, the company benefits by finding code or system related performance problems much earlier in the software development cycle. Reducing the number of defects released into production, which allows the developmental organisation to focus on innovating for competitive advantage in the marketplace.
Applying agile ops in the application development process often results in higher efficiency. The reasons for this include avoiding first-day failures, compressing the time between development and testing, and shifting some of the development team from testing to addressing business issues.
Having a tool to easily locate where performance problems originate is one way of driving such efficiencies. CA APM's timeline view is designed to allow users to roll back to a point in time and speed triage.
3. Driving quality through the Level 1 support analyst
A wealth of data quickly becomes too much data. Billions of metrics a day require new approaches to visualisation and intelligent analytics to sift through the metrics and identify the relevant variables.
For Pete, a level 1 support analyst, he is typically the first person who receives the system alarm alerts. However, this can be overwhelming as someone in his position typically does not have a deep level of expertise or technical background.
Yet his function as a first responder is important. Drawing a parallel, it is not necessarily efficient or realistic to have surgeons in every ambulance, which is why the first responders play an important role in ensuring the patient is treated until he/she reaches a specialist at a hospital.
Sign up for Computerworld eNewsletters.