Please use this identifier to cite or link to this item:
https://idr.l1.nitk.ac.in/jspui/handle/123456789/11021
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Basavaraj, M.J. | - |
dc.contributor.author | Shet, K.C. | - |
dc.date.accessioned | 2020-03-31T08:30:44Z | - |
dc.date.available | 2020-03-31T08:30:44Z | - |
dc.date.issued | 2008 | - |
dc.identifier.citation | Journal of Software, 2008, Vol.3, 7, pp.12-21 | en_US |
dc.identifier.uri | http://idr.nitk.ac.in/jspui/handle/123456789/11021 | - |
dc.description.abstract | Application Service Maintenance Projects normally deals with Incidents as First Level support function. Incidents in majority directly link with Production Environment, so Turn around Time for Incidents is a significant factor. Many Companies are having Service Level Agreements with Customer for Turn around Time for Incidents. There is a need to focus on Estimating and Predicting Turn around Time for Incidents. Improvement in Turn around Time helps in improving the Service Level Agreements earlier agreed with the Customer. Saved time can be diverted to other Project Activities like Enhancements or for new requests. This will also helps as one of the paths for Companies to get new business with the Customer. We have used Capability Maturity Model Integration(CMMI)V1.2 Quantitative Project Management(QPM) methodology for Application Service Maintenance(ASM) Projects for estimating and predicting turn around time for incidents. By implementing this best practice in SEI CMMI Level 5 Company we have achieved a significant improvement of approximately 50 percent reduction in Average Turn around Time for incidents. 2008 Academy Publisher. | en_US |
dc.title | Estimating and prediction of turn around time for incidents in application service maintenance projects | en_US |
dc.type | Article | en_US |
Appears in Collections: | 1. Journal Articles |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.